@cote maybe the Belgariad? They turn into birds there and maybe will trick into fantasy? :p was how I got started around that age
Anecdotally, I feel like the team I have been working with has been doing a lot of these things and it’s why it has been successful.
So now to try and find a way to help dev leaders (not managers) that aren’t used to this to succeed in replicating it. 🤞
If y’all want I can give an update in some months? 😁
In my company we use a chapter model to pull people together and learn. But it has gotten too big and it means it’s hard to showcase more active day-to-day. Shifting to smaller communities now with a hope of creating learning cultures. And bigger syncs to cross-pollinate
They had gotten the feeling they’d show up at work, get tickets, and then churn through ‘em. And that work was a lot more fun then they ever hoped thanks to it.
@faassen @grimalkina @gvwilson I think there’s a lot here in “not recognizing it,” as someone who has been steeped in agile practices for many years and see it work I can trust in learning and the process.
Many of my colleagues have only seen the farce of “standup=agile” and with some manager chasing output over outcomes. And then expectations are set for what work is like.
@oxtyped admittedly, I am a really a person who is trying to find his way. So I’m merely offering opinions :)
But, also, I am following people at https://woof.group who sometimes posts interesting stuff related to tech but otherwise is living their own great life. And it gives me interesting perspectives.
So I’m here for interesting perspectives :)
Over the last 3 years, the understanding of what barcodes, QR codes can offer has become mainstream and yet, there are people struggling to get the crux of it. Perhaps if they could generate these themselves, trivially, it will become a no-brainer. Enter, Zint Barcode Studio. Generates lots of barcode types, QR included. https://opensource.com/article/21/2/zint-barcode-generator #FOSS, ftw!
@oxtyped tag feels reasonable? Or just CW if it feels out of bounds? We’re all complex humans and let’s show our complete side?
Also, how would music be diff? Should I be ranting software under a tag? 😬
@faassen I did a quiz yesterday with people at work and it was 50/50 that PR reviews are about catching bugs compared to learning and improving. My position is that learning => fixing bugs, with the important part being that if they’re about catching bugs then we’re using humans as linters.
If we’re learning we might catch bugs but it’s about missing context (and the odd brain fart) so that’s the perspective that matters :)
@faassen definitely feels like there is something here about the non-linear. It’s something I have embraced more. But I felt like that was something I also embraced when I did trunk based? I would push when I had some amount to work, often behind a flag, and it wouldn’t necessarily be ready. So code changes all over as I learn more about the approach… 🤷
@faassen 100% on how much is on context. For this team it’s not unusual that start to finish an RFC with discussion takes a month. And it’s part of how we plan our work.
PRs I view mostly as a learning exercise: both for author and reviewer. We want to share knowledge but we also want to make it simple to deal with one small part. A year ago it was common with 1k+ PRs and they’d sit for days 😅
As an aside, weekly sharing meetings where we mob review has also been great!
Low cognitive load to read the code. I link the PRs together manually and share a story for full context. Open PR as soon as I finish a commit.
As I get reviews, I will then address/fix/rebase.
Same thing, higher visible WIP, but it's probably only 1 story behind 😄
One of the most effective things I've found is silent meetings where someone has written something up, then we schedule a time to read it together (forces the page count down) and then ask questions sync in text. Things we can't quickly sort out that way, we'll then discuss.
It also does wonders for tedious scrum of scrums and sync meetings.
Not sure I'm veering off in the direction you had in mind? 😁
@faassen now comes the dance of when will I get replies? If I'm lucky they will reply immediately when they start their day, and I won't be busy and can act immediately, it might turn into an impromptu call.
But most likely I'll get a reply at 21:00 and I'll respond next day around 10:00. Back and forth.
With my colleagues in my timezone, I will have a meeting, do a quick call, pair up, and so on.