When I was a corporate employee, my calendar was always packed. Meeting after meeting. By the end of the day, I'd been going 100 mph and gotten further behind.
The organization rewarded people who were always slammed.
But busy and productive are not the same thing.
#TimeToThink #SelfLeadership
Most organisations don’t lack effort. They lack clarity on where to start. The Team Topologies assessment helps surface where things feel heavier than they should, and where to begin. Take the assessment here - https://survey.teamtopologies.com/tt-assessment
Most organisations don’t lack effort. They lack clarity on where to start.
The Team Topologies assessment helps surface where things feel heavier than they should, and where to begin.
Take the assessment here - https://survey.teamtopologies.com/tt-assessment
I feel this post from @johncutle.fish is about to become very important (for me) in terms of how work gets structured in my context…
cutlefish.substack.com/p/tbm-414-le...
"Being the Human in the Loop" - @kevlin.bsky.social. Typing isn't the bottleneck. Be the driver, not the road. Watch youtu.be/vpYJMr1pJRY
Looking for work. Will DevRel for coffee or wine 😁
New article where I offer definitions & a mental model how to think about harness engineering as coding agent users. Building blocks at our disposal, dimensions and goals to consider; emerging practices, open questions; and of course, what role do humans play martinfowler.com/articles/har...
Danish price for a gallon of diesel is approx USD 10.1 (for comparison)
This post by @johncutle.fish really resonates with me
cutlefish.substack.com/p/tbm-412-in...
I don’t see any change in how work is performed - just people working faster - because that’s what expected with AI right?
That behavior gets promoted and internalized.
We need to work different - not more
This is one of the things collaborative software design is fundamentally about: making implicit knowledge explicit. The opinions, the preferences, the emotions behind a technical stance, they don't disappear when you ignore them. They just go underground and shape decisions anyway, invisibly.
>>>
"AI Augmentation for Technical Leaders" - Birgitta Boeckeler. Can AI help with architectural decisions? Watch:& Subscribe. youtu.be/qB7rsbDfmQg
🎉 That's a wrap with the last sessions from @andrewhl.bsky.social
@bitboss.bsky.social and @josvanschouten.bsky.social 2 days, 28+ sessions, countless connections. From AI to Team Topologies to real-world solutions. Thank you. See you next year
And so it’s a wrap!
I’ve been attending the Agile Meets Architecture 2026 #amaberlin @amaconf.bsky.social in Berlin and my head is still buzzing from all the insights on how we (could?) shape both systems, organisations and ways of working through architecture.
…and sometimes the other way round 😉
We would really like to enable our developers to use Copilot CLI but are currently somewhat stuck on the terms for Copilot Business stating that prompts from Copilot CLI will be retained.
I can’t seem to find info on for what purpose and for how long GitHub retains those prompts?
Does it even make sense to introduce agentic ai to accellerate workflow execution if we don’t have a clear idea of what that flow or process looks like?
It does seem worthwhile to accelerate a code generation phase if it only accounts for 20%(?) of the entire value-stream?
Removing waste is better?
If using agentic ai corresponds to ingesting more work into a system (e.g.generating code) but we’re not moving faster?
So using ai didn’t remove the right bottleneck in a theory of constraints type of way?
During a discussion I got the feeling that value-stream-mapping and LEAN are still relevant.
The first time I heard about “back-of-an-envelope-calculations” was during a computer science class in 2002 which referenced a “Programming Pearls” article by Jon Bentley.
This has been a tremendous help in my life (both personal and professional) ever since!
dl.acm.org/doi/epdf/10....
My personal (unscientific) theory is that it’s the NTFS filesystem itself, which results in poor build time performance for Java Microservices (e.g. Quarkus). We’ve unfortunately not seen Dev Drive make a huge difference. So our Java developers favor MacBooks because it’s much faster build times!
For a long time we thought it was Defender which resulted in poor build performance when building Java Microservices on our Win11 developer machines. But that was disproved by comparing performance with a non-enrolled machine with similar poor build performance. We don’t see this issue on MacOS
That rule prevents newly build binaries (the output of a build) to be run on a machine with Defender of you don’t disable it (or put it into monitor/ audit mode).
Disabling that rule for specific file paths made the world of a difference.
We’ve done these things to exactly avoid local signing of files as part of a developer flow.
Our risk scenario was a developer machine that was compromised and able to sign executable files which were then distributed across the network and trusted.
We wanted to avoid that.
We’ve been meaning to investigate process whitelisting to avoid having to request an IDE to run as Admin based on fingerprinting - but it hasn’t been prioritized (yet). So some teams still have to elevate processes locally +10 times a day….
Our local developer environment (Windows 11 with E5 license and Defender XDR) is (almost?) CIS2 baseline compliant.
So lots of things have been disabled and or restricted as well.
ASR rules and not local admin user however being the major issues that we had to handle. There is no local signing…
Many restrictions! 😂
Apologies - I thought you were asking about what we tried to do to make “Windows Desktop” development feasible again?
Running IDE as admin user when you’re no longer local admin on your dev machine is also a pain. We use a PIM tool: User requests that program is run as admin.
Exactly that one! 👍
Binary signing is done using an EV certificate stored in a Azure keyvault and can only be done through a pipeline. Never locally.
ASR = Attack Surface reduction rules
We choose to exclude a specific folder from Defender ASR which was the worst issue for home-built exe/dll as well as Python development. Our developers love WSL because it’s much faster for Java development than e.g. normal Windows and Dev Drive
“As the US military chases Trump’s ever-changing Sharpie lines across the world’s maps, the West’s enemies will be tempted to take advantage of the fact that the US has obliterated the most powerful alliance in history while scattering American forces around the globe in showpiece operations.”
Analysis paralysis?… everything needs to be thought of before taking action.
So many times, nothing (bad) actually happened… yet weeks are spent consulting, asking, contemplating… without adding value.