31–40 of 63 posts
Working from home I can report that leaf blowers ruin my day pretty quickly. Some days it will be 4 hours of lawn equipment running.
Earlier quoted context omitted.
Ah yes, the “you touched it last” or the venerable “you brought us the bad news” schools of management. I also love the “we’ll do the meta-work that improves work velocity after the work is finished. Not before! We’re too busy for that now.”
Yep, we’ll optimize it later infra told me. I hear it still at my current employer. Optimize it later means you’re touching on a long ignored piece of negative tech debt.
These are the factors to me: * formal meetings, where I was, 30 hours of meetings a week. * Users wanting us to read their minds * bureaucracy, need to ask permissions to do one little thing * Jira
Using Jira slides into tracking all minutiae in Jira. People begin to think if it ain't tracked in Jira it didn't happen. You cant just do work now, you gotta write Jira first. I call it Jira diarrhea
Working from home I can report that leaf blowers ruin my day pretty quickly. Some days it will be 4 hours of lawn equipment running.
Earlier quoted context omitted.
It's amazing to me that someone's whole job could be running the scrum board, and that such a person would be questioning other people's contribution to the team.
I've had a really good scrum master. (Plenty of bad ones too). The really good one I could say something like "I started work on this item and realized that I'm actually missing a lot of context and information in the requirements. I need your help clarifying them" The scrum Master knew who to contact to get that information would set up a meeting, have the meeting without me if they thought they could do it or sched…
Working from home I can report that leaf blowers ruin my day pretty quickly. Some days it will be 4 hours of lawn equipment running.
Somewhat surprised by how candid the responses are - to have multiple of your survey subjects say they are seriously considering quitting! I enjoy that there's an entire blocker for "Teams isn't working". Personally my worst days are "I did a thing, rolled it out, found it was seriously broken, rolled it back, and now it's 6pm and that is what I did today". I couldn't see anything in their report that would cover tha…
These are the factors to me: * formal meetings, where I was, 30 hours of meetings a week. * Users wanting us to read their minds * bureaucracy, need to ask permissions to do one little thing * Jira
For me bad days are entirely about the people side vs the infra side. If some infra is down that hurt productivity but I don’t feel that negative about it. I’ll just do something else. Meanwhile if I have too many meetings or have to deal with dumb people or get criticised by someone that doesn’t understand what I’m doing that’s actually a bad day and has big negative effects beyond just that one interaction.
I once got criticised by the scrum coach(master?) that she had numerous complaints about me being not well suited to the team and was probably out of league and would fit a far more junior level. This of course gave me a very bad day and left a mark for almost 6 months. Needless to say, I later found out from my manager that, the scrum coach thought I was spending too much time on particular tickets and causing bad j…