bro to bro: never make a big move when you’re feeling any extreme emotion (frustration, anxiety, lust, betrayal etc)
that usually ends up being regretful, save your judgement for when you find calm and can think straight about that situation and see if you’re still on to the same decision
in this process you also need to be careful because the act of thinking about that situation itself is likely to put you in the same emotional response and confuse you for being decisive in calm
talk to someone you trust their judgement and have a demonstrated history of smart judgement and who also is not involved in that situation of yours so it doesn’t serve to their best interest
AI red flags:
- "My marketer agent just finished a meeting with my chief of staff agent - just 2 of the 127 agents on my books"
- "The agent did it, not me"
- "I've invented a coding language for agents"
- "I've got 250K tokens in my context before I send a message, is that normal?"
- "Opus 5 is way dumber today than yesterday, secret nerf?"
- "Peasants, gaze upon my 600-line CLAUDE.md, my results are incredible"
- "LOOK WHAT OX ALPHA JUST ONE-SHOTTED, SOFTWARE ENGINEERING IS DEAD"
- "All human knowledge is worthless now"
- "I turned 600 coding books into a skill"
- "Coding is solved. Bugs are not solved"
Most software engineers are facing an identity crisis bordering on depression.
As CTOs aggressively evangelize tokenmaxxing, a class divide ensues.
The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working.
The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy.
This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
🌘 Kimi-K2.7-Code, our latest coding model, is now released and open-sourced!
🔷 Improved coding & agent performance over K2.6: +21.8% on Kimi Code Bench v2, +11.0% on Program Bench, and +31.5% on MLS Bench Lite.
🔷 Reasoning efficiency: Less overthinking, with 30% lower reasoning-token usage compared to K2.6.
🔷 Long-horizon coding: Improved instruction following, higher end-to-end coding task success rates.
⚡️ 6x High-Speed Mode coming soon!
🔌 Available today via Kimi API and Kimi Code.
🔗 Kimi Code: https://t.co/uvoSJKyGCY
🔗 API: https://t.co/EOZkbOwCN4
Hands down, the best AI series right now
CS 153 at Stanford, published on YouTube
Speakers include Sam Altman, Jensen Huang, Satya Nadella, Andrej Karpathy, Ben Horowitz
Here's my 6 hour conversation with @dhh, a legendary programmer, creator of Ruby on Rails, author, and race car driver. This was a fun and inspiring conversation on everything from the future of programming & AI to the nature of happiness & productivity to the value of family, getting married and having kids.
X limits video length to 6 hours. So this full convo doesn't fit (by a few minutes). So, the first 6 hours are here on X. The full version is up everywhere else (see comment).
Timestamps:
0:00 - Episode highlight
1:21 - Introduction
2:32 - Programming - early days
19:57 - JavaScript
30:16 - Google Chrome and DOJ
38:03 - Ruby programming language
45:14 - Beautiful code
1:03:15 - Metaprogramming
1:06:36 - Dynamic typing
1:13:55 - Scaling
1:26:47 - Future of programming
1:44:18 - Future of AI
1:50:13 - Vibe coding
1:58:45 - Rails manifesto: Principles of a great programming language
2:23:11 - Why managers are useless
2:32:32 - Small teams
2:38:39 - Jeff Bezos
2:53:57 - Why meetings are toxic
3:01:43 - Case against retirement
3:09:00 - Hard work
3:14:38 - Why we left the cloud
3:17:48 - AWS
3:27:07 - Owning your own servers
3:33:19 - Elon Musk
3:43:01 - Apple
3:54:48 - Tim Sweeney
4:06:22 - Fatherhood
4:32:04 - Racing
4:59:08 - Cars
5:04:26 - Programming setup
5:19:35 - Programming language for beginners
5:32:53 - Open source
5:41:46 - WordPress drama
5:53:03 - Money and happiness
6:01:56 - Hope
Absolutely love Inertia and Rails and in honor of the NextJS folks opening up their Chat SDK template, I'm putting together a Rails, inertia, Ruby LLM, and AI SDK UI template!
Goal here is to get the best of Rails, and the AI SDK React frontend UI handling with the unified interface of Ruby LLM! With this, I have an adapter going for SSE handling with the Data Stream Protocol 😃
Inertia Rails is awesome, right? That's why we're creating a page to highlight community efforts, including videos, articles, demo applications, and open-source projects. Join us by sharing your work—or someone else's—we'd love to feature it!
Did you know you can install Windows 11 without any bloatware simply by selecting "English (World)" as the Time & Currency format at the initial install?
What is the favourite development methodology at your company?
TDD: Test Driven Development
FDD: Founder Driven Development
MDD: Metrics Driven Development
VDD: Vibes Driven Development
Cold showers are the gateway to flow and energy and peace. I’m not exaggerating. It’s the entry point from which you will learn the power of the mind over the body.