|
|
|
|
|
by bstar777
1716 days ago
|
|
This is such a strange thing to choose to write a derogatory article about. If you are a singular developer that is only writing code to satisfy your needs, then you can do whatever the hell you want. If you have to work in a collaborative environment, then you will likely need to play by the rules of that environment. There's not much else to say about it. The stuff about automation doesn't even seem to fit in this article... that's a completely different conversation. |
|
I've always worked at agencies so I get exposure to a great deal of projects, and I do partly see what they are saying. More and more parts of orgs are becoming intertwined with software, and they're becoming better at software, requiring you as a developer to organize and connect all the loose bits and pieces everyone else has made to achieve tasks. That takes communication and collaboration even if you're the only developer.
Half my days are spent getting access to SaaS accounts, figuring out who's in charge of what, finding out if certain things are still in use or not. A task like "automate a monthly sales report" becomes a journey of discovery, where you don't have access to anything, and nothing lives where you expect it to.
A single piece of functional software, built from the ground up, is not usually what I find in a new project anymore. More often it's a hodgepodge of SaaS that's opaque and hard to reason about in whole, but each part made sense at the time.