Kangkan Boro

AI @ borderplus, Previously GenAI platforms @fractalai
Startup chaos veteran
Arsenal fan with a GPU addiction

[DHH @dhh]

You can’t outwork the whole world. There’s always going to be someone somewhere willing to work as hard as you. Someone just as hungry. Or hungrier.

Assuming you can work harder and longer than someone else is giving yourself too much credit for your effort and not enough for theirs. Putting in 1,001 hours to someone else’s 1,000 isn’t going to tip the scale in your favor.

What’s worse is when management holds up certain people as having a great “work ethic” because they’re always around, always available, always working. That’s a terrible example of a work ethic and a great example of someone who’s overworked.

A great work ethic isn’t about working whenever you’re called upon. It’s about doing what you say you’re going to do, putting in a fair day’s work, respecting the work, respecting the customer, respecting coworkers, not wasting time, not creating unnecessary work for other people, and not being a bottleneck. Work ethic is about being a fundamentally good person that others can count on and enjoy working with.

So how do people get ahead if it’s not about outworking everyone else?

People make it because they’re talented, they’re lucky, they’re in the right place at the right time, they know how to work with other people, they know how to sell an idea, they know what moves people, they can tell a story, they know which details matter and which don’t, they can see the big and small pictures in every situation, and they know how to do something with an opportunity. And for so many other reasons.

So get the outwork myth out of your head. Stop equating work ethic with excessive work hours. Neither is going to get you ahead or help you find calm.

[The Outwork Myth — It Doesn't Have To Be Crazy At Work, 2018]

[Kangkan Boro @kangkanB]

❤️❤️❤️❤️❤️❤️❤️❤️❤️

[Arsenal @Arsenal]

The Arsenal. Your Premier League champions.

[HandofArsenal @HandofArsenal]

“Enjoy your playoff final, pal”

[APS @anirudhasah]

We are very close to inventing water from first principles

[Nick Khami @skeptrune]

>what do you think of the claude codebase?

brother, i'm not even reading my own code anymore. what makes you think i'm going to read someone else's?

[Claude @claudeai]

Computer use is now in Claude Code.

Claude can open your apps, click through your UI, and test what it built, right from the CLI.

Now in research preview on Pro and Max plans.

[shadcn @shadcn]

git worktree is a great feature for people smarter than me

[aditya @adxtyahq]

Me and the API key I hardcoded “just for testing”.

[Kangkan Boro @kangkanB]

Hard agree... claude code is my openclaw

[BOOTOSHI 👑 @KingBootoshi]

my honest thoughts after using openclaw/moltbot/clawdbot:

after 24 hrs of usage i dont use it anymore

for anything genuinely serious just use claude code/codex directly, hosted on a server if i want on-the-go work

openclaw uses tokens like a mf and it is NOT efficient at all

you also should not be connecting personal services/apis together in one bot

you should be taking security seriously and isolating each service with different ai systems

you do NOT want to infect sensitive information in an agent that can also access the web or social media (like, moltbook, which is accessible via an api call lol)

it’s great for prototyping though! but again, claude code can easily do these prototypes solo

next i will be experimenting with kimi k2.5 on the regular claude agent SDK on isolated sandboxes and see how that performs!

[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.

[Kangkan Boro @kangkanB]

@MyIndusIndBank applied for the IndusInd Avios CC January 1st week and have not received the card yet. Today I get an SMS saying that my bill has been generated - 11800 annual fee but I DONT HAVE THE CARD YET. I do not want this card anymore, please cancel it .. you’re wasting 🕣

[gaut @0xgaut]

realizing you don’t need to know how to code to build good ideas anymore but you have no good ideas

[Dan Robinson @danrobinson]

Claude Code is humbling in how fast it can prove that my cool backlog ideas that I never had the time to implement were actually pretty mid

[Kangkan Boro @kangkanB]

@bcherny Was just thinking about this yesterday and you shipped this today. Thank you!!

[Aaron Li @aaronli]

Steps to ruin your day:

1. go to https://t.co/plh3OeOnsZ

[Kangkan Boro @kangkanB]

We love you Opus 🥰

[Claude @claudeai]

Introducing Claude Opus 4.5: the best model in the world for coding, agents, and computer use.

Opus 4.5 is a step forward in what AI systems can do, and a preview of larger changes to how work gets done.

[Kangkan Boro @kangkanB]

We got Sagaland before GTA 6
Congrats @srijanyaham @jeankaddour

The games are sooooo good ❤️

[Y Combinator @ycombinator]

Sagaland is a UGC games platform where players create and remix games using AI.

They're starting with interactive story games and have hit $200k ARR in 4 weeks.

Congrats on the launch, @srijanyaham & @jeankaddour!

https://t.co/YaxXFAbBZq

[Kangkan Boro @kangkanB]

@ycombinator @srijanyaham @jeankaddour Let’s goooo!

[Y Combinator @ycombinator]

Sagaland is a UGC games platform where players create and remix games using AI.

They're starting with interactive story games and have hit $200k ARR in 4 weeks.

Congrats on the launch, @srijanyaham & @jeankaddour!

https://t.co/YaxXFAbBZq

[∞ @TheFalseNein]

The entire Arsenal frontline returning for Spurs