Those who chase Easiness over Simplicity will end up creating something that is neither Easy nor Simple!

It is 4:20 AM and Fable is not letting me go to sleep! This is the first model I feel I am missing out every second I am not leveraging it!

1000 users doing what? Reading a blog? Joining a livestream? Placing bids? Moving money? Uploading video? Calling 911? The candidate is wrong for jumping straight to Kubernetes, Kafka, Redis, sharding, and multi-region. But the tweet is wrong too. It mocks overengineering while ignoring the actual mistake: nobody defined the use cases, constraints, traffic shape, or SLOs. That is the real system design failure.

Production deployment 🤑

#MyElixirStatus I propose that String.to_atom/1 to be deprecated and introduce String.to_atom/2

Hinting Engineering Meta is deprecated

The funny thing about this is that, if you know, there is a bug in it! This is exactly why you should use a library unless you understand it. Case made by itself!

Added `trg ai skills eval` to the CLI, give it a try github.com/TrogonStack/rusty…

The programming language that made me fall in love with Types is F# I watched so many videos from Scott Wlachin that I eventually understood how to leverage the compiler in my advantage. While having Jose in the other side reminding us that types cant guarantee all correctness 😛 I am a mixed breed

Released trogonstack-product-requirements v0.1.0 - PRDs and feature-level FRDs: product context, success metrics, personas, technical constraints, feature trees, and reviews. github.com/TrogonStack/agent…

My runtime resolve await as a monad act so, I am good! 😛 In other word, "It Depends ™" yordisprieto.com/context-is-…

All Above!

More often than not, the components may be "broken," but the system isn't. Is the component broken then? #SystemThinking

My first 10 years as a professional developer were spent almost exclusively in dynamic languages: JavaScript, Ruby, and Elixir. I always understood the appeal of static typing, but I never understood the ideology around it (the idea that you have to be on one side or the other.) Lately, working in Rust and Go has reminded me how nice it is to define new categories/types and let the compiler enforce them. I will continue to write tests, because tests capture forms of correctness that categories/types cannot prove. But I love not having to write tests for properties the type system can already guarantee.

• MCP 2026-07-28 RC is out: biggest protocol change since launch • Protocol core is now stateless → no sessions, no sticky routing, no shared session store • MCP requests can now scale behind plain HTTP load balancers • `initialize` handshake removed, metadata moves into `_meta` per request • Explicit handle pattern replaces hidden session state (`basket_id`, etc.) • New `Mcp-Method` `Mcp-Name` headers improve routing, caching, observability • Multi-round-trip requests replace persistent SSE flows for elicitation/prompts • Extensions become first-class with independent versioning governance • MCP Apps introduce server-rendered sandboxed UIs over MCP • Tasks moved out of core into official extension model • OAuth/OIDC authorization hardened across multiple SEPs • Roots, Sampling, and Logging officially deprecated • Full JSON Schema 2020-12 support for tools • Formal feature lifecycle deprecation policy introduced • RC available now, final spec ships July 28, 2026 blog.modelcontextprotocol.io…

I found the fun workflow and ultimate take advantage of @cursor_ai Composer 2.5; I created a `/agent-handoff` skill that fan-out to multiple work stream while keeping the main loop in @claudeai Really happy thus far

This is the way, weirdly, I find more joy on that than writing the code nowadays!

System Thinking!

Do not forget 🐢🐇 The finish line is what decides the winner. Also, yeah, stop with the "clean" code shit already, unless you give me a methodology of such "clean" code

Drop the R and I am cool with it most of the time!

Classic! 💀