me too, but at the same time i'm enjoying getting things done, otherwise i would get lost in details like bikeshedding naming variables and making the code look pretty, and little would be done.
Makes sense to me, though I think one important (IMO) aspect of this evolutionary role is incurring liabilities. Yes, software can be created by a wider audience, but when things go awry, would they have the aptitude or contingencies in place to recover and take responsibility?
Maintenance of software/systems was a mere after thought in my experience. Adding new things made careers, bonuses etc. so there was no real incentives for maintenance. The article argues that LLMs will do it. I'll believe if and when I see it.
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
I made a chrome extension to bring the top Hacker News stories to your new tab, with quick summaries.
So every time you open a new tab, you might discover something everyone else hasnโt heard about yet.
If youโve never heard of Hacker News: it was created by Paul Graham(founder
I noticed today that I'm an idiot.
I built a static site generator with NO DATA MODEL. Beginning to fix it now, but my god how embarrassing. Hobbyist less than amateur...wow.
Good thing my day job isn't at stake.
Another little corner of the internet. Anything using fixed-width fonts and without pictures has surely got to be promising in this day and age, surely...