|
|
|
|
|
by ehnto
1716 days ago
|
|
From that light, I think the article's point is that rules of the environment have changed so much that the archetype of the lone-programmer is becoming obsolete in the workforce. 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. |
|
I see now that much of my ability to accomplish a task/feature/project is now out of my control - I'm now so highly dependent on 3rd parties and spend the day sorting out stuff to glue together rather than actual creative work.