🐌 Joseph NOMO

L’empereur

Le mien a abusé sur la vodka

The level of detail

Pardon arrêtez d’inventer le miroir de Yata repousse toute sorte d’attaque pas juste le ninjutsu. Je ne sais pas exactement ce qu’on raconte dans l’animé, je vais essayer de regarder. Mais dans le manga de Kishimoto ce n’est pas ça.

This meat riding is diabolical

I started adding playwright full tests suite on my pipelines; it’s better to do that in this era.

Zoro a encore beaucoup de chemin à faire. Luffy ne peut même pas se tenir debout quand Kaido fait la même chose.

Pfff

Sanji avait ses gènes Germa actifs lorsqu’il a botté le laser de Borsalino, là actuellement ce n’est pas le cas Les Vinsmoke sont insensibles à ce genre de trucs.

Chef?

@schmonky_ @Sangeruo @WorstGenHQ

@MorelNi63205197 @TheHokageYonko

Lately, I’ve been building an agentic workflow around the way I work. The idea is not to remove myself from the process, but to stay focused on the important part: what are we building, why, and how should we approach it? I stay involved with the agents until the architecture is clear and I’m happy with the direction. Once that part is validated, the workflow takes over a lot of the heavy lifting: build, test, debug, review. I also have the agents maintaining a wiki as they work, so decisions are explained and the work is documented properly in case I need to come back later. That’s really where the acceleration comes from for me. I’m still very much in the loop, just spending more of my time on decisions and less on the coding side.

I don’t want to assume that scale automatically means splitting the system. I want to see where the monolith actually starts becoming the constraint. Until then, I’d rather optimize what I can measure than distribute what I don’t need to.

The focus for me is different this time. I want to reduce internal network hops, keep transactional flows simpler, and have tighter control over what happens inside the application while going deeper on database indexing, locking, concurrency, transaction design, CPU and memory profiling, query performance, idempotency, and clean domain boundaries.

Now I’m building a new payment orchestration engine, and this time I decided to start with a monolith. Not because I think microservices are bad, but because I want to push the monolith experience much further and see what it can really handle before distribution becomes necessary.

For the past three years, I’ve been building and operating a payment orchestration platform around microservices. That experience taught me a lot about distributed systems, service boundaries, scaling, infrastructure, and the operational complexity that comes with all of that.