5 ms·
Programming for the sake of programming gets boring after a few years. At least for me, this was the case. There is only so far you can go with it as a pure di
by laichzeit0 9y ago
Programming for the sake of programming gets boring after a few years. At least for me, this was the case. There is only so far you can go with it as a pure discipline. Once you've mastered design patterns, higher order functions, etc. you end up with writing "just another" app, service, CRUD thing, etc.
What I found really interesting was going one step further and using programming to solve "higher order" problems, such as data science or artificial intelligence related problems. I'm not talking about implementing something in Tensorflow. That again is just programming. I'm talking about implementing something in Tensorflow to solve a specific problem and seeing the result of that. The programming part is beside the point, it is a means to an end.
I think you really need to dig deep and ask yourself why you are writing code at all. The act of writing software itself is not that intellectually stimulating once you've mastered it well enough. It is just one layer of abstraction. Think about what is the next layer of abstraction you can build on top of your programming layer.
- ryanianian 9y agoThis sounds like natural career progression (and also perhaps why some get bored doing the same thing for so long). You want to move up the lever of impact. For many this means applying their experience to a growing field (e.g. lots of interest in AI/etc recently) or helping other developers be more productive and not have to solve the same problems they did (e.g. growing k8s, cloud, ci tooling, new languages, etc.)