News for hackers. Stuff that matters.
Re:Software engineering topics I changed my mind on by aerovistae on Saturday January 23, 2021 @09:17PM (#25888366)
Have never agreed with a blog post more. Every single bullet point, 10/10.

Okay, okay, actually I have one qualm~

> Standups are actually useful for keeping an eye on the newbies.

Unfair. Standups are useful for communication between a team in general, if kept brief. If senior engineer X is working on Y and other engineer M has already dealt with Y (unbeknowst to X), it's a great chance for X to say "I'm currently looking for a solution to Y" and for M to say "Oh I had to solve that same problem last month!"

Seniority has nothing to do with this. Communication/coordination/knowledge-sharing matter at all levels.

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.

Re:Software engineering topics I changed my mind on by H8crilA on Saturday January 23, 2021 @09:30PM (#25888455)
It's especially useful with the newbies, as they are most likely to attempt to reinvent the wheel, due to lack of knowledge/experience.

Also, in the age of WFH stand-ups are a replacement for lunch conversations, the most rudimentary block of team building. I think that if you're not doing stand-ups or something like that since March you're probably losing team coherence.

Re:Software engineering topics I changed my mind on by austincheney on Saturday January 23, 2021 @10:45PM (#25888983)
There is not much wrong with reinventing the wheel. It is a less efficient use of time that often results in a beneficial serendipity. The opinion that reinventing the wheel is somehow a supremely evil satanic ritual is what prevents original solutions and allow expert beginners to become shitty decisions makers.
Re:Software engineering topics I changed my mind on by joatmon-snoo on Sunday January 24, 2021 @08:26AM (#25891832)
Re-inventing the wheel can be useful for learning, but can have very real costs, often in the form of production outages.

* "You can usually use user metadata field X for billing" - except for those users for whom field X actually maps to something else, for tech debt reasons. (Is it stupid and bad? Yes. Is anyone going to be able to fix it this year? No. Is this going to result in Very Big Customer TM getting mad? You Betcha.)

* "Oh, I'll just roll my own fake of Foo" - congratulations, now anyone looking for a fake needs too decide between yours and the other one. (Yes, this is highly context dependent, but the moment you have multiple fakes in common/util libraries this usually starts being a problem.)

* "I can just use raw DB writes for this, because I don't want to learn how to use this API" - except the abstraction exists because it guarantees you can do safe incremental, gradual pushes and roll back the change, whereas your home-rolled implementation had a small bug and now the oncaller needs to do manual, error-prone surgery on the backup instead of the usual undo button built into the API. (Oh, and legal is going to have a field day because there's no audit record of the raw writes' content.)

Cargo-culting is bad, yes, but reusing existing abstractions is often important because they handle (or force you to handle) the various edge cases that someone learned about the hard way.

And of course, if you find a bug in the existing abstraction, well, congratulations- you just found a repro and root cause for that infamous support case that's been giving everyone data integrity nightmares for months.

Re:Software engineering topics I changed my mind on by austincheney on Sunday January 24, 2021 @09:22AM (#25892221)
> often in the form of production outages

Completely unrelated. If you have production outages resulting from new code you have serious gaps in your certification process, especially so if the new code covers existing process/requirements. You are probably insecurely reliant upon dependencies to fill gaps you haven’t bothered to investigate, which is extremely fragile.

The benefit of code reuse is simplification. If a new problem emerges with requirements that exceed to current simple solution you have three choices:

1. Refactor the current solution, which introduces risk.

2. Roll an alternative for this edge cases and refactor after. This increases expenses but is safer and keeps tech debt low.

3. Roll an alternative for this edge case and never refactor. This is safe in the short term and the cheapest option. It is also the worst and most commonly applied option.

Re:Software engineering topics I changed my mind on by clooless on Sunday January 24, 2021 @04:37PM (#25896358)
> If you have production outages resulting from new code you have serious gaps in your certification process

If you have production outages every week, yeah. But no organization is free of production outages. When they do happen (I said when, not if) it matters a lot if you used standard libraries, code that is plugged into the infrastructure, and the like, and not hand-rolled cowboy code

Re:Software engineering topics I changed my mind on by austincheney on Sunday January 24, 2021 @09:07PM (#25898267)
> it matters a lot if you used standard libraries

Why? From a security perspective, an outage is a security matter, the remediation plan is what’s important.

Re:Software engineering topics I changed my mind on by Twisell on Saturday January 23, 2021 @11:42PM (#25889339)
You are totally right but probably assuming you have a top notch and easily discoverable documentation that can guarantee that newbies won't spend 15 days reimplementing "that bash script you need once a year or so" that do the job in 2 minutes.

However even if this case you might get lucky and end up with a new script that do the job in 30 seconds and everybody in the team have learn that documentation is very important.

Re:Software engineering topics I changed my mind on by H8crilA on Saturday January 23, 2021 @11:52PM (#25889392)
It's a matter of balance. No simple rule of thumb exists.

Sometimes it results in a much better solution, great! Sometimes it's a new wheel but with more awkward square-ish corners. Sometimes (and this is the worst because it's hard to explain) it is actually better but still likely has been a waste of the engineer's time - high cost vs low benefit, also often cooccurs with lack of team's capacity to maintain the new thing.

Re:Software engineering topics I changed my mind on by mark-r on Sunday January 24, 2021 @12:27AM (#25889562)
We decided early on that a daily scrum was just too frequent to be effective for our team, so went to 2x per week. When we started working from home, we added a "keep in touch" meeting for the other 3 days of the week just to stay connected.
Re:Software engineering topics I changed my mind on by GordonS on Sunday January 24, 2021 @10:28AM (#25892783)
Yep, not being dogmatic about standups having to be daily, or indeed about any process, is invariably a win - do what works for the team!

I'm working in a small team just now, just 5 of us, and a short, daily standup is working well for us - and it's usually finished in 7 minutes or so.

In my last project (where I wasn't leading the standups), the teams were bigger, 10 people in each, and they went.on.forever. Neither the scrum master or PM were strict at curtailing them or keeping them relevant. Everyone hated it.

Re:Software engineering topics I changed my mind on by mixologic on Sunday January 24, 2021 @12:36AM (#25889608)
Our standups (for a team of four) are about 15 minutes. Then we just leave the zoom on and co-work together out loud for an hour or two. It's pretty priceless the stuff that comes up during that time.
Re:Software engineering topics I changed my mind on by lydon on Sunday January 24, 2021 @11:34AM (#25893303)
Always thought this will be useful, but never had a chance to experience it. What kind of stuffs come up?
Re:Software engineering topics I changed my mind on by avereveard on Sunday January 24, 2021 @04:07AM (#25890517)
I'm glad I've reinvented the wheel that many time as a junior, it let me learn why some framework and some solutions are the way they are, and made it extremely easy to pick up third party solutions later on
Re:Software engineering topics I changed my mind on by throwaway2245 on Sunday January 24, 2021 @06:53AM (#25891307)
We'll never know the counterfactual, but in my opinion:

You could have learned the same thing more efficiently, with more support for why you didn't need to reinvent the wheel.

Re:Software engineering topics I changed my mind on by paledot on Sunday January 24, 2021 @10:11AM (#25892634)
I've been a professional software developer for ten years, and I'm on a hiatus right now. One thing I've been doing with my time is reinvent a bunch of wheels, implementing broken clones of this library or that algorithm, and I've gained a tremendous amount of understanding of what's going on behind the scenes of tools I'd been using for years. So yeah, it's a valuable learning tool to build with your own hands.

Also, a valuable guide when deciding whether to write code yourself or introduce yet another library to your dependencies.

Re:Software engineering topics I changed my mind on by datavirtue on Sunday January 24, 2021 @09:06PM (#25898260)
Before getting sucked into the enterprise world, I reinvented a bunch of wheels and this indeed gave me a deeper understanding of the inner workings of various frameworks and technologies. I noticed that my colleagues who had ten years or more on their resume rarely had any idea what I was rambling on about or the basis for the things they were using.

Their were so busy trying to get stuff done that they never had time to explore. I don't mean blog post or tutorial explore, I mean weeks and weeks of implementation and testing of patterns and low level engineering. Building database engines from scratch or writing a compiler or a distributed message broker, for instance.

Re:Software engineering topics I changed my mind on by systemvoltage on Saturday January 23, 2021 @10:45PM (#25888986)
Let’s be honest, stand ups are there so we can get together as a team. Otherwise, engineers would be heads down working on their own things.

Benefits of “Oh I yea I’ve worked on the same thing before” are usually realized outside of stand ups in over the shoulder chats or slack.

Stands ups are a waste of time. There, I said it. But, I like them, especially if you have a fun team.

Re:Software engineering topics I changed my mind on by ffhhj on Saturday January 23, 2021 @11:13PM (#25889159)
Agreed!

Stand ups are a teather play to make the client believe a project is moving forward, while team members use their own private channels to talk about the real work.

Re:Software engineering topics I changed my mind on by Clubber on Saturday January 23, 2021 @11:08PM (#25889118)
For our team, we just do a weekly biz/dev meeting, then break into a pure dev meeting every Tuesday morning. The process takes about 30min - 60min a week and we can go into depth when needed. Plan the week and go do what we do. It works great for our small 5 man team.

Daily meetings seem excessive to me, even if they only last 5 minutes.

Re:Software engineering topics I changed my mind on by rektide on Saturday January 23, 2021 @11:14PM (#25889169)
> Standups are useful for communication between a team in general, if kept brief.

Just once I'd like to work for a company that tries to stay in communication without so many explicit/manual/sync check-in gates.

* No stand-up, engineers required to write a 250-words or less blog post 2+ times a week.

* No announcing PRs, reviews &c to each other. Make watching the board a habit, one you "pull" rather than that is pushed to you. Or use a company provided chat-bot/tool to help surface changes as they happen, if you need that. The issue tracker should better dashboard whatever activity is happening, in general- indicate branch updates, pr changes, &c, clearly, across the board.

There's some value to using social processes to radiate all the changes happening, but I'd really like to see some camp out there that makes a go at mechanizing themselves. I think there are a lot of interesting possibilities, more enduring & valuable forms of communication that we have failed to even begin to explore.

Re:Software engineering topics I changed my mind on by jbay808 on Sunday January 24, 2021 @01:22AM (#25889808)
A place I used to work had engineers documenting their work essentially in the form of a blog. It was actually really a useful habit, and reviewing the project blogs once each week made it really easy for me to find cases when I could help a colleague who was working on something I'd had experience with before.
Re:Software engineering topics I changed my mind on by anaerobicover on Sunday January 24, 2021 @01:39PM (#25894479)
I'd venture that the parent was talking about engineers "documenting" their work for managers, whereas I think you mean documentation for other engineers. Very different audiences and thus different things to say. (And widely different lifespans for the information.)

The latter no doubt is hugely useful (I'm on a long slow effort myself to get my co-workers to document their work more robustly). But writing status reports for managers/PMs on a weekly basis is, in my not so humble opinion, a complete waste of time for the company, and a sign of poor organization.

Re:Software engineering topics I changed my mind on by rektide on Sunday January 24, 2021 @02:11PM (#25894787)
I was hoping both purposes would be served, at this mandatory level.

I would adore any engineer who writes more blog posts walking through what they're up to more technically.

How do you feel about every-day stand ups as a means for managers/PMs to check in on employees? My own impression has been that this is at least 50%+ of the reason for stand up, and to me, I'd far prefer periodic write-ins, rather than ephemeral, undetailed, synchronous communication.

Re:Software engineering topics I changed my mind on by Shorel on Saturday January 23, 2021 @11:10PM (#25889132)
Every time I mention the goodness of pencil and paper I get downvoted by so many youngsters.

Some people will always disagree about some points. It's in their nature.

Re:Software engineering topics I changed my mind on by User23 on Sunday January 24, 2021 @01:10PM (#25894185)
Some of the greatest scientific work of all time was done on paper. Doing algorithm design on paper really brings home that you’re working with a mathematical object that just happens to have a mechanical interpretation.
Re:Software engineering topics I changed my mind on by zbobet2012 on Saturday January 23, 2021 @11:12PM (#25889149)
I disagree. The best medium is a whiteboard or a blackboard :p.

(Really though, something about paper makes me afraid to "commit" things which make the pieces of paper no longer usable. Something made to be erased seems to be the trick for me).

Re:Software engineering topics I changed my mind on by Shorel on Saturday January 23, 2021 @11:51PM (#25889388)
And I find a whiteboard a bit more intimidating. It kind of implies performing your writings in public.

A notebook is a very personal thing. =)

Re:Software engineering topics I changed my mind on by tribaal on Sunday January 24, 2021 @03:51AM (#25890452)
I recently switched from a very whiteboard/paper heavy workflow to using a reMarkable tablet.

Holy shit this thing is good.

It's like an infinite notepad/whiteboard that auto syncs to the cloud, lets you define page layout templates, and renders PDFs and ebooks.

I've had it for just a few weeks and it's already the favorite pice of tech I own.

Re:Software engineering topics I changed my mind on by azemetre on Sunday January 24, 2021 @12:05PM (#25893582)
I use a rocketbook [1] to do something similar. They recently came out with a legal pad version and I love it. It's a little more work to convert notes into PDFs (have to manually take a picture) but it's a cheaper solution.

I've never used a reMarkable tablet but there's something off putting for me about using tablets to take physical notes. IDK how to explain it, drawing apps are fine but physically writing symbols, or making charts, or writing notes? It just feels off. I like the rocketbooks because it's just a fancier way to implement OCR for handwritten notes and the actions between paper and their product is nearly identical for me.

Maybe the reMarkable is able to handle this, just never tried it. It does look better than using something like an iPad for note taking.

[1] https://getrocketbook.com/

Re:Software engineering topics I changed my mind on by tribaal on Sunday January 24, 2021 @12:36PM (#25893867)
I know what you mean with taking notes on a tablet, but the reMarkable is very good at that aspect. Nothing at all like an iPad: the e ink makes it look like paper, and even the tip of the (passive) stylus feels like writing on actual paper (it "scratches" ever so slightly, even if it obviously doesn't actually scratches the screen).

It also doesn't do fancy stuff: it's black and white, and doesn't do OCR on device at all. It's basically just a notepad that is synced to your other devices (without the manual picture step, and you can get svg instead, etc)

To me it's too a notepad what a kindle is to books: a single purpose device that does it's job very well.

Oh yeah, and about two weeks of battery life is pretty good.

I realize I'm starting to sound a bit like a sales rep... but I'm just a fanboy user.

Re:Software engineering topics I changed my mind on by Shorel on Monday January 25, 2021 @10:28AM (#25904241)
I also have a rocketbook. It is an amazing mix of low and high technology, for a very cheap price.
Re:Software engineering topics I changed my mind on by kettro on Saturday January 23, 2021 @11:30PM (#25889255)
To this end, I have a small, paper-sized whiteboard that I can scrawl onto on hands at all times. I bought a couple packs of the ultra-fine expo markers, and it’s been a boon. Great for quickly noting things down that don’t need to last.

Having both is important, though: you need to be able to preserve the things that matter, that you may need later on.

Re:Software engineering topics I changed my mind on by Shorel on Monday January 25, 2021 @10:30AM (#25904284)
You can use the rocketbook app. No need to buy the notebook.

https://getrocketbook.com/

Re:Software engineering topics I changed my mind on by mark-r on Sunday January 24, 2021 @12:29AM (#25889581)
That's why phones have cameras.
Re:Software engineering topics I changed my mind on by bostonvaulter2 on Sunday January 24, 2021 @05:50AM (#25890989)
I've recently replaced this with my reMarkable tablet. Pricey but I love it as a paper replacement. Very open and hackable too (if a bit fragile).
Re:Software engineering topics I changed my mind on by axaxs on Saturday January 23, 2021 @10:00PM (#25888674)
Same here. Well everything except retrospectives, which I think are generally wasteful or better done in small pieces. Was afraid I wouldn't see something about overdoing microservices, but I think the monolith line covers it enough.
Re:Software engineering topics I changed my mind on by eyelidlessness on Saturday January 23, 2021 @10:56PM (#25889058)
Retros should be like recall elections: always available, never scheduled, with a high but achievable barrier to entry and specific veto principles both ways. The point of a retrospective is "something big happened and we should learn and adapt". They shouldn't be routine, because most weeks/sprints, nothing that big happened (or something that big happened too frequently/urgently to wait for a calendar). They shouldn't be too hard to trigger, or you're never going to get one (or results from one). The best process for this is "shit goes down and you should make appropriate dedicated space for it".

Edit to add: I want to emphatically contradict my metaphor in one way, which is that retros should be exactly the opposite of a recall election in terms of identifying/naming/assigning fault. They should be about identifying good/bad outcomes and good/bad patterns, but not about pointing fingers at or casting aspersions on people.

Re:Software engineering topics I changed my mind on by kenhwang on Sunday January 24, 2021 @02:32AM (#25890121)
We have an retro automatically if we have a production outage. This doesn't mean its an everyone must attend in-person meeting. Most of the time its just a writeup.

Otherwise, a lead or multiple senior engineers just exercises their judgement on when something serious enough happened that the team needs to be aware of or act on.

Re:Software engineering topics I changed my mind on by pseudalopex on Saturday January 23, 2021 @11:09PM (#25889128)
It shouldn't take something big to reflect on what went well and what didn't. Or suggest a change.
Re:Software engineering topics I changed my mind on by axaxs on Saturday January 23, 2021 @11:14PM (#25889168)
Most teams are silo'd like it or not. A backend guy or two, a frontend guy or two, layers of management, product, qa, ops people.

If I'm a backend person, I'll talk to the backend guy person if we messed up. If the frontend guys are lamenting among themselves, I find myself not really caring and time being wasted.

There's zero reason that teamwide changes can't be proposed for discussion via email or slack.

Re:Software engineering topics I changed my mind on by arbalist on Sunday January 24, 2021 @01:14AM (#25889784)
It doesn't take domain knowledge to take responsibility for improvement. If your retros are taken up by lamentation maybe you should try to bring more focus.
Re:Software engineering topics I changed my mind on by pseudalopex on Sunday January 24, 2021 @08:10AM (#25891741)
Lots of companies have teams for back end, front end, ops, etc.

Slack is a good way for things to get lost in the noise or decided by whoever is in the channel at the time. Email doesn't have those problems but discussions can stretch out over days. And people speak more freely when there isn't a written record.

Re:Software engineering topics I changed my mind on by eyelidlessness on Sunday January 24, 2021 @03:35AM (#25890387)
You’re right it shouldn’t. Those don’t need a recall election. Just a normal one. Elections should be like sprints too.
Re:Software engineering topics I changed my mind on by ncann on Saturday January 23, 2021 @11:13PM (#25889164)
Agree about retrospectives. It's such a waste of time. Most of the time it's just there so that the scrum master can show off their new game and try to justify their usefulness.
Re:Software engineering topics I changed my mind on by tikhonj on Saturday January 23, 2021 @10:56PM (#25889060)
A bit of a controversial take: if you need standups for this sort of communication, your work and work culture are way too siloed. With a flexible and collaborative culture, people will communicate these things naturally as part of doing their work. Issues that come up will get addressed as needed when they come up. If something is important, why would you wait for tomorrow's standup? If something isn't important, why are you dedicating an inflexible daily meeting to talking about it?

If your team is having the sort of communication problems standups are supposed to solve, it's a symptom of a deeper issue and standups are a bandaid solution. If your team already works collaboratively, standups are pure overhead at best and actively counterproductive at worst. It's easy to get into the bad habit of waiting for a standup to bring up important issues, which loses time and context. Worse yet, chances are the standup has too many people and not enough time to discuss anything in detail—I've seen so many standups where any actually useful conversation would be caught, stopped and moved to a different venue. You end up with a pro forma meeting where most of the information isn't useful to most of the attendees, but still breaks up people's schedules and focus.

In my experience, an emphasis on standups goes hand-in-hand with a view of engineering work as a ticket factory: individuals get a ticket off the queue, work just on that, get it done as soon as possible and pick up another ticket. I think that correlation is not a coincidence.

Re:Software engineering topics I changed my mind on by Chris_Newton on Sunday January 24, 2021 @01:36AM (#25889857)
That seems like a reasonable concern to me, and something that could apply to almost any communications that are on a regular schedule, whether it’s a daily team meeting or an annual review with your boss.

My father said something to me when I was nervous before my first annual review in my first job, and it has stuck with me ever since: nothing anyone says in that review should ever be a surprise. Whether it’s good or bad, if your management are doing their job, everyone who needs to know about it should have known when it became relevant, not on the anniversary of your employment.

I suspect there is more value in some types of regular but short technical meeting at the moment, when many colleagues aren’t in close proximity at work and ad-hoc informal discussions are less likely to serve the same purpose. But as someone who’s primarily worked from home for years, I’d usually still prefer to arrange a group call or physical meeting with whoever actually needs to be there when there’s something specific to discuss, rather than assuming in advance that any particular tempo will be the right one.

Re:Software engineering topics I changed my mind on by closeparen on Monday January 25, 2021 @11:59PM (#25912741)
When trying to schedule on an as needed basis, the next time slot where everyone is available together could be in several weeks. Especially if one or more participants are business types with impossible calendars. Standing meeting reserves a time slot and guarantees a topic can be discussed within N business days of becoming important. If there is nothing for the agenda that day then you cancel it and everyone gets some free time.
Re:Software engineering topics I changed my mind on by ncann on Saturday January 23, 2021 @11:09PM (#25889126)
While you have a point, it's not that rare for someone to be blocked on a hard issue for a day or two, even having talked to someone, then bring that up at the stand-up. The one you talk to may not always have the solution, and it may be someone else in the team at large.
Re:Software engineering topics I changed my mind on by pseudalopex on Saturday January 23, 2021 @11:58PM (#25889426)
Email works great for that.
Re:Software engineering topics I changed my mind on by jayd16 on Sunday January 24, 2021 @03:15AM (#25890314)
Better is better but a daily stand-up provides a common, catch all meeting with the entire team blocked off to participate.

Why wait? Well you could should tap(which we all hate), or you could email, ...or you could do something else in the mean time and bring it up in the daily.

Lets say you're blocked but don't know who to talk to? You could end up playing email tag or out on a few man hunts as you jump from team member to team member looking for who knows what ...or you could bring it up in the daily.

It solves a lot of problems, even if it doesn't solve every problem.

Re:Software engineering topics I changed my mind on by js8 on Sunday January 24, 2021 @03:48AM (#25890441)
> If senior engineer X is working on Y and other engineer M has already dealt with Y (unbeknowst to X), it's a great chance for X to say "I'm currently looking for a solution to Y" and for M to say "Oh I had to solve that same problem last month!"

I wonder why these "agile practices" shun the expertise so much. Instead of Y working on a similar problem as X in another month, why not make X an expert in the thing so that everybody knows about him being an expert and consults with him on a regular basis.

Is it really better to have everybody a shallow experience with everything rather than have a few individuals with a deep expertise with a particular thing?

And to have a meeting every day to "solve" this non-problem (somebody not knowing who the expert is, or supposed to be) seems really inefficient.

Re:Software engineering topics I changed my mind on by Jestar342 on Sunday January 24, 2021 @04:00AM (#25890487)
That's "Siloing" which is considered a negative pattern. If X is the expert, then only X can work on that something*. X is now a bottle neck.

Natural siloing happens, but you (team) should be striving to reduce it, not encourage it.

*More accurately: work can only proceed on that something when X is available*

Re:Software engineering topics I changed my mind on by js8 on Sunday January 24, 2021 @04:57AM (#25890752)
My point is, it doesn't have to be black and white. If your expert is less available, or has too much of the same work, or you just want a backup, you just start training someone else to be an expert in that area too. It's not costlier than what you propose, it seems that it is always better to start with having a designated expert rather than to dilute the expertise so much than no one really is.
Re:Software engineering topics I changed my mind on by watwut on Sunday January 24, 2021 @07:17AM (#25891419)
It does not work, at least did not worked for us. The problem is that in any single situation it is easier for expert to solve it alone then explain and when then there is sudden need to explain, expert can't do it effectively. Because he was not explaining for years.

Plus, you end up being in a limited box and have harder time to grow by learning new things - project structure keeps you in box and you can't easily expand it by taking tasks to learn something new.

Finally, expert is sort of fake expert - expert only because others are kept clueless. Not because he would had such great knowledge objectively, but because we decided this is only his area. There is no other engineer to discuss issues with our to compete with.

Re:Software engineering topics I changed my mind on by Jestar342 on Sunday January 24, 2021 @06:25AM (#25891169)
Nobody has said it should be except for you. As I said it will occur but you should strive to spread information and learning as much as is reasonable.
Re:Software engineering topics I changed my mind on by Scea91 on Sunday January 24, 2021 @03:58AM (#25890477)
Reason why I don’t want my team to overspecialize:

I don’t want them to isolate and develop tunnel-vision. I want everyone to be aware of the project goals and understand the work that needs to be done to deliver value.

My experience with teams where people are divided by topics for a long time is that unpleasant work that does not fit into a single topic well gets neglected.

Re:Software engineering topics I changed my mind on by js8 on Sunday January 24, 2021 @05:04AM (#25890783)
> My experience with teams where people are divided by topics for a long time is that unpleasant work that does not fit into a single topic well gets neglected.

I doubt it isn't the case either way. If you neglect understanding and development of expertise, you will still end up with some people having more expertise than others, and possible blind spots. Except now you have no idea what those blind spots are. (https://news.ycombinator.com/item?id=10970937)

Re:Software engineering topics I changed my mind on by BurningFrog on Sunday January 24, 2021 @10:59AM (#25893032)
I think "agile practices" without pair programming misses 70% of the benefit.

If you're pairing, no one person becomes the only expert on something, and also no one person is left alone to solve all problems in an area.

Re:Software engineering topics I changed my mind on by diob on Sunday January 24, 2021 @02:35AM (#25890133)
Standups aren't always necessary, but you'd need a high functioning (read communicative) team. In other words, they serve primarily as a forcing function to make sure teams are acting like teams (communicating).

I find the most useful standups are asynchronous though. It's much easier for others to follow along (and ask follow up questions), and avoids statuses devoid of usefulness (or at least makes them very apparent).

Re:Software engineering topics I changed my mind on by jimbob45 on Saturday January 23, 2021 @09:31PM (#25888460)
Agreed. It’s a deliberate inefficiency to make sure you at least have a chance to communicate with your team on a regular basis. Otherwise you might go days or weeks without the chance to have a critical two minute conversation.
Re:Software engineering topics I changed my mind on by crdrost on Saturday January 23, 2021 @09:59PM (#25888671)
That sounds suspiciously like your team is not communicating enough in the first place though. I mean, I guess the profession does get its fair share of introverts, but I would have expected enough teamwork that everyone knows what everyone else is doing, at least roughly. At my last gig I remember we had three backenders and four frontenders on a game we were building and the stand-ups seemed superfluous, Ryan on the frontend knew all of the frontend tasks and their exact states, I on the backend knew all of the backend tasks and all of their states, stand-ups were more of a means to celebrate what folks had done and coordinate that info with our QA team.

My silver rule of meetings is “to make a meeting matter, make a decision.” If we were assigning new tickets and/or backlog, deciding who would own each of them, that meeting is valuable. Progress updates can be delivered asynchronously and consumed asynchronously, unless, say, one wants group applause.

Of course now covid exists and I changed jobs to a team that barely talks with me and daily stand-ups are kind of my only social contact with them, so that's less fun. But yeah, 100% the original vision of agile with the “developers should be meeting daily with the product users to clarify the underlying model and mold the software to their hands” should cause people to work together so much that stand-ups become something of an afterthought.

Re:Software engineering topics I changed my mind on by closeparen on Saturday January 23, 2021 @10:39PM (#25888938)
It sounds like you and your team are working on the same artifact and that your tasks are interrelated. That’s kind of a special case. At any given time our 3 engineers have maintenance tasks in flight on 4 or 5 distinct products.
Re:Software engineering topics I changed my mind on by tikhonj on Saturday January 23, 2021 @11:09PM (#25889121)
If people are working on completely unrelated things, what do you get from a stand-up other than a group status update?
Re:Software engineering topics I changed my mind on by UncleMeat on Sunday January 24, 2021 @10:00AM (#25892541)
> That sounds suspiciously like your team is not communicating enough in the first place though.

That's probably true. There definitely exist teams that communicate well enough that the benefit of a standup is nearly nonexistent. But many teams aren't like that and have a handful of people who need a structured process for communication or they will struggle. Standups aren't the best solution, but they are an easily implemented way of getting a team part way there.

Re:Software engineering topics I changed my mind on by darkerside on Sunday January 24, 2021 @09:57AM (#25892512)
You and Ryan are set then (as far as you know). What about the other people on the team? Did they also have flawless insight into latest progress and next steps?
Re:Software engineering topics I changed my mind on by skohan on Sunday January 24, 2021 @09:33AM (#25892289)
I agree the list is very good list in general. My point of disagreement is:

> Software architecture probably matters more than anything else The devil is in the details here, but the more I program, the less I feel that "software architecture", at least as it is often discussed, is actually not important and often actively harmful.

The architecture driven approach takes the assumption that the "correct" shape of a program should fit into a pre-defined abstraction, like MVP, MVVM (or god forbid atrocities like VIPER) etc which has been delivered to us on a golden tablet, and our job as programers is to figure out how to map our problem onto that structure. In my experience, the better approach is almost always to identify your inputs and desired outputs, and to build up abstractions as needed, on a "just-in-time" basis. The other approach almost always leads to unnecessary complexity, and fighting with abstractions.

The author also mentions SOLID - like architecture patterns, I'm always a bit suspect of true-isms about what makes good software, especially when they come in the form of acronyms. I generally agree that the principals in SOLID are sensible considerations to keep in mind when making software, but for instance is the Liskov Substitution Principal really one of the five most important principals for software design, or is it in there because they needed something starting with "L"?

After 10 years of programming, the biggest takeaway for me has been that the function of a program (correctness, performance) is degrees of magnitude more important than its form. "Code quality" is important to the extent that it helps you get to a better functioning program (which can be quite a bit) but that's where its utility ends. Obsessing over design patterns and chasing acronyms is great if you want to spend most of your time debating with colleages about how the source code should look, but the benefits are just not reality-based most of the time.

Re:Software engineering topics I changed my mind on by otijhuis on Friday January 29, 2021 @01:50PM (#25960836)
I consider software architecture to be extremely important and based on the other opinions of the author he probably agrees with you that it should be "just-in-time", as do I. Useless abstractions just get in the way and make things complex and hard to understand.

Yes, if a program doesn't function the way it's supposed to, it's useless. Unfortunately I've seen many developers take shortcuts and not even think about the software architecture (because "hey, it works doesn't it"). Good software architecture not only makes it much easier to build functioning software, it also makes the team function much better. The ability to maintain the software and quickly add new features depends on it. Even little things you do can contribute to a good software architecture.

Overengineering leads to a terrible mess, so does the "hey it works, I don't care about anyone who has to maintain it" mentality. Ideally you'd be somewhere in the middle. You shouldn't design everything up front and you shouldn't ignore things that are right around the corner either.

Re:Software engineering topics I changed my mind on by jrib on Monday January 25, 2021 @08:18AM (#25902772)
> If senior engineer X is working on Y and other engineer M has already dealt with Y (unbeknowst to X), it's a great chance for X to say "I'm currently looking for a solution to Y" and for M to say "Oh I had to solve that same problem last month!"

I personally hate stand-ups. We do get benefit out of them, but I think it also leads to people waiting for the next standup to communicate instead of fostering a culture of communicating more pro-actively.

In your example: why wait for a standup? Why not just drop a message in slack saying "working on Y and not sure how to proceed; any ideas?"

Personally, I don't see the need for standups as long as the team is open about sharing blockers as they come up instead of waiting for the next standup cycle.

Re:Software engineering topics I changed my mind on by warrenm on Monday February 01, 2021 @09:16AM (#25988861)
That's exactly how Opsware Support worked when I was there: https://antipaucity.com/2011/09/15/the-ticket-smash-raw-metr...
Re:Software engineering topics I changed my mind on by christkv on Sunday January 24, 2021 @01:29AM (#25889826)
We always run standups in the same way. What did I work on yesterday, what am I working on today and finally impediments or help required as well as general organizational stuff that might impact the team.
Re:Software engineering topics I changed my mind on by Falkon1313 on Sunday January 24, 2021 @03:53AM (#25890461)
So do we, but generally a quick glance at the kanban board would show that for everyone. Well, it would if we had one unified board. Instead we have stuff scattered across multiple boards. Still it would only take 1-2 minutes to open them all up and glance through them. Information radiators. They work well.

Instead we have a 30-60 minute standup/sitdown/try-not-to-doze-off meeting to achieve the same thing. We used to also have additional meetings to review the boards but eventually cut those because people got tired of me saying "the status is still the same as I said an hour ago, because I've been in this meeting since then."

The exception is stuff like team announcements, reminders that someone's going to be out, requests for someone to volunteer to take a task. That can all be done async though.