Earlier quoted context omitted.
> If the meeting is on a calendar ahead of time it's not really an interruption. Knowing about it doesn’t make it interrupt flow any less, unless you just avoid the kind of work that would require flow around it, which still imposes the same kind of productivity impact on intellectual “making” workers. [0] [0] related: http://www.paulgraham.com/makersschedule.html
I don’t know about you guys, but I can’t really keep a sustained bust going for 8 hours anyway. Even if I had no meetings at all, I have to stop for the restroom, tea, food, or even just to give my body a break.
Embrace the Grind
201–210 of 320 posts
Re: Embrace the Grind
#202When I joined a mentoring program targeted at recent college grads, I expected to be teaching things like interview prep, resume writing, negotiation skills, communication skills, and how to deliver results in a workplace. For about half of the mentees, that's roughly true. However, for the other half much of my mentoring ends up being about time management, following through on commitments, and putting in the effort…
Re: Embrace the Grind
#203Re: Embrace the Grind
#204Re: Embrace the Grind
#205Earlier quoted context omitted.
I don't understand why software architect isn't a position in any of the new startup culture tech businesses. The advantage of having an older, very wise and very experienced engineer whose job it is to document, plan and understand all the moving parts of your project would have been invaluable instead of expecting all the engineers who are stressed about hitting deadlines and chasing down memory leaks to do that wo…
The people who do this job at large companies are called Staff or Principal engineers. One reason startups might be less likely to have them is that they are extraordinarily expensive.
The wrong person in this type of role at a smaller company can things back significantly.
Re: Embrace the Grind
#206Re: Embrace the Grind
#207Earlier quoted context omitted.
This resonates with me deeply. I can barely get work done most of the time. My "solution" is to leave a company before people get too frustrated with me. Changing companies frequently nets me better pay and more promotions than my harder-working peers, but I haven't felt fulfilled by work in a long time. What do you tell these mentees? What would you tell someone a bit further along in their career who still has the…
> what would you tell someone a bit further along in their career who still has the same problems? If it's been going on for a while but you are otherwise successful at the work you're doing, the best advice I can give you is to ask a trusted third-party (friend[0], therapist/mentor that you've worked with for a while) and ask them "why, do you think, I have these problems?" Obviously, this has to be someone who won'…
Good to know I’m providing a valuable service
Re: Embrace the Grind
#208In a bigger team, a big second reason why these kinds of very uncomfortable tasks aren't done is that they also often don't produce immediate business value. You then have double resistance: the PO wants features from you and grinding is boring.
The people who first get to a position where they can spend the time and then do spend the time (instead of doing the even more fun tasks), are worth their weight in gold.
Re: Embrace the Grind
#209> For example, I once joined a team maintaining a system that was drowning in bugs. There were something like two thousand open bug reports. Nothing was tagged, categorized, or prioritized. The team couldn’t agree on which issues to tackle > I spent almost three weeks in that room, and emerged with every bug report reviewed, tagged, categorized, and prioritized. Honestly, this is one of those traps a team can fall in…
Imagine how the kernel and operating system feels...
Re: Embrace the Grind
#210Earlier quoted context omitted.
> Which is why it's so utterly toxic that corporate America runs on an interrupt driven system, with meetings sprinkled carelessly across engineer calendars. I agree with this statement and your other points. I’ve noticed a more insidious variant of this behavior: the expectation of interruptions. Some groups have such frequent priority shifts and/or a culture of fire fighting or door knocking such that even with a r…
I think you can blame "agile thinking" for that and the general laziness in product planning which is so typical of the last 10 years. We went from recognising that requirements may change after planning to zero planning and telling developers what's the next priority for the day, day by day. This lack of planning and product definition is also what drives the lack of documentation, which is another big problem in 20…
This is a separate higher level of abstraction backlog where the possible work for the next 1-X sprints are planned and defined ready for the team take "tickets" into their backlog.