Jake Olson

Everything is Computer

[Jake Olson @_jake_olson]

You’re NOT absolutely right

[tyler hogge @thogge]

Redo is giving $100 for up to 4,037 people to shop Redo brands.

They just raised $81M, and they're highlighting brands instead of themselves.

1. Tag @redo_hq in my replies
2. Tag a brand that uses Redo (https://t.co/NFWSTubRr2)
2. Say what you love about them
3. Watch the video for details

Pretty cool Series B launch from @sterlingmsnow @redo_hq

[tyler hogge @thogge]

https://t.co/FIf7UBCtln

[Jake Olson @_jake_olson]

@sterlingmsnow @ThursdayBootCo is my everyday wear and I still need more - awesome brand

[Sterling Snow @sterlingmsnow]

Well we just raised $81M at a $1.25B valuation led by Smash Capital, Pelion Venture Partners, and Cervin Ventures.

Over the last 24 months we've grown working with 100 Brands to more than 4,000.

Every month has broken the record from the prior month.

But it's always strange to announce these things. Really we all just think about how much work is in front if us.

This is a hard problem and we are excited to keep solving it for Brands.

For this launch we decided that instead of spending a few 100k bragging about ourselves in a fundraising launch, we made a video in house (the actor is by far the worst I've ever seen) and we're putting the money to better use.

It's going to YOU.

Our Brands and their Shoppers.

The only reason we were able to raise this round is because thousands of brands trust us with their business.

More than 70% now trust us with multiple solutions, not just Returns.

That trust means everything to us.

So we asked ourselves a simple question:

What if we spent the announcement budget on them instead?

Here's how we're gonna do it:

1. Tag a brand that uses Redo (link to brand list in pinned comment)
2. Tell us what you love about them
3. We'll give 1 person for each Redo brand $100 to spend on their site

To all our brands. Thank you.

[Lee Robinson @leerob]

You might believe you should spend less time thinking about code because of AI.

I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability.

At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time.

Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change.

I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance.

I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

[shadcn @shadcn]

Nope. The AI you use right now is UI that talks to APIs.

[Lex Tang @lexrus]

Ghostty can be a floating Liquid Glass panel above your movie.
————————————
background-opacity = 0.0
background-blur = macos-glass-clear
macos-titlebar-style = transparent

[Jake Olson @_jake_olson]

@theo Harmful but Polymarket is hardly the beginning of sports betting

If I had a nickel for every time Kevin Hart shilled Draft Kings…

I’d bet it all on the Rockies and have no nickels

[Jarred Sumner @jarredsumner]

In the next version of Claude Code

Claude Code’s Bash tool runs faster and uses less memory. Claude writing 1 GB to stdout 10 times:

Before: 115 seconds
After: 15 seconds (7x faster)

[Jake Olson @_jake_olson]

@chamath Except it’s not taxable if its net worth right

[Jake Olson @_jake_olson]

@bcherny Really want to see some useful slash command examples

[Jake Olson @_jake_olson]

@vimota @bcherny This

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Jake Olson @_jake_olson]

@chamath And people think AI note takers are a good idea

[Jake Olson @_jake_olson]

@antoniogm https://t.co/i7PXhGk8yN

[aditya @adxtyahq]

Vibe coding is fun until production shows up

[Micky @Rasmic]

Easy way to get into YC 2026 guide

Fork Opencode

Call it BetterCode

Raise 10 million

Pay yourself $300k a year salary

Win

[kanav @kanavtwt]

“I will work 9 to 5 and build small saas apps on the weekend to achieve financial freedom”

[Jake Olson @_jake_olson]

@fidexcode Who knew it was this easy

[Jesse @d0wnsideofme]

holy fucking shit