3 ms·
Don't ask for 30 minutes tasks unless you have to (it's breaking the prod or something), it's inefficient for everyone involved. I'm in a team with a lot of le
by orwin 3y ago
Don't ask for 30 minutes tasks unless you have to (it's breaking the prod or something), it's inefficient for everyone involved.
I'm in a team with a lot of leeway. No one is counting my hours, no one external look at our productivity, but when we're needed, we don't have time to polish our code. When i have a '30 minute' task identified, I put it in our morning review, and ask if something adjacent should be done while I'm on the subject. If there is nothing, I'll still take the full day (except if it's a project I know really well, in that case I take half), and take half a day to skim the code, and another half to update it (small comment, version upgrade, code improvement, renaming variables).
Push your IC to do the same. Imo it's more time efficient, the new-ish IC use that time to learn the older code, and in the end you will have less legacy issues (unless you make a big change).
- rrr_oh_man 3y agoAny downsides to this approach, from your experience?
- orwin 3y agoI only have 10 month working like this, but yes. More linked to the code than to the approach, but sometimes I become easy to get lost on the 'I also need to fix this' and deliver the code _really_ late. My way of dealing with it is simple: at 4pm (I usually stop at 6), I take a 15 minutes break, talk with people (remote or not), make some tea and stuff, recenter myself. Then I check what can be merged into master before 6, scrap the commits I won't use, rebase the rest into one or two commits, then push and ask for review (once it was the '30 minute task' that pulled a lot of other shit, in this case I stopped and called the team lead/PM to redefine the card). Then if I still have time I do reviews, administrative work and probably end the day there. The nature of our team make that time management suitable.
- nmstoker 3y agoUnderstood. I never do unless it were breaking prod or breaking major business processes. Regular approaches, avoiding firefighting are essential to steady, stable states.
- nmstoker 3y agoSadly the need comes up too often.