News for hackers. Stuff that matters.
Re:Software engineering topics I changed my mind on by temporallobe on Saturday January 23, 2021 @10:09PM (#25888733)
Agree with this wholeheartedly. Standups are annoying but I have learned they are necessary, even as a very experienced developer. Sometimes things just cone up you wouldn’t otherwise know about and it encourages helpful, meaningful communication amongst the team.

What’s not helpful is when standups are treated like status reports. That’s not the purpose - even uber green newbies are responsible enough to do their work. The best kind of standups are those where you can feel free to discuss your blockers and simply state what you’re doing so the team has a general awareness if what’s going on and how/if it impacts them.

Re:Software engineering topics I changed my mind on by crescentfresh on Sunday January 24, 2021 @12:27AM (#25889558)
> not helpful is when standups are treated like status reports

> simply state what you’re doing

Honest question, what's the difference.

Re:Software engineering topics I changed my mind on by projectileboy on Sunday January 24, 2021 @01:05AM (#25889740)
In theory, no difference. In practice, good standups to me always feel like a casual conversation, and bad standups always feel like people speaking off a script like bad actors.
Re:Software engineering topics I changed my mind on by hordeallergy on Sunday January 24, 2021 @02:03AM (#25889968)
Why not just have casual conversations instead? Standups are one those things that people disagree on endlessly without discussing context - their worth depends on the team. On my current team they're worthless. I'd rather have casual conversation, but that's like squeezing blood from a stone. Departure planning underway.
Re:Software engineering topics I changed my mind on by ozim on Sunday January 24, 2021 @03:41AM (#25890409)
It should be, but not everyone on the team has to be confident. Not everyone has to be outspoken, not everyone has to have perfect pronunciation. Not everyone is able to structure their thoughts in 1 minute, even though they are able to work on complex systems.

What you want from "what you did yesterday, blockers, what you will do today" script is a framework for conversation starter, conversation scope and having something that you can prepare before. Some people can come up with it on the spot and some people think they should come up with it on the spot.

That is why I hate having standup right at the start of the day like 9.00, I usually have to get at least 20 mins to get check up what I finished yesterday and start picking up something new, going through priorities.

Re:Software engineering topics I changed my mind on by OJFord on Sunday January 24, 2021 @06:36AM (#25891233)
Personally I'd like a stand-up where it's ok not to have anything to say, like yeah, WIP, no problems, no blockers (except being here talking about it instead of doing it..!) etc.

Fully agree I would prefer it later. Not just 20min, I typically start ~1h before ours anyway, but it hangs over me all that time. I'd like to spend most of the day working on something and then stand-up in the afternoon, I'd be more likely to have an issue someone could help me with, or otherwise on my mind to discuss.

Re:Software engineering topics I changed my mind on by ProZsolt on Sunday January 24, 2021 @11:58AM (#25893532)
Yeah having standup in the afternoon is great. At my last company I worked with Americans from the EU. My standup was at ~4pm. My "last day's work" was still fresh and still had ~2 hours to resolve blockers.
Re:Software engineering topics I changed my mind on by loopz on Sunday January 24, 2021 @06:36AM (#25891236)
Careful what you wish for. In open landscapes and in meetings with business side, there's endless pointless chatter about everything else but doing their job. I'm not a devotee to overwork and squeezing blood out of stone type of worker. However, the directionless chatter, general incompetence, lack of inquisitiveness and awareness become energy-draining over time.

Status report is when a team say the same things every day and every week, nothing changes and there's nothing new to be learned. This is Waste.

Daily scrum is meant to encourage collaboration, inspiration and brief sharing of information. However, when driven by business needs alone, it becomes another pointless status report. On the flip side, if daily scrum takes off, it should be allowed to continue as a new meeting afterwards, but is also a sign that there's not enough coherency in the group with the current practice.

Re:Software engineering topics I changed my mind on by kenhwang on Sunday January 24, 2021 @02:20AM (#25890059)
Some people just don't like casual conversation and wouldn't initiate conversation on their own. If you have enough of those types, no communication wold happen. Ad-hoc conversation tends to be interruptive which is not desirable for people on maker schedules.

Either way, standups is just one communication strategy. Pick the communication strategy that works with the style your team feels comfortable with. There's rarely one solution fits all when it comes to communication.

Re:Software engineering topics I changed my mind on by projectileboy on Sunday January 24, 2021 @03:20AM (#25890337)
It’s a good question that every team should ask themselves rather than just blindly follow some scrum book. One reason that standups can be worthwhile is if your product managers are hard to get a hold of (which is common), it’s a guaranteed time when you can ask them some questions. But your mileage may vary.
Re:Software engineering topics I changed my mind on by BurningFrog on Sunday January 24, 2021 @10:50AM (#25892962)
> Why not just have casual conversations instead?

Scheduling it daily is how you have these casual conversations.

Re:Software engineering topics I changed my mind on by dragontamer on Sunday January 24, 2021 @01:48AM (#25889913)
> In theory, no difference. In practice, good standups to me always feel like a casual conversation, and bad standups always feel like people speaking off a script like bad actors.

As someone who did sales early in my career... acting off of a script correctly feels like a casual conversation to the one you're selling to.

If your script-reading is bad, that's because you haven't practiced enough. Having a script isn't necessarily a bad thing, and is in fact very useful in keeping focus.

Re:Software engineering topics I changed my mind on by emteycz on Sunday January 24, 2021 @03:14AM (#25890312)
Programmers are not salesmen, and this is not in their control, the scrum master often demands a question/answer type of conversation.
Re:Software engineering topics I changed my mind on by dragontamer on Monday January 25, 2021 @10:17AM (#25904071)
The more I grow into senior engineer / more leadership positions, the more and more my sales training from my youth comes in handy.

Every meeting you have with people has a goal (otherwise, you wouldn't meet with them to begin with!!). Maybe the goal is to gather requirements, or maybe the goal is to convince them to do something for you. The latter is 100% sales. None of us exist within a vacuum, we rely upon APIs or libraries or frameworks to do things. And if these APIs / libraries / frameworks are company / organization specific, you'll need to convince their lead engineer that your change is worthwhile to adapt.

Re:Software engineering topics I changed my mind on by zygy on Sunday January 24, 2021 @02:30AM (#25890106)
If one had to troubleshoot a bad standup meeting, how might you turn one that feels more scripted into one that feels more natural?
Re:Software engineering topics I changed my mind on by corty on Sunday January 24, 2021 @06:02AM (#25891047)
Everyone is standing up, sitting down only as a medical exception. Strict time limits. Everyone gets 30s, extension only of there is a question from the crowd. For the topics "yesterday, blockers, today" just make it 3 "words" for yesterday and today each. Like "yesterday customer contact and small bugs, today think about customer suggestions, maybe with Christine" at most. Only the blockers deserve a full sentence maybe.
Re:Software engineering topics I changed my mind on by lordgrenville on Sunday January 24, 2021 @04:35AM (#25890648)
I would suggest the difference is if you feel pressure about your response. Is it ok to pass, or say something like "still working on same issue I discussed a couple of days ago"? If not, it's less like a casual conversation, and more like justifying your time.
Re:Software engineering topics I changed my mind on by paledot on Sunday January 24, 2021 @10:04AM (#25892593)
I would say that's perfectly okay, but not for the reason you think. If your status is "still working on the same issue", your team should respond with "how can we help?". If your status doesn't change, that's a sign that something's wrong at some level, whether it's because you're stalled or because the issue was poorly scoped or poorly defined.
Re:Software engineering topics I changed my mind on by navaati on Sunday January 24, 2021 @12:16PM (#25893699)
What about the fact that some stuff just takes time, is that not conceivable to you ?
Re:Software engineering topics I changed my mind on by fragmede on Sunday January 24, 2021 @07:34PM (#25897719)
Stand up is not (supposed to be) oppositional/conflict driven (but there are many toxic workplace cultures). Obviously some things "just take time", but what is the stuff that's taking up time? Assume it's all developers in the room and we're all familiar with the code base. Are you doing a stupid boring refactor of a thing tat "just takes time" but someone on the team wrote - and they have thoughts on pitfalls to avoid if they were rewriting it? Are you banging your head against an elusive bug that "will just take time" to tease out? The point of the standup is to shine light on any number of stupid pitfalls that every developer, even (especially) seasoned developers get stuck on, have dealt with in the past, and can give guidance with.

If you're just cargo-culting having a daily 15-minute meeting under the guise of agile or whatever, and it's just a status meeting, then cancel it, until after people learn to have a proper stand-up. Waking up just to go to a meeting and report "I'm still working on the thing", is a waste of everyone's time, and is a meeting that would have been better off as an email. (Provided people can send that email, which is not always possible, and is an entirely different topic.)

Re:Software engineering topics I changed my mind on by crescentfresh on Monday January 25, 2021 @11:20AM (#25904930)
> your team should respond with "how can we help?"

this would kill the meeting at my company, it would go off the rails as a thing that everyone is present for and listening to. Moving it "offline" - as is often done - only occurs once it has gone sufficiently off the rails in the first place. Not saying there's anything wrong with this process, just pointing out it's counter to the "keep it short" discussion happening in this thread.

Re:Software engineering topics I changed my mind on by dirkt on Sunday January 24, 2021 @04:19AM (#25890567)
status report = you have to take responsibility for what you have done (or not done)

state what you are doing = what happens automatically if you sit in the same office with other programmers: you know what they are working on, you know if they are stuck with something because they usually just ask aloud, etc.

Re:Software engineering topics I changed my mind on by BurningFrog on Sunday January 24, 2021 @10:54AM (#25892994)
Not questioning your experience, but I've sat in a lot of engineering offices and had very little clue what the people around me were working on.

Standups really improved that aspect for me.

Re:Software engineering topics I changed my mind on by iovrthoughtthis on Sunday January 24, 2021 @07:13AM (#25891403)
In a standup you should be able to say “i’m not really doing anything atm”, “i’m writing tests for x”, “i’m documenting y” without fear of someone asking you justify yourself.
Re:Software engineering topics I changed my mind on by pvinis on Sunday January 24, 2021 @06:08AM (#25891078)
we use these three questions: - what you did? - what will you do? - do you have any blockers? usually the blockers part is useful to know if anyone is having any issues with anything that others could help.
Re:Software engineering topics I changed my mind on by spockz on Sunday January 24, 2021 @11:51AM (#25893456)
What you did is typically not useful to share. This can be seen on the scrum board. What you do want to share is your experience, what was hard/easy/remarkable or when you are stuck. Just reporting what you did goes quickly to defending your hours or something.
Re:Software engineering topics I changed my mind on by edumucelli on Sunday January 24, 2021 @09:07AM (#25892118)
I do not understand why people have to wait to discuss the blockers? Discuss a blocker whenever you have one.
Re:Software engineering topics I changed my mind on by williamdclt on Sunday January 24, 2021 @09:45AM (#25892408)
Wouldn't it be great if people were perfectly rational agents, gifted with objectivity vision and purged of all bias?

Of course you're right, you should discuss blockers whenever you have one. But people don't want to discuss blockers (or don't want to discuss at all), or don't identify something as a blocker, or would like to solve it themselves, or want to "protect the team" from this information, or think they'll get it resolved sooner without extra communication, or expect that they'll disagree on the course of action, or feel ashamed of having this blocker, or any other reason out of a hundred.

They won't rationally formulate it like I did just above, but it's just what people do: they get biased and their brain doesn't take the most rational course of action. A personal bias: I tend to prefer solving uncertainties by writing more code than talking to people. This is a stupid thing to do and I actively fight against it, but the fact is that I naturally tend to favour the "code" approach to the "communication" approach: standup forces to surface the problem and people can challenge me.

Re:Software engineering topics I changed my mind on by dagw on Sunday January 24, 2021 @12:17PM (#25893702)
Discuss a blocker whenever you have one.

But that would require me interrupting one or more people in the middle of whatever they are doing and possibly ruining their flow. Unless there is a very tight deadline, work on something else and bring up your blocker when you know the relevant people have time to listen.

Re:Software engineering topics I changed my mind on by greenyoda on Sunday January 24, 2021 @02:28PM (#25894963)
I also prefer not to interrupt others or to be interrupted. But if you send your problem as an e-mail, people can answer at their convenience.

My own experience is that frequently, the act of thinking about an issue long enough to be able to formulate a coherent e-mail about it makes the solution jump out at me before I even send the message.

Re:Software engineering topics I changed my mind on by dagw on Tuesday January 26, 2021 @04:20AM (#25913903)
In truth I normally do both. I'll send an email flagging that there is a blocker I want to discuss at the next relevant opportunity.

And I've also found that writing that email leads to me solving the problem at least 50% of the times (same with writing to forum posts of StackOverflow questions)

Re:Software engineering topics I changed my mind on by thw0rted on Wednesday February 03, 2021 @07:45AM (#26013130)
It sounds like your team doesn't have a chat tool (Slack, Teams, etc), or if they do, they're using it wrong.
Re:Software engineering topics I changed my mind on by BurningFrog on Sunday January 24, 2021 @10:56AM (#25893007)
If it can't wait, sure, ask for help right away.

But there are levels of blockers. Most are not emergencies.

Re:Software engineering topics I changed my mind on by m1gu3l on Sunday January 24, 2021 @11:35AM (#25893315)
this is legit. sometimes i feel like i wait a little too long to gather notes or brainstorm possible solutions when i could probably get that going faster by involving a colleague and tag teaming it. it is a balance i am trying to work on because i feel like i “don’t want to bother anyone” a lot.
Re:Software engineering topics I changed my mind on by cygned on Sunday January 24, 2021 @09:11AM (#25892152)
Standups allow you to see blockers before they are there just by having a bigger picture of what’s happening.
Re:Software engineering topics I changed my mind on by conradfr on Sunday January 24, 2021 @01:05PM (#25894132)
I think it's the role of the lead dev to help newbies and coordinate work if needed. It can also be discussed at some meeting where the PO would present future tasks.

I don't see that as an intangible rule, it's all project and team dependent. And I see how in a remote world a "standup" can be beneficial.