2,524 karma · joined October 1, 2020
Most people are not that unique. They know where you are and who you are with and any searching or sites you have been to and what is in your text messages or whatsapp as well as that same information for all the people 6 degrees away from you. They know people like you, who are your age and like the things you like and are where you are with friends like yours etc etc it goes on and on.
People rarely talk about things unprompted and you will only notice when you think you talked about something and then see an ad for it so there is a confirmation bias as well.
Most developers don't work building low level high performance scalable systems for a large tech firms, they are making CRUD back-ends for phone apps.
This section of the industry is definitely contracting. Even more obvious is the dev tooling part of it. Dev tooling companies are disappearing or being "bought" all over the place because what might have been a product before is now an hour or two with someone with CC.
Disagree.
Most people would think this is journalism. This is the kind of journalism most people are interacting with in 2026.
Honestly I am not really upset about that. Train them to support the community in other ways while they hang out waiting for a fire. People are always raging that police cant handle mental health incidents, train them for that (heh I am sure firefighters would not be pumped about that but you get the idea).
I don't know. Maybe.
Software might be getting worse but we are not far enough along yet for it to matter. Most people use less than 10 websites total, the internet has shrunk. It will take a while for it to be obvious in the other backend services that they dont know they use. People are really tolerant of buggy shit and some software has already been basically wiped out. Dev tooling is a blood bath right now, things like tailwind and all sorts of little CI tooling is fast disappearing. I wonder what happens to the open core stuff like elasticsearch / gitlab / redis where they gate some features in the enterprise offering that could probably be implemented by LLM pretty fast.
> We're producing massive quantities of code constantly, but still every project is on fire and every line of business is way behind schedule.
Right but did they start altering the schedule when AI entered the picture? We have barely just passed "tokens == productivity".
Also people tolerate quite a bit of buggy shit. Anthropic is down to two 9s (aha) and people still use them. There is a github ci failure post on here like every other day.
There is a wide range of code that will do the same job. 15s vs 2h for code 60% as good? 10 minutes for code 80% as good? 10 minutes today and 10 minutes tomorrow to fix something that is 30% as good?
A lot of people are going to draw that line in a different place and now that people can make that trade off you will quickly find they will and it probably wont fall where you would like it to.
At the end of the day a business pays you to produce value that will earn them money / customers. They don't pay you to write good code. Sometimes those two align and both sides are happy but they don't and often wont.
In some respects maybe in others less so.
So in my situation I am using a client for a system and am using a very specific part of it even though there is a lot of other complicated code in other parts of the client. A LLM is good enough to maintain the code path I am using and of course any changes are triggered / watched over by me. In this situation I am comfortable letting LLMs do most of the code. I would be less enthused if that was outside of my control and the code changes were more often and faster.
I myself have been using an open source lib that I contributed a fix for and inquired about it. I didn't just drop a PR either, opened an issue, was told PRs accepted, opened a PR, signed a license agreement and then the PR just sort hung out for months without response even after some gentle prodding.
Now, they don't owe me anything and they don't have to merge the code, it is their repo after all. However what did I do? use an LLM, fork the repo with my changes and now "I" maintain that private fork and add to it as needed.
As time goes on I think these smaller packages / clients will start to disappear as people/LLMs just spit out a client library or whatever or just implement the same thing over and over. Combined with the opinion of the author I figure oss libs for npm, ruby, pypi etc will start to dwindle.
Solar just thrives in places without dependable established grids and has way lower buy in.
Two different tools for different things.
There are issues though. If you remove the staff from the bus you will need to handle some particularly unruly passengers in a different way. Currently the driver just stops until that person leaves or gets police / special constables involved.
In fact one of the worst "trade offs" of the trades is they can very much be a young mans game.
It gets real hard to sling water heaters up/down tight stairs or pull cable in a 100+ degree attic into your 50s.
It is why I never use "sign in with <google, meta, apple, whatever>"
"Agents" can be very "persistent" and when not sand boxed appropriately can get at things they were not meant to get at. Even if its only 1/1,000,000 that one time that one time is going to keep making the news
Explaining that to the general public when facebook is pushing Muse on everyone will be difficult so its going to get worse before it gets better (if it gets better)
JS running on a raspberrypi can support most sites on the internet.
Sure it matters at scale but what tech interviews forget is most don't every get to the scale where it matters.
A 2015 machine with duel xeons can run many many small tech companies stacks.
The open models that are chasing the frontier labs will stop being open once things slow down and there is less incentive to undercut the front runners. Time will tell if GPU compute gets cheap enough to run stuff locally.
Now I derive no satisfaction from anything 'I' have built with it. At some point I am just stuck asking myself "Why am I doing this if someone can prompt an LLM the same way I have and get a similar result?". I can have the LLM write documentation, only to think "who am 'I' writing this for?". Why bother if someone isnt even going to read it, its just going to become context for someone else's LLM session.
I know there are other ways to look at but this is where I am at currently.
Some German compound nouns are funny.
Which people would be wise to remember. HR is there to protect the company, not you or your co-workers. Sometimes these two things align but not always.
In the age of LLMs every one is "tailoring" their resume to every posting.
https://code.claude.com/docs/en/hooks-guide#agent-based-hook...
It burns more tokens but is the only way to get tolerable text.
When I tried minio 5 years ago it choked pretty quick on storing billions of objects
Just hit a button the bottom and it swaps to the other input and I keep the keyboard / mouse plugged into the monitor and it goes where the input goes.