Luís Soares (@lsoares) profile picture

software developer 🖥️ 👍🏼 Lean, XP, TDD, pairing, DevOps, CI/CD, trunk-based dev., user-centric dev, domain-centric arch., Kotlin

Lisbon
Joined July 2008
With AI, teams can iterate much faster if they use it properly. They can have more feedback loops, etc. What do they do? Upfront planning, better specs, better waterfall. It's depressing
14
Luís Soares retweeted
There's a pretty simple heuristic to know if you are getting replaced by AI: - If your work is taking a thoroughly-specified business task from analyst and translating it into programming language, and you used to constantly complain when the task is not super precise - you are getting replaced. - If your input is mostly "make it good bro" and then it's your job to know what is good, how is good, and where is good, and especially if you take ownership and responsibility over a product or its part - you are not getting replaced.
26
35
818
35,029
Luís Soares retweeted
Replying to @unclebobmartin
“Your job is to help the LLM write better code faster.” Strange: I thought the job of a software engineer was to bring value to stakeholders in an enduring, economically sustainable, and ethical fashion. I suggest you reconsider your life choices, Bob.
30
31
7
509
60,816
Gentle reminder that amount of features is not a goal or a metric to pursue. Before and after AI.
32
Luís Soares retweeted
529 days can change a man He doesn’t even wear hats indoors anymore
70
422
52
6,183
423,337
It's 2026, and devs still create `util` files/dirs.
4
106
Challenges of a shared codebase — Part II open.substack.com/pub/newsto…
44
Challenges of a shared codebase — Part I open.substack.com/pub/newsto…
47
The deal with Iran will go down as one of the most incompetent ever made. The U.S. lost on virtually every point. We just don't win anymore! – at Manhattan, NY
2,165
8,949
1,571
21,279
Created an app to keep track of the current episode, which is nice if you're watching multiple shows: play.google.com/store/apps/d… also: AI mood suggestions (ratings-based), new eps notifications, widgets, among others. uses Trakt or Simkl. Feel free to provide feedback.
1
1
77
Luís Soares retweeted
Lots of people compare LLMs to assembly, and say "You didn't look at the assembly output of your program, why would you look at the output of the LLM?". Well, first, in the Linux Kernel we did look at the generated assembly often. But leaving that aside: Except for the rare compile bugs, I can trust that if I write correct code, I will end up with correct assembly. I also know that the compiler will not start adding security holes on its own volition. No such guarantees with llm.
it's kind of useful to see what this approach ends up producing
76
96
9
1,820
97,098
In my experience, the vast majority of waste in a software shop is time spent building things nobody wants on top of overly complex architectures that solve problems we don't have. Focus on that. Put solving your customer's actual (not imagined) problems first. And do exactly that—no bells and whistles; no futureproofing (select a change-friendly architecture instead). Forcing AI onto a customer who doesn't want it (because it doesn't solve a real or critical problem for them) is worse than waste. It drives people away. Sitting around imagining how AI can "help" your customers without understanding their specific problems is just expensive arrogance.
6
12
1
88
5,244
Luís Soares retweeted
Remember when we learned that our wealthiest and most powerful people were connected to a guy who ran a literal child sex trafficking ring? And then that guy died mysteriously in a jail? And now we just don't talk about it.
14,424
54,514
12,946
181,014
A user story is not a code word for specification or a requirement or any description of work. It is not a ticket. It is not a to-do item. It is not something you can build. The fact that the term has been corrupted by the Jira-slinging ticket-money pseudo-Agile Scrummy culture is a real shame, because it's a valuable concept: A "user story" is literally the user's story. It is a description of a problem, not a solution. It is not a specification. It cannot be estimated. It's the topic of conversation that we have with our users/customers to understand their problems and collaboratively develop the smallest, best solution. The story is not the solution—it's the beginning of the conversation you have to arrive at the solution. A story describes our users' work, not ours. The idea is that the best software solves real problems that real people have, and that, by identifying those problems, we can build something that's actually useful. By working on the software one small problem at a time, we guarantee that every release does something useful. People who talk about user stories being dead never understood what they were to begin with. You cannot build software without them.
7
24
1
158
9,448
having a README.md filled with different goals and guides is as bad as a types.ts file. both are a hotspot for unrelated things.
1
1
36
Frameworks, tools, and methodologies are a byproduct of values and principles. Get those right first.
27
Myth: DRY means not repeating code. Reality: DRY means not repeating knowledge (as per the original definition in The Pragmatic Programmer). This can mean more code in the end, sometimes.
1
41