The right question for most people is not am I happy at work but rather "can I tolerate work", same as marriage.
Am I Happy At Work? Analyzing my entire career
21–30 of 128 posts
Re: Am I Happy At Work? Analyzing my entire career
#22This is great! I wish I'd started doing something like this long ago. The closest thing I've found to this that I'm able to at least remind myself to use regularly is this, https://daylio.webflow.io/ It'd be interesting to leverage something like this to decide when I should take vacation... If my happiness is slowly decreasing and visualized like this, it'd serve as a nice reminder to schedule some vacation. I'd als…
I just tried this one, (and another one, Journal which both seems to be Google 'editors choice'), but I found that both only had 5 possible moods (basically: exstatic, good, meh, bad, terrible) , and I fear me data will just be 90% "good". Do you know if it can be configured to have more levels? Or if other apps have more specificity?
Try MoodDiary[1], it has a scale of 10 but also allows tracking multiple metrics (e.g. I track 4 metrics: sleep, mood, energy level and overwhelmed vs. undercontrol)
[1] https://play.google.com/store/apps/details?id=de.jonathansau...
Re: Am I Happy At Work? Analyzing my entire career
#23I don't want to sound an asshole, but I will sound an assholle nevertheless. I was damn happy as one can be at 3.5 years in my career. 10 years in, I feel like my happiness and awesomeness has been slowly consumed by corporate politics, unfair promotions and layoffs, bad work ethics and the such. I still like my work. I really really enjoy it when it's productive, and I still feel amazed to see the green checkmark on…
> I still feel amazed to see the green checkmark on my CI after a long and challenging git push
How is this "amazing"? Can you not build a branch locally to see if it works as you go? Have you no facilities to run local tests?
Re: Am I Happy At Work? Analyzing my entire career
#24I don't want to sound an asshole, but I will sound an assholle nevertheless. I was damn happy as one can be at 3.5 years in my career. 10 years in, I feel like my happiness and awesomeness has been slowly consumed by corporate politics, unfair promotions and layoffs, bad work ethics and the such. I still like my work. I really really enjoy it when it's productive, and I still feel amazed to see the green checkmark on…
> I still feel amazed to see the green checkmark on my CI after a long and challenging git push How is this "amazing"? Can you not build a branch locally to see if it works as you go? Have you no facilities to run local tests?
I don't know about OP's environment, but the larger the codebase, the less feasible running every test locally as you go becomes. You run relevant tests locally as you go, but depending on the change it might take a long while to run ALL tests that could possibly be impacted.
Re: Am I Happy At Work? Analyzing my entire career
#25I don't want to sound an asshole, but I will sound an assholle nevertheless. I was damn happy as one can be at 3.5 years in my career. 10 years in, I feel like my happiness and awesomeness has been slowly consumed by corporate politics, unfair promotions and layoffs, bad work ethics and the such. I still like my work. I really really enjoy it when it's productive, and I still feel amazed to see the green checkmark on…
The only places I found where this was not the case were companies / teams in a state where their existence and viability depended on churning out high quality software. Crisis situations with pressing needs have the doubly added advantage that they are irrational choices for those consumed by corporate politics.
Re: Am I Happy At Work? Analyzing my entire career
#26Earlier quoted context omitted.
> I still feel amazed to see the green checkmark on my CI after a long and challenging git push How is this "amazing"? Can you not build a branch locally to see if it works as you go? Have you no facilities to run local tests?
I don't know about OP's environment, but the larger the codebase, the less feasible running every test locally as you go becomes. You run relevant tests locally as you go, but depending on the change it might take a long while to run ALL tests that could possibly be impacted.
I'm still surprised that there'd be an element of uncertainty. Wouldn't you want to be sure that your code would pass before pushing it out for others to see? What if you pushed and the CI gave you a red X, wouldn't you then feel bad when your coworkers see that and think you are a poor coder? Seems to me it'd be best to be absolutely sure everything would pass before letting anyone else read the code...
Re: Am I Happy At Work? Analyzing my entire career
#27Earlier quoted context omitted.
I don't know about OP's environment, but the larger the codebase, the less feasible running every test locally as you go becomes. You run relevant tests locally as you go, but depending on the change it might take a long while to run ALL tests that could possibly be impacted.
I'm still surprised that there'd be an element of uncertainty. Wouldn't you want to be sure that your code would pass before pushing it out for others to see? What if you pushed and the CI gave you a red X, wouldn't you then feel bad when your coworkers see that and think you are a poor coder? Seems to me it'd be best to be absolutely sure everything would pass before letting anyone else read the code...
"Absolutely sure" isn't an achievable level of surety, because everything has a chance of failure, however small.
You could go for "NASA sure", which is when you spent 100x the effort of the average tech company making sure only some of your spacecraft explode on launch, or you could go for "Github sure", which is when you spend a large chunk of your $200+ million ARR to ensure your core product only has a couple of major outages every year, or you could go for "startup sure", which is when your test coverage is 5% and you throw random stuff into production to see who complains, but you can't ever achieve "absolutely sure".
Re: Am I Happy At Work? Analyzing my entire career
#28Earlier quoted context omitted.
I don't think licensure is part of the definition of "engineer"
I didn't get a chance to see the comment before he edited it out, but in some countries (Canada I think?) "engineer" is actually a protected title, requiring licensure. I don't know what his point was, but as a "software engineer", I sometimes wonder if I should be called a "developer" and let my PE friend keep the "engineer" title, just for clarity's sake.
This, also there was that kerfuffle in Oregon about someone saying they were an engineer, but not licensed, and how that was apparently illegal.
https://www.washingtonpost.com/news/morning-mix/wp/2017/12/0...
Re: Am I Happy At Work? Analyzing my entire career
#29Earlier quoted context omitted.
I don't know about OP's environment, but the larger the codebase, the less feasible running every test locally as you go becomes. You run relevant tests locally as you go, but depending on the change it might take a long while to run ALL tests that could possibly be impacted.
I'm still surprised that there'd be an element of uncertainty. Wouldn't you want to be sure that your code would pass before pushing it out for others to see? What if you pushed and the CI gave you a red X, wouldn't you then feel bad when your coworkers see that and think you are a poor coder? Seems to me it'd be best to be absolutely sure everything would pass before letting anyone else read the code...
A failing CI build should not be taken as indication of being a "poor coder". As others have said, in complex systems running every single tests locally can be very time consuming, or even impossible. In my opinion, if you work in an environment where being seen as poor coder because of failed CI builds is a real concern, that speaks more to the potential toxicity of the work environment and/or insecurity of the coder.
Re: Am I Happy At Work? Analyzing my entire career
#30I don't want to sound an asshole, but I will sound an assholle nevertheless. I was damn happy as one can be at 3.5 years in my career. 10 years in, I feel like my happiness and awesomeness has been slowly consumed by corporate politics, unfair promotions and layoffs, bad work ethics and the such. I still like my work. I really really enjoy it when it's productive, and I still feel amazed to see the green checkmark on…
The only places I found where this was not the case were companies / teams in a state where their existence and viability depended on churning out high quality software. Crisis situations with pressing needs have the doubly added advantage that they are irrational choices for those consumed by corporate politics.
Crises are amplifiers of both positive and negative. I previously worked at a company in prolonged existential crisis, and while my team (working on a potential way out) and immediate management was great, there was a whole lot of backstabbing and irrational/incompetent/powerplay decision-making happening elsewhere in the continually shrinking org as people played musical chairs.
In the end, we delivered the project, but the company was acquired and everybody got laid off anyway...