3 ms·

Ok boomer! that said I feel the same, having worked solo for 10 years. 99% of the stuff i read about in this forum is about processes, management, code review,

Ok boomer! that said I feel the same, having worked solo for 10 years. 99% of the stuff i read about in this forum is about processes, management, code review, packaging, testing, automating deployment. Who is doing the actual building? It used to be that , with software, "processes" are automated leaving you with only the highest-of-the high level entities, the code, which is brief like poetry. Code seems less powerful nowadays, not a tool to create, but hidden under layers and layers of process. I 'm kind of thankful i don't have to work for others ever again, but i m also missing out on SV-level salaries. How much time do people spend writing program rather than checking in and out of various systems?

hootbootscoot 7y ago
this. and ultimately, who PAYS for all these deliberate hurdles and the deliberate curtailing of human productivity to serve a tangential dubious (at best) goal?
- marktangotango 7y ago
  Seems like a proof by existence about the predominance of BS jobs?
tarsinge 7y ago
I think these two kinds of environments always cohabited. In the 90's/00's you had enterprise software development (think old school J2EE) which was all about processes (and boilerplate code), with the smallest feature taking months to implement (and usually resulting in an over-engineered outsourced low quality mess). On the other side you had small shops environments like ID Software and startups with a completely different philosophy. My take on the issue is that we have lost the distinction, and now everything is enterprise software development. No matter your size and the scope of your project you must adopt THE enterprise way of developing. The reason is that using the same processes and tech that a FAANG/Unicorn has basically become a requirement in term of signaling, both for companies and developers. Edit: What we miss is that at that size they are (rightfully) solving processes problems. But for startups it's irrelevant (or premature optimization at best). Previously it was simpler: companies with 1000+ developers were not cool.

hootbootscoot 7y ago

this. and ultimately, who PAYS for all these deliberate hurdles and the deliberate curtailing of human productivity to serve a tangential dubious (at best) goal?

marktangotango 7y ago
Seems like a proof by existence about the predominance of BS jobs?

tarsinge 7y ago

I think these two kinds of environments always cohabited. In the 90's/00's you had enterprise software development (think old school J2EE) which was all about processes (and boilerplate code), with the smallest feature taking months to implement (and usually resulting in an over-engineered outsourced low quality mess). On the other side you had small shops environments like ID Software and startups with a completely different philosophy. My take on the issue is that we have lost the distinction, and now everything is enterprise software development. No matter your size and the scope of your project you must adopt THE enterprise way of developing. The reason is that using the same processes and tech that a FAANG/Unicorn has basically become a requirement in term of signaling, both for companies and developers. Edit: What we miss is that at that size they are (rightfully) solving processes problems. But for startups it's irrelevant (or premature optimization at best). Previously it was simpler: companies with 1000+ developers were not cool.