Rule 9: No Low Effort Posts, Excessive Venting, or Bragging.
Using this subreddit to crowd source answers to something that isn't really contributing to the spirit of this subreddit is forbidden at moderator's discretion. This includes posts that are mostly focused around venting or bragging; both of these types of posts are difficult to moderate and don't contribute much to the subreddit.
A couple of ways:
First, I decide at the beginning of a project what skills I want to learn from developing the project, and approach it from the perspective of learning new skills. That way, even if part of the project is tedious, I can think of it as a learning exercise.
Second, I develop open source software in my spare time, and whatever I'm doing in my paid job, I do something else in my open source project. When my task at work has me writing Perl, I write my own software in C or D. When my task at work has me writing Python, I write my own software in Perl. When work has me on an integration task, I spend my spare time working on LLM inference software or cryptography or something else very **un**like integration, and so on.
You don’t have to work in the same thing at your company.
I’ve had wide ranging jobs ripened even on the same team at my companies. And that’s ignoring internal transfers.
Same system, but you can approach solutions and designs in different ways. Then you end up with a bunch of apps using different design patterns and/or languages.
I leave after a few years. It doesn't look bad (IMO staying at one place for 20+ years looks worse), I end up with a new set of domain knowledge and new interesting things to work on. Also early startups are helpful for this if you can do greenfield projects.
Good companies understand this is an issue and have formalized internal mobility programs to transfer to another team to keep good people engaged.
Even if there isn't an official program in place, your manager might be able to pull some strings. Ask about it.
I just told my manager i want to change teams. New tech, new projects, new coworkers. Mostly because i have 3.5YOE, ive been learning little last year or so, and i want a good resume for my mid career.
I'm not bored so I don't have to "fight the boredom". I am having fun writing code with a team of SWEs creating something bigger than I could ever do on my own.
Rule 9: No Low Effort Posts, Excessive Venting, or Bragging. Using this subreddit to crowd source answers to something that isn't really contributing to the spirit of this subreddit is forbidden at moderator's discretion. This includes posts that are mostly focused around venting or bragging; both of these types of posts are difficult to moderate and don't contribute much to the subreddit.
I look at my paycheck every two weeks. Helps with the boredom.
A couple of ways: First, I decide at the beginning of a project what skills I want to learn from developing the project, and approach it from the perspective of learning new skills. That way, even if part of the project is tedious, I can think of it as a learning exercise. Second, I develop open source software in my spare time, and whatever I'm doing in my paid job, I do something else in my open source project. When my task at work has me writing Perl, I write my own software in C or D. When my task at work has me writing Python, I write my own software in Perl. When work has me on an integration task, I spend my spare time working on LLM inference software or cryptography or something else very **un**like integration, and so on.
Boredom is a luxury
You don’t have to work in the same thing at your company. I’ve had wide ranging jobs ripened even on the same team at my companies. And that’s ignoring internal transfers.
Same system, but you can approach solutions and designs in different ways. Then you end up with a bunch of apps using different design patterns and/or languages.
I leave after a few years. It doesn't look bad (IMO staying at one place for 20+ years looks worse), I end up with a new set of domain knowledge and new interesting things to work on. Also early startups are helpful for this if you can do greenfield projects.
Good companies understand this is an issue and have formalized internal mobility programs to transfer to another team to keep good people engaged. Even if there isn't an official program in place, your manager might be able to pull some strings. Ask about it.
I just told my manager i want to change teams. New tech, new projects, new coworkers. Mostly because i have 3.5YOE, ive been learning little last year or so, and i want a good resume for my mid career.
I'm not bored so I don't have to "fight the boredom". I am having fun writing code with a team of SWEs creating something bigger than I could ever do on my own.
I remember my first job