4 ms·
I think you should be able to set up database backups (it can affect your overall architecture, so someone in development ought to know). I think you should be
by eximius 7y ago
I think you should be able to set up database backups (it can affect your overall architecture, so someone in development ought to know). I think you should be able to configure a web server for the same reason.
Security dependencies/updates? Those are largely transparent and a matter of noticing and updating. Operational changes like updating a systemd config or something. They affect your platform but not your application.
- kthejoker2 7y agoWho know it was all so simple? Everyone should just be a jack of all trades and master of none! Underestimating the complexity, variety, and difficulty of all the tasks of delovering professional-grade software is the biggest challenge in the industry. It's like telling a soccer player to be his own cook, trainer, and psychologist. Specialization means letting the law of comparative advantage do its thing. It has nothing to do with "what I'm able to do" and more about being optimally efficient.
- eximius 7y agoI didn't say it was simple. I didn't say you needed to abandon mastery of a field of your choice. It is hard. But a soccer player should know how to make pasta, cook meat so that he doesn't get sick, even if he isn't a gourmet chef. He should be able to do physical activity without harming himself, etc. We should all be generalists to some degree. Where on that spectrum of specialization we should be satisfied is a valid debate. I also don't disagree that there are costs/inefficiencies generated by being more generalists vs more specialized. But it also depends on the size of the organization you can rely on. If I work at a startup, I may need to be more of a generalist. If I work at FAANG, I can specialize because I can depend more on the specializations of others.