Do you prefer single tech stack throughout your career?
In the beginning of my career, I worked on multiple technologies. After a few years I specialized in a single technology stack for a good 8+ years. Now I have just grown bored and so I decided to learn and move to a new technology stack. Thinking of other people having similar experiences? Did you changed your technology stack ever? Or did you just stick to the same tech stack for the rest of your time and became a manager at some point? Love to hear about your experiences. #shareyourexperience #singletechnologystackboredom #learning_experience
Started off as web dev and then started working in services in Java. Eventually moved to do Golang services. Overall it feels good to see the growth. Things aren’t immediately obvious but once you pick up the similarities, its very rewarding.
Full stack to middleware?
Frontend to full stack. I still do web and front facing technologies but also build Golang services.
I probably have a different perspective. I’ve never been asked about any sort of “tech stack” in an interview and I’ve never had a job where I’ve had to explicitly use any tech stack. I use whatever languages and tools will help make my company the largest possible profits. I think if you focus on your CS/math fundamentals and focus on making money then that’s how you succeed and not get bored. Throughout my different jobs I’ve worked on web dev, kernel development, trading infrastructure, and other stuff. Haven’t gotten bored yet.
Real engineers solve distributed systems & storage, build infra & DB. Full stack & frontend growth saturates pretty fast no matter how many stacks you change!
What do the job description look like for those and which language is used
AWS S3, DBaaS teams. Azure CosmosDB Facebook storage GCP Spanner Low-level is C++ and some things are mostly Java. These are hard engineering problems with ms of optimization. Then the full-stack or FE or whatever engineers just develop a gateway for the user i.e. Not solve engineering problem, business problem!
Worked on Java the entire career, doesn't need another language.
Not to badmouth Java, but After coding in Java, you can't write it in other modern languages now adays. They can do the same thing with boilerplate code reduction far more better than Java. However Java has also been upgraded with these new standards.
You can't really write it faster than Java for backend services. Because you don't need to reinvent wheels. And you can't beat battle tested wheels.
You need to try new things to stay sharp. Otherwise you die professionally.
Rest and vest.
Seems so true but at the same time I feel with family its quite difficult to play with a career... Specially when it comes to changing a technology stack.
Same stack same 💩 every day. Everywhere I go and do similar thing. At least as an IC I can slack off. Where as manager you need to stay awake during meetings for the most part At end of the day I don’t really give a f. Waiting for the day to FIRE. 🔥 🔥 🔥
Look into working at a consumer facing software company. That may change the pace slightly.
Which team at Apple? You can say director level to stay anonymous. And what stack? Java and Scala?