3 ms·
Switch teams to a different domain every six months? In the domains I’ve worked in, it might take six months just to get the basic idea sketched out and workin
by teakettle42 4y ago
Switch teams to a different domain every six months?
In the domains I’ve worked in, it might take six months just to get the basic idea sketched out and working. The current project has a timeline of 8 years to full completion — two years just to get to the first minimal release for a subset of our problem domain and the hardware to run it on.
It sounds like you’ve been doing unchallenging work in unchallenging domains and have acquired a much too inflated opinion of yourself in the process.
- fdgsdfogijq 4y agoI've worked on teams with 6 month ramp up times. Almost always this happens because there is an absurd amount of domain/business knowledge encoded in some massive 500k line code base. Tenured engineers gate keep with domain knowledge. The real learning happens by switching between working on those types of systems and then moving to greenfield to implement the patterns you observed.
- teakettle42 4y ago
- fdgsdfogijq 4y agoI'm talking about corporate jobs/high tech startups. Compiler development is like .001% of programming jobs
- teakettle42 4y agoI apologize for the insult, but perhaps this means there’s still more for you to learn, and even deeper and more interesting problems to explore? I’m about 25 years into my career, and I still have so much more I want to learn!
- Beltalowda 4y agoHow do you know if you did a good job if you leave after a few months? Did you leave a beautiful work of art, a bug-ridden unmaintainable mess for others to clean up, or anything in-between? A large part of experience is doing things that seemed like good and reasonable idea at the time, and then discovering that it actually wasn't. And how do you know what are and aren't good ideas? By sticking around and seeing what does and doesn't work.