I'm sick of the distinction between backend and frontend engineers.
The backend engineers think they're hot shit because they solve the big problems. They know how to scale. They look down on frontend engineers who are only solving trivial problems. Backend engineers build the real things. They don't have time to learn about CSS or a wretched language like JavaScript. Without them, a project can never be successful.
The frontend engineers think they're hot shit because they're the closest to users. They know to perfect a user experience. They look down on backend engineers who have no idea how the product is actually used. Frontend engineers build the real things. They don't have time to learn about partial template specialization or wretched languages like C++. Without them, a project can never be successful.
You're both wrong. You must do both or you'll be irrelevant (somewhere).
Over-specialization is the curse of our profession. Stratification breeds condescension. The only remedy is for all engineers to do full-stack programming.
I'm Brett Slatkin and this is where I write about programming and related topics. You can contact me here or view my projects.
05 November 2012
About
I'm the author of the book
Effective Python. I'm a software engineer at Google (currently in the Office of the CTO) where I've worked for the past 19 years. Follow @haxor on Twitter
if you'd like to read posts from me in the future. You can also
email me here.
© 2009-2024 Brett Slatkin