I know managers love that term, but I think I’ve come to hear it as an insult… Sorta like being called an unprofessional “jack of all trades” budget handyman that does everything mediocre…
I know managers love that term, but I think I’ve come to hear it as an insult… Sorta like being called an unprofessional “jack of all trades” budget handyman that does everything mediocre…
That is a compliment. The separation of front end developer and back end developer is obsolete and untrue. Either you are a developer or not. If you work on web, then you must, now or in the future, know how web browsers work, how APIs work, how to write and consume them, etc. The browser is just an API we consume from JS. There are many others.
100% agree. Programming is programming, and these divisions are arbitrary and restrictive.
It’d be like if someone wanted to learn a language, but refused to learn vocabulary about an important topic.
I agree that back end dev and front end JS are pretty much the same skillset, but HTML and CSS (especially so if you include design and UX) are very different and not something I would expect any dev to be able to pick up easily.
I’m not going to write .Net, you can’t make me do it. I’m not going to write Python, you can’t make me do it.
Is your backend Node?!? Let’s go baby, I’m a full stack dev.
Node and JS is just an example of how easy it is to write code for the back and front ends. You may employ as much langues as you want like PHP, Java, Rust, Python or even Elixir. Does not matter.
If you’re not being sarcastic, why limit yourself to only one thing? If you’re working on some amazing UI with tons of CSS animations and a full audiovisual experience, and it takes intimate knowledge of everything frontend, I guess it would make sense. But if you’re just making internal CRUD apps, I don’t see a reason why a given domain is special enough to have its own job title.