4 ms·
What do you think the vast majority of the 2.7 million developers in the US are doing? They are your standard Enterprise CRUD/framework developers.
by scarface_74 3y ago
What do you think the vast majority of the 2.7 million developers in the US are doing? They are your standard Enterprise CRUD/framework developers.
- ghaff 3y agoI don't think I'm disagreeing. If I need some basic plumbing work done, I'm far more likely to hire even a relatively inexperienced plumber than an MIT mechanical engineer with very little practical experience. And if I just need a fairly interchangeable entry-level enterprise developer I might well hire a bootcamp grad rather than an MIT EECS major (who will cost more and may have less hands-on experience). The former may not grow in their job as much--or they may--but that's not really my problem if they help address my current need.
- scarface_74 3y agoI think we are mostly in agreement. Even though I started in computers like this. https://news.ycombinator.com/item?id=36801868 https://news.ycombinator.com/item?id=36801868 I “pivoted” to Enterprise Dev - and really restarted a stagnant career - in 2008-2012 (muddled my way through the recession) Career projection for an enterprise dev is just like a BigTech dev to a smaller degree. Junior engineer - learning the ropes and learning how to be a real professional developer. They will learn the then current frameworks and learn how to turn requirements into code. A boot camp grad has a leg up here. Mid level - they can work mostly independently and by now they can take a relatively complicated feature from requirements to production following standard best practices. They may even be able to lead a team of developers working on a feature. Senior - they can figure out what needs to be done (high ambiguity), lead multiple teams (scope and impact). (After this I happened to pivot slightly and fell into a role at BigTech in the cloud consulting department.) Senior+ - they can have an organizational impact and lead corporate technical strategy. At higher levels, you need to know more about architecture and design. Even in large tech companies, being a good developer and knowing algorithms only distinguishes junior and a mid level developer College wouldn’t help anyone after they pass the L5 level.
- ghaff 3y agoI'll just add that a lot of the most senior people doing software today didn't major in CS and have gone through a variety of significant career pivots; CS is a pretty young field. I suspect a lot of people coming into the field today would be shocked at how circuitous a path a lot of the senior engineers at their company have followed.
- PartiallyTyped 3y ago> learn how to turn requirements into code. A boot camp grad has a leg up here. We did that in undergrad, most of my friends and I are leading small teams a few short years after graduation. We found that people without CS degrees can't handle ambiguity, and need a lot of hand holding to get things done, but maybe bootcamp grads are different. > Senior - they can figure out what needs to be done (high ambiguity), lead multiple teams (scope and impact). I am doing that, on AWS, one of the most important projects of the org, even though on-paper I don't have a lot of "experience". I, the cs grad with an MSc, was the only one who could show that what the seniors wanted to do was [fundamentally] impossible - because this is very exotic CS knowledge. I delivered an approach - on time - that actually worked, when all senior engineers said it would take months. I was the only one who found a way out, and it leveraged all of my diverse - and at times exotic - knowledge and background. > At higher levels, you need to know more about architecture and design. Even in large tech companies, being a good developer and knowing algorithms only distinguishes junior and a mid level developer Ehhh, when you try to solve NP-Hard (or worse) problems, it is good to have people who can identify reductions and implement the right kind of algorithms. When the complexity (hah!) of the task is so enormous that exact solutions are impossible and you need to involve exotic stuff, neither design nor architecture can compensate. To design a good system you need proper knowledge of what you are solving, no amount of engineering and architecture can get around a bad solution to a problem you don't understand.
- scarface_74 3y ago> Ehhh, when you try to solve NP-Hard (or worse) problems, it is good to have people who can identify reductions and implement the right kind of algorithms. When the complexity (hah!) of the task is so enormous that exact solutions are impossible and you need to involve exotic stuff, neither design nor architecture can compensate. I happen to have access to the internal guidelines for being promoted to a senior developer at AWS. It mostly talks about “scope”,”impact” and “dealing with ambiguity”. It very possible for a mid level developer to be stronger than a senior technically. But that doesn’t put you on the promotion track.
- imtringued 3y agoThe thing is, the big money isn't in being a highly skilled theoretical computer scientist who is a technical expert. The big money is in being someone who is able to execute an idea that he came up based on his knowledge in another area of expertise that is completely orthogonal to his technical skills.
- ghaff 3y agoSure but at that point, someone is experienced and it becomes harder and harder to draw a line from their educational credentials to knowledge and abilities they've picked up over 10+ years of experience.
- scarface_74 3y agoI posit that you can’t tell the difference between a mid level developer with 3-4 years of experience whether they learned on the job or from college or through a boot camp. If their company has a good mentorship program. And on the other hand if they did go to a good college and ended up at a company without good practices, they will probably end up being “expert beginners”. Also, I would be very hesitant to hire a software developer who only got experience at BigTech at a startup. They usually don’t have the breadth of experience that you need at an early startup.