Timo Reimann (@timoreimann) profile picture

Systems Engineer working @Cloudflare

near Munich, Germany
Joined March 2011
Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)Photo by Timo Reimann (@timoreimann)
Timo Reimann retweeted
When I first told @MParakhin that we were planning to move to a monorepo he said wisely: Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.
moving to monorepo has been a boon for agents at shopify. definitely requires some thoughtful tooling, and has some downsides that take a bunch of effort to mitigate… but man I wouldn’t go back
143
82
59
2,122
258,985
Been saying the same thing to various folks for weeks. No more excuses to apply good engineering practices which are only becoming more critical with agents.
Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.
2
599
Timo Reimann retweeted
yall im ngl its way harder to get joy and satisfaction out of building with ai than it was before constantly straddling burn out, being far less immersed in hard problems, constant context switching i’m tired of the uncertainty of where this is going and how to do it well
274
224
88
3,775
392,857
Timo Reimann retweeted
Love this! noslopgrenade.com/ Share it to everyone, everywhere.
2
6
188
Timo Reimann retweeted
announcing artifacts - a versioned file system that speaks git certainly the coolest thing i've ever built and i got to build it with some truly great people fearless leader: @elithrar zig/git nerd: @mattzcarey storage goat: @thomas_ankcorn blog.cloudflare.com/artifact…
92
129
67
1,340
242,660
Timo Reimann retweeted
sent this to the team today everything great comes from being able to delay gratification for as long as possible and it feels like we're collectively losing our ability to do that
252
697
189
6,854
985,630
Timo Reimann retweeted
One of my favorite people in tech is @bcantrill and he wrote one of the most thoughtful essays about LLMs I've read in the last two years: rfd.shared.oxide.computer/rf…
6
42
2
460
38,044
Timo Reimann retweeted
The best engineers never just wrote code. They were clarity merchants. The collapse of the implementation middle isn't making engineering less important but it's revealing what was always important: understanding problems so clearly that the code (now, the spec for our agents) becomes more obvious. The engineers who will thrive aren't those who can translate specs to code fastest. They're the ones who can: 1. Shape ambiguous problems into actionable intent 2. Design the context architecture that makes good outcomes inevitable 3. Judge what matters from what merely works This mirrors what others have observed about business model shifts: when distribution costs drop to zero, value accrues to curation and taste. When implementation costs approach zero, value accrues to problem formulation and judgment. The tools that win won't just accelerate the middle but I think they'll eliminate the need for it to exist separately at all. The craft evolves. It always has. But it remains craft.
54
207
24
1,860
217,238
Timo Reimann retweeted
Brilliant post on using coding agents. The workflow described here is as close as it gets to my own. From creating rules and skills to optimizing workflows, testing, and more.
32
106
9
1,623
218,698
I can’t get over the fact that 50% of Roger Federer’s name is just “er”
2
12
867
Timo Reimann retweeted
New Anthropic research: Tracing the thoughts of a large language model. We built a "microscope" to inspect what happens inside AI models and use it to understand Claude’s (often complex and surprising) internal mechanisms.
180
1,409
413
8,330
1,578,689
Timo Reimann retweeted
This is the worst feature that Apple has ever launched.
124
80
30
2,529
234,441
Timo Reimann retweeted
OpenAI, Anthropic, et al. scraped my website, my videos, my codebases, and all of the content I've published online. They used years of *my* work to train *their* models. Now, they claim this is "their data" and accuse others of "stealing" it. It's really hard for me to empathize with them about this. It's also hard to understand how they can claim moral superiority concerning the censuring of models. Both the GPT model series and Claude are totally nerfed and ideologically biased! Here I am, once more, rooting for free, open-science, and open-source models to be the last ones standing.
278
1,132
107
9,700
766,571
How to be a Principal Engineer/Senior Principal Engineer/Senior Architect/fancy-sounding-title Engineer, a thread: 1. You're evaluated on how much more the company succeeds because you're there, not the lines of code you wrote. If you can unblock someone, do that. If you need to kill a two year project that's not going anywhere, do that. Do what is right, not what makes you look good.
Very interesting. Do you have more insights into senior principal engineer role for somebody who considers it as a next milestone on their carrier path?
23
323
37
3,443
628,484
This got bookmarked and so I want to expand on it and give five (I hope) helpful pieces of advice to people who are job hunting in 2025, in what is a very competitive market. 1) Your network is more important than ever. Referrals go a really long way. This doesn't mean asking people you do not know for referrals, but build relationships and use them to get a foot in the door. To do this attend meet-ups, join communities, contribute to projects - whatever is interesting to you. 2) Make tailored resumes. For each role you apply to, make sure to ensure your resume matches as close as possible to the requirements. AI is being used more and more for initial screening, and you want to ensure you at least get the chance in front of a hiring manager where you can show your stuff! 3) Niche down. Pick a thing and become great at it. Could be a programming language, a technology or a domain. Either way, become great at it and evidence it through code, blogs and talks. 4) Reinforcing the last one; demonstrate your expertise. You want to be able to link to code, blogs and talks that show you're experienced in a space. 5) Don't wait until you need a new job to start looking. You have the most leverage when you have options. If you're thinking of exploring new roles, start the process now. A lot of big companies will have just signed off roles for year and will begin opening new roles this week if they have not already. I know this seems a lot, but I promise you others are already doing all of these things because I am seeing them come into my hiring pipeline. Good luck in your job hunt in 2025!
This quoted post is unavailable.
1
14
1
40
4,623
New blog post explaining `tool` directives in Go 1.24: cirw.in/blog/go-tools
5
2
28
5,761
Timo Reimann retweeted
A Go testing package for time and concurrency testing That's freaking awesome 🤩🤩🤩 danp.net/posts/synctest-expe…
6
26
1,557