4 ms·

I think that if someone chooses engineering then he must love to learn. For me it would be too boring to do the same thing for my whole life, I always try to le

I think that if someone chooses engineering then he must love to learn. For me it would be too boring to do the same thing for my whole life, I always try to learn more languages, more paradigms, architectures and whatever. I can jump in the code of a different team and be immediately productive. Usually I suggest and implement small changes that have a large impact on the maintanability of the system as soon as I start to grasp it as a whole. I couldn't ever do it if I stayed in the same field, in the same environment, for all my life. I think that if someone expects to work in a field doing the same thing for the majority of his career then probably should not choose engineering.

emodendroket 9y ago
But you are doing the same thing. This is the frustration. I've worked in several languages with various tools and it's very common to just be learning slightly different syntax to approach a problem in the exact same way (and then eventually maybe you'll reach a higher plane where you approach it in a way somewhat characteristic of the tool, but still not fundamentally different). Technologies that really change the way you work or think about problems are few and far between, and most of the algorithms and data structures you'll use most of the time in typical applications were discovered in the 1970s. It's not a big deal to pick up a new tool on the job, but I have a hard time motivating myself to spend free time learning yet another MVC framework or whatever. It's a different story, I guess, if you go into a completely different type of programming from what you're used to (say Web apps to embedded programming), but I don't think that's necessarily easy.