Imported from Uruguay. Web/Mobile Developer. Lean activist and part of the Free Software community. Really friki about quality. Love a good beer!
Florianópolis, Brasil
Joined July 2009
- Tweets4.2K
- Following649
- Followers543
- Likes12.2K
How do you build a shared understanding of what’s the problem before jumping into technical details?
2026 com carro voador e não tem debate com checagem de fatos em tempo real #DebateNaBand
Have been using the /show-me skill from @humanlayer_dev to understand PRs or complex domain designs, but with the addition of storytelling. So is a visual explanation plus a story that I can understand. You’ll be amazed how easy is to build shared understanding by telling stories
Sebastian retweeted
Como eu posso explicar que um desenho animado representa como funciona a política da extrema direita no Brasil?
#EleNão
Sebastian retweeted
great post from @exedev team - the same thing that has always been true of software engineering is still true:
Do fewer things in parallel, do them very well, optimize for getting incremental value out to users, FOCUS
It's been 30 years since the XP and Lean folks said "limit work in progress (50+ if you count the eli goldratt thing) - its still true
blog.exe.dev/etoomanythings
Sebastian retweeted
Context isn't handed to you. You build it.
It's the one part of the job the agent can't do for you, and exactly the part you thought was someone else's.
the /grill-with-docs skill from @mattpocockuk is my favorite skill of all, and what I like most is because balances from pushed to pulled communication between me and the agent so together we build shared understanding at my own human speed
I’m starting to like AI slop, it's creating enough pain that deliberate design matters more than ever. Implementation was slow enough that humans could usually keep up and make conscious decisions on why, what and how should be build
Sebastian retweeted
Lazy work used to mean too little output.
Now, with AI, it often means too much and more work for everyone else.
@tobi call it "slop grenades."
A "Slop Grenade" is when you let AI produce the work and pass it on without adding any value (including checking it).
Someone else has to wade through it, catch the mistakes, and clean up the mess.
You save time and look productive but someone else pays for it.
My third conversation with Shopify co-founder and CEO @tobi.
0:00 How Shopify Uses AI
7:18 River: Shopify's Internal AI
8:55 How to Encourage Osmosis Learning
10:52 AI Dreaming and Self-Reflection
11:53 How to Use AI for Strategic Decision Making
14:11 The One Thing AI Cannot Do
16:04 What AI is Making Worse at Shopify
19:46 Predictions: Where AI is Headed Next
21:55 The Future of AI-Powered Software
24:40 Will CEOs Be Replaced with AI?
27:54 Can Superintelligence Be Controlled?
31:13 Critical Skills in AI Age
34:22 Why Complex Solutions are Usually Wrong
36:33 Conditions Needed for True Intuition
38:02 The Best Path Doesn't Have Instant Feedback
44:51 How Affirmations Can Shift Your Behavior
50:44 The Inobvious Thing Hurting Companies
52:37 Relationship Between Beauty and Creation
56:23 How SpaceX Moves Forward By Subtraction
1:00:24 Why Companies Need Refounding Events
1:01:50 Books as Cheat Codes
1:02:39 Three Books to Change Your Thinking
Enjoy!
(Includes paid promotions.)
Sebastian retweeted
This vision of (fake)Agile👇 drives me nuts. Just No. There are no waterfall tracks. I collect just enough information to start, not finish, the work, and I do that just before starting. I write my tests first and run them every few minutes (TDD). I deploy often—minutes, not hours or days (CI/CD). I get feedback (and additional requirements) as I work and adjust what I'm building based on that feedback. The whole team works on each story and does not split the work into parallel tasks (scatter/gather). The relationships between stories are a (mostly undirected) graph, not a hierarchy (epics). There is no central orchestrator—decisions are made by the team as a whole.
There is nothing at all Agile about that diagram, though many people work that way. Small waterfalls are still waterfalls. This is a waterfall shop holding onto dysfunctional ways of working with a death grip.
hear me out, what if... wait wait..., what if, after optimizing the building part, we optimize how we build shared understanding of what we’re actually building and why? maybe that's the hidden root cause of AI slop
If digital product development is a process of making deliberate decisions, how in the hell do you expect humans to keep up with thousand of decisions delivered by an AI agent. Plan for humanS understanding bandwidth, not AI bandwidth
Sebastian retweeted
I'm starting to think that DDD might be the answer to all of my problems
- Model not doing what you want? Shared language
- Can't navigate a massive codebase? Bounded contexts with global mapping
- Don't know why a decision was made? ADR's
It's just so freaking elegant
Sebastian retweeted
Code review made sense when humans wrote code at human speed. Now I'm on a beach with a genie, generating faster than anyone could review. The old model broke. What replaces it?
open.substack.com/pub/tidyfi…
New post, sponsored by @coderabbitai