Timo Reimann

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/artifacts-git-…

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

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/rfd/0576

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.

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.

👋Cloudflare Containers are now available in public beta! Simple, global and programmable compute. Read about it and see how you can try it. blog.cloudflare.com/containers-are…

I can’t get over the fact that 50% of Roger Federer’s name is just “er”

@AntoineGrondin Thx, I'll be on time (unless DST thwarts my plans)

@timoreimann tomorrow 9AM EST

say no to timezones

@VicVijayakumar @dok2001 @Cloudflare soon: blog.cloudflare.com/cloudflare-con…

@dok2001 @Cloudflare Running docker containers

What should we build (or improve) next @Cloudflare?

Containers + Workers coming soon on @Cloudflare : blog.cloudflare.com/cloudflare-con… Lots reasons why I am excited about where this is going:

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.

This is the worst feature that Apple has ever launched.

@fatih That Sid Meier book is going on my list right now.

So far I’ve finished 5-6 books this year. Currently reading “Bullshit Jobs” by David Graeber (and “Debt” in parallel). And here are the books I still want to read. Not sure when but I’ll finish them eventually.

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.

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.

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!

@ChShersh Such a strong and likeable post until soul-crushing (5) entered the game.

Devs love wasting time discussing new solutions to solved problems. These are solved, move on: 1. Don’t use ORM 2. Monolith first, microservices second 3. Monorepo first, split when it doesn’t scale 4. Never use mocks 5. LeetCode interviews are easy

@FedEx @FedExHelp @FedExEurope @FedExHelpEU And yes, I tried a different browser and cleared the cache / cookies to no avail. This seems to be on you.

@FedEx @FedExHelp @FedExEurope @FedExHelpEU been trying to schedule a package pickup but receiving errors from your server ("500 Internal Server Error") consistently since at least December. Something is broken on your end, at least for the data you need to process in my case.