3 ms·

There's a very salient point here that "full stack" development isn't something you can start out doing. If you advertised yourself as a full stack developer wi

There's a very salient point here that "full stack" development isn't something you can start out doing. If you advertised yourself as a full stack developer with only a single year of professional development experience behind you, it's likely that you were let go precisely because you aren't a full stack developer. It takes years to develop the body of experience needed to truly work effectively as a "full stack" developer. Now, as mentioned by the insightful parent of this comment, that is more a reflection on the poor planning of the company (and lack of due diligence on their part) than on you, assuming you were forthright in your resume and interview about your history.

bsima 11y ago
The person that did the firing (the CEO) wouldn't be able to tell a difference between a full-stack and a frontend or backend dev. It's a small company, two backend devs (including me) and a frontend dev, though they are hiring 2 more backend devs. For a few weeks, I was the only backend dev. This means I touched all areas of the codebase: designed front-end functionality and aesthetic stuff, wrote backend services, setup devops workflows and did database stuff. So that's why I used the term "full-stack". That said, I definitely plan on specializing over the next few weeks. Full-stack is hard! :)