There's another way to get this kind of parallelism without the mess of microservices. Build a well architected monolith and be super strict on single purpose and keeping modules separated from each other.
There's no such thing as a small software team anymore
91–100 of 183 posts
Re: There's no such thing as a small software team anymore
#92Re: There's no such thing as a small software team anymore
#93I'm a 1 person dev team who wrote frontend code that outperforms React. Is was successful because I didn't use any sort of LLM assistance.
That's pretty impressive. I always like bespoke web utilities tailored for specific dev purposes. What approach are you taking? I'm about to start a mithril.js project, was always under the impression it was the most efficient approach. Are you doing something similar or different or are you referring to WASM?
It’s not hard to be faster than React while exposing broadly similar functionality. If you’re making something for your own usage only, it’s even easier to beat it.
Re: There's no such thing as a small software team anymore
#94Earlier quoted context omitted.
> but programming is never going back to normal. Are you telling it's shit now? I'm just curious.
You're not going to get your old job back. You're a prompt engineer or you're fired. Programming will never go back to what it was before 2026.
Re: There's no such thing as a small software team anymore
#95> If you have a large monolithic service where every change has to be coordinated carefully.. Microservices are WAY harder to coordinate for deployments. You end up with feature service dependencies, and you are back to the same coordination, but now harder to discover down stream dependencies..
Re: There's no such thing as a small software team anymore
#96Re: There's no such thing as a small software team anymore
#97Wait two years until we have sufficient churn of senior talent in the teams. Then all of the services will have outages daily. Only the seniors who know their systems are keeping the lights on today by keeping bs commits out. Once they burnout and quit, nobody will have a freaking clue what the LLMs have done and why services are down.
I have a similar concern, though. To do my job, I need to understand "the thing". I could outsource the understanding process to AI, but then if I'm asked a question by a developer or tester then I'm essentially stumped / useless because I didn't spend the time to understand the thing, I handballed it.
So I then ask the LLM the question I was asked, and pass the answer back (they could have done this themselves though, so where does that leave me? I'm either an AI wrangler, or replaced by someone else who wrangles AI replacing mutliple people in my role). Does my personally understanding the thing actually add value - do the seniors who know their systems add value - in the age of AI/LLM?
Does "LLMs all the way down" solve the problems?
With the existence of hallucinations I lean towards 'no', but again is that solved by adding layer(s) of LLMs to check for hallucinations?
Re: There's no such thing as a small software team anymore
#98Earlier quoted context omitted.
You're not going to get your old job back. You're a prompt engineer or you're fired. Programming will never go back to what it was before 2026.
You're living in a corporate bubble, drowning in the kool-aid, along with half this forum.
Re: There's no such thing as a small software team anymore
#99Hundreds of bots modifying thousands of microservices may sound good on the surface, but all those thousands of microservices make up an architecture and a product. Agents aren't very good at carrying the entire model in their context, so when they reason about a small piece of code, they often come up with something that hurts other parts of the code (especially as the KLOCs pile up). The complexity hasn't been repl…
What’s the point if you’re treating the whole system as a slop bucket?
Re: There's no such thing as a small software team anymore
#100Earlier quoted context omitted.
I don't say this to be mean, but you need to plan for a world where it's always summer. Maybe the valuations will collapse with OSS models but programming is never going back to normal.
> plan for a world where it's always summer The difficulty in adopting this belief lies in the fact we have multiple points of reference in the past, of visionaries claiming that "this time is different" and we reached the end of history... and well, the rest is history.
In fact there's almost nothing similar between my day to day life and the day to day life even of my grandfather, to say nothing of the Irish peasantry I came from 500 years ago, say. The number of correct everything-is-differences per year seems to be going up, not down.