Capt Caveman
Lifer
- Jan 30, 2005
- 34,547
- 651
- 126
Hmm, a lot of the people I know who do backend work aren't labeled as architects and their work isn't architecture either. That's often a separate role in itself. Architecture is someone who makes the blueprints and backend devs are usually the people who just implement those blueprints (and sometimes follow standards, which usually come from an architect)... This isn't true in all companies but you'll find it frequently enough in large companies with appropriate budgets.
A little bit of everything is okay but that's only great for companies that can't afford separate roles. It'll also hold you back from getting jobs at companies that can afford those separate roles. (Again, the difference between a full stack web developer and someone who does backend/dba/frontend/architecture/api-dev/etc) People who are great at one field are much preferred over people who are just okay at a bunch of fields. This is true in a lot of career fields... not just software dev.
You're one step above clueless. I love how you think you know how things work when you've had one job and can't get a job b/c you've decided to ignore all of the good advice given to you. Time to make amends with your parents.