botfriendsarent

The simple version is, when typing was a job, people put IBM selectrics in their homes to signal they were economically viable.

Then Bill G said you wont have a job if you dont learn MS word so people put PCs in their homes.

All we have ever done in tech is imitate our employers so that we can signal to the world we are employable deploying tech at home.

At his point I not anti, but with the onslaught of AI imitating your employer now looks pretty gross. Maybe we hit the wall. Looking back on it it looks pretty silly. Plus RAM costs. Get a pet turtle.

I think this is a fair and normal reaction to AI slop. Alot of work though. I think OSS projects are at serious risk of implosion due to the vigilance required which honestly may end up being a fool's errand anyway.

But maybe we are thinking about it backward. Have you ever wondered why there is so much "free software"? Beware of strangers bearing gifts.

I have always wondered and been suspicious of people who are so eager for you to use their software. Which isnt to say OSS isnt high quality. Im just saying that maybe when people are pushing free software on you they are kind of in it for themselves.

As for whats next, me personally, last year I pulled all my personal repos about 80 of them off of bitbucket and self host that all now. I think OSS projects should setup a paywall and charge money to create PRs.

Like 10-100 bucks per PR to cover the cost of the extra vigilance. Also I could see migrations away from github, to AI free dependency hosting or something like that. Its an interesting challenge. But its not insurmountable.

Either paywall OSS projects or take them off the interwebs. Also one option the OP didnt explore I dont think is forking and freezing the dependencies. Huge maintenance burden, but its better than source corruption.

Also use fewer dependencies. Maybe set a limit of 5.

I had a friend back in the 90s who referred to his desktop computer as "his mainframe" lol

This "home lab" stuff is kind of nice hobbyist talk. I wish we had fancy words like that back in the 80s.

Technology has come along way. But I think that in tech we should be careful to not fall prey to monkey see monkey do.

We should not be deploying technology in our homes to "mimick our employers"

Remember they are miserable for a reason.

Dude! Give me some stolen science!

I tried it all it said was "Hot or not?" before it crashed

Sonnet 5 OUCH! every model is just loaded with more hurt, stolen content, BS prompts, more scare tactics, more illusions, more government lobbying, less honesty.

Oh Claude you master of software engineering does it ever end? DO you have no bounds?

How may we further assist you oh Claude?

Sounds suspiciously similar to the "album title", "Steal this album" by system of a down.

Im not sure why we are dithering on the boundaries of honesty when the entire content LLMs are trained on is stolen.

Are we debating "honor among thieves"?

Of course we are not, or maybe we are!

Does the behavior of a thief even matter to me? only after they do their time. And they will.

I can see the investors perched on the balconies of their condos in a couple years if that.

its a long way down.

This is what I also do not just in JS but also in other languages. But I write the schemas. And I dont use TS. Im glad Im not the only one. The OP post gave me a serious headache trying to read it.

Parse and Validate are not binary choices and have nothing to do with each other. Both are useful when applied correctly to a given situation.

I felt punked by most of it. I dont see what programming languages have to do with it either. Look at swift, a language that can barely only barely parse JSON. Who cares?

What if they sent out a hit squad to your house?

At what point though doesnt somebody stand back and say "wow, thats really dumb!" I think its probably more an indication of a dev having too much time on their hands rather than being in a hurry.

I actually dont see AOP ever coming back. Primarily because its authors were modeling smalltalk which ironically didnt even need AOP.

At first it hooks you these cross cutting concerns, but then you realize it handled better as a simple dependency.

AOP as a concept is great, however in practice using real world tools never lived up to the implications.

Its all or nothing, almost if not all code can be written as a "cross cutting concern"

I could write one function for the rest of my life, and simply use AOP to inject a different program.

but WHY would I do that? Something so incongruous with my mission as a software engineer. AOP was pretened smalltalk MVC glue for other languages that didnt have it at the time.

It didnt last long and it wont be back.

More useful than a working accounting system?

Because of the disaster of screen resolutions, mobile form factors and all the previous dishonesty inherent in the past 30 years of software development?

That must be really useful. The machines are not the problem. UI layout was solved 40 years ago on all windowed and non windowed platforms.

Mobile breakpoints are not special.

How about the browser as a "failed platform"? Seems to fit! Hardware is irrelevant.

You are right about being cynical about media.

But you didnt grow up reading BYTE magazine.