Member-only story
Are you an Angular developer? You probably shouldn’t be.
Read the free version here
My friend used to tease me:
“once, you were a software engineer, then you decided to become an Angular monkey🐵”
I don’t think frontend development is inferior to backend. Specialising for either is a legit choice, as there is value in depth of knowledge. Some say it’s best if one’s knowledge is T shaped, has a solid foundation and has an area of depth to it.
Fullstack?
Some believe in unicorns of course, and it is their right to do so, but let’s not kid ourselves, fullstack engineers are but an advertisement for managers who don’t want to spend two to N times the headcount to hire. They’d need a frontend, backend, devops and security specialist at the bare minimum. But instead they hire a unicorn.
How full is your stack?
I could ask, if I were even more cynical than I am anyway. But I won’t.
Why not Angular?
I have no beef with Angular, I have been working with it for more years than I can remember. Even with AngularJS and hybrid applications. But I never considered myself an Angular developer and I wouldn’t recommend you do either. Naturally, my T has a depth in Angular, and so Angular opportunities find me. If a non-Angular opportunity finds me? I’ll take it thank you very much. As long as it’s not a one-way street like a company specific framework, I…
