emmanuelvalverde.dev
Working 👨💻 @ 🏡 | 🎗️ Cancer survivor 🦸♂️ | Crafter working @BavelVoxel, ex-@codurance_es, ex-@_nailted | co-organizer @murciaswcraft | Open Source #bashunit | International speaker | co-author | #XP #TDD #PairProgramming #TBD #DDD
👤 Joined on 05 November 2024
Followers
Following
Total Posts
@evalverde.bsky.social@evalverde.bsky.social → @emmanuelvalverde.devI get your point. From my experience, I would say most have evolved so that more people are exposed to the crafting mindset, which is still present around. Especially in the hall conversations and the typical table that's the meeting point for katas all day long. That, you won't get on YouTube.
Show PostToday's Pragmatic Engineer newsletter [https://t.ly/ltiYl] was talking about Meta's misguided attempt to fire everybody and replace them with AI. Zuch was evididently thinking (if you can call it that) that mass layoffs would make them look more like a startup. 1/9
Show PostYou're making incorrect assumptions. As with most of my advice, doing what you're doing now with one change doesn't work. Doing what you're doing now but with fewer people does not work, either. You have to work differently. 1/
Show PostI've worked in many highly effective 3-5 person teams that don't have the problems you mention. We were mob/ensemble programming, so—time off is simply not a factor, even during the day. When one person leaves the mob, work continues without them. Knowledge is not siloed. 2/
Show PostThe teams had about 30% slack time built into the schedule. For example, we had learning hours every morning, game time once a week, and people had ample time to work on personal projects. We were not doing any time-sucking canned process like Scrum. I could go on.
Show Post