Yani Lathouris
banner
yacl.bsky.social
Yani Lathouris
@yacl.bsky.social
Nup
July 30, 2025 at 8:12 PM
Beautiful. But where are the pigeons? Surely this is prime realestate.
July 27, 2025 at 6:36 PM
Great article!

The semantic diffusion is real. This seems to happen a lot in our industry. There are lots of wonderful practices that are misrepresented, misunderstood, and under-utilised. That’s why experts like you and articles like this are so important.

Thank you!
July 26, 2025 at 9:17 PM
Nausicaä would never give up
July 21, 2025 at 7:17 PM
Catchy!
June 12, 2025 at 9:10 PM
These companies cannot test and deploy services independently which drives them towards testing things in batches.

Maybe not an official “release train” but close enough.
March 1, 2025 at 10:54 PM
I know you recently discussed this with Dr Nicole Forsgren which was awesome.

Other than groups you have identified, I think this can apply to companies who have tried to adopt Microservices but ended up with a Distributed Monolith.
March 1, 2025 at 10:54 PM
Same. I like DORA + SPACE.

I am also a huge fan of Trunk-Based Development whilst pairing or even mobbing with the whole team (domain experts included). Often pushing directly to trunk - no PRs.
February 19, 2025 at 2:07 AM
Same. Like using the number of PRs per dev per day as a key metric in the new Core4 model.
February 18, 2025 at 4:26 PM
I read this as “I am the tidiest”. That’s how tired I am.
February 18, 2025 at 4:07 PM
For example, say you have a stream-aligned/product team working on a new feature. That team has domain expertise but are lacking other technical capabilities needed to deliver a solution.

How do they go about designing the solution? Collaboration?
February 18, 2025 at 12:03 AM
I like this approach but here is something I have been thinking about recently...

If the expertise is separated from the business context, how can we ensure we're using the right solution for the problem?
February 18, 2025 at 12:03 AM
🤣
February 17, 2025 at 11:22 PM
I got an A+ for my bowel prep. My Gastroenterologist told me to only eat white foods before the exam.
February 16, 2025 at 11:29 PM
I know the pieces never fit together as perfectly as we’d like but my gut tells me something like this:

If you continually need to converse in some parent context (e.g. global) to make sense of things, then perhaps the child contexts aren’t quite right.
February 12, 2025 at 10:29 PM
How often do we have conversations in the global context?

Whilst, I am sure they do occur, I suspect the majority of useful conversations happen within a given bounded context using the ubiquitous language.
February 12, 2025 at 8:17 PM
Yeah, I think that’s it. It depends on the org and the culture.

In the wrong environment, team members can compete for visibility. I don’t think this serves anybody.

Maybe this is a good example of one of those things that works in the forest but works against you in the desert?
January 24, 2025 at 5:37 AM
You can solve a problem that has been bugging/blocking a lot of people.

Obviously this is great but is it worth more than the work that was done to prevent folks from being blocked in the first place?
January 24, 2025 at 4:42 AM
You can get involved on those really high profile project initiatives.

You might get more kudos at the end from well respected folks but the highest profile projects aren’t always the ones that have the biggest impact.
January 24, 2025 at 4:42 AM
Visibility can be a bit of game too!

You can be the first to come into the office and the last to leave.

It might look like you’re putting in extra effort but it isn’t always productive. It sets a bad example and can lead to burnout.
January 24, 2025 at 4:42 AM
Is visibility what we really need?

I think I’d rather be a “Ghost Engineer”
January 24, 2025 at 4:42 AM
🤣👏🙌
January 24, 2025 at 12:40 AM
Hahaha! Love it.

Do you think it’s acceptable for someone to take on an alter-ego when writing comments (or other forms of async comms)?

Basically, I think I just realised how boring I actually am.
January 24, 2025 at 12:14 AM
I am quite surprised by the decision to use PR Throughput (PRs/developer) as a key metric though. Especially when previous research (State of DevOps Reports) highlighted practices such as Trunk-Based Development (TBD) which can, and often is, practiced without PRs.
January 15, 2025 at 10:04 PM