I wish Slack was: - Agent-first - Beautiful to use - Integrated with agents natively so your Hermes or OpenClaw lives inside it - Huddles worked seamlessly and were fun - Built for teams of 1-3, not just teams of 300 - Truly a second brain similar to Obsidian - Searchable without wanting to throw your laptop - Designed around async, not constant interruption - Voice first for mobile - A place where I could see who's working on what right now without asking anyone - Smart enough to know the difference between "I need you right now" and "whenever you get to this" - A workspace where my agent could tap someone else's agent on the shoulder and coordinate without involving either human - Designed so the new hire on day 1 has the same context as the person who's been there 3 years -Something that felt like walking into a room of people building, not walking into a room of people typing - A place where decisions are first-class objects - Able to auto generate SOPs, skills, agents etc from conversation history - Something that rewards deep work instead of punishing it with 47 unread notifications

"Engineering, product, and design are all merging into a 'builder' role" Yeah... I'm not so sure. This feels like an oversimplification and podcast talking point. Reality is a lot more complex. Even with 1000 "Member of Technical Staff" titles, someone still has to wake up and care 100x more about Product or Design than anyone else. It is their Main Thing™ That's not to say MTS titles are universally bad, but I think they're an example of this 'builder' talking point that's become bastardized. AI and coding agents have made generating code easy and yet... you're in for a world of pain if non-engineers ship a bunch of slop and don't have great engineers to tame the complexity. The SF hivemind has a tendency to overfit what works at startups for every company. And to be fair, sometimes this is true! Startups can be a leading indicator for how the industry is changing and often cause disruption. However, it is going to be incredibly hard to disrupt the extremely human parts of corporate jobs. You really think there's going to be a PM who also does some engineering and design on the side at JPMorgan Chase? This is true for the simple parts of most jobs, like people wanting to have ownership over something and do good work, move up a career ladder, support their family, get paid well, make an honest living... And also the hard parts: internal politics, some critical business system that has a bus factor of 1 which has been running for 15 years and isn't documented anywhere because it's that guy's job security. The real world has a lot of this stuff. It's easy to pontificate about all roles collapsing but it's actually really nice to have a specific person or team who is an expert in one thing that you can work with. I don't expect that to change. Further, I think AI disruption to knowledge work will take decades to play out because it is more fundamental to the human condition (e.g. sociological/organizational) than pure intelligence.

What's the largest landlocked country in the world?

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]

Hot Take: 90% of people using these models are building simple web software with a backend, which has low *fundamental* complexity - the high *incidental* complexity is what makes them need expensive models. Put another way - choose a simpler stack with a clear canon & you'll be able to build to your heart's content and save 95% to 99% on models.

Lots of "AI influencers" out there with god-awful takes. It's embarrassing. Look, we're all trying to figure this thing out, but it's not magic: 1. Ship real software, not AI theater. LOC count, agent swarms, and token burn are not progress unless users get something reliable. 2. Let requirements harden from evidence. Use AI to discuss, prototype, and test assumptions before locking the plan. 3. Treat code as cheap and understanding as expensive. Deliver increments quickly, throw away bad first passes, rewrite, and refactor aggressively. 4. Keep humans and AI in a tight loop. AI generates options quickly; humans supply taste, domain judgment, trade-offs, and the ability to say "no." 5. Build around people with taste and ownership. They should set clear boundaries, trust AI to execute within them, and have the standards to redo, undo, or throw away the result. 6. Prefer dialogue over prompt bloat and rigid process. Talk through the problem, agree on direction, then write down only what needs to persist. 7. Reliable, tested software is the measure of progress. Abundant code, docs, prompts, traces, and tool output are useful only when they improve the system. 8. Sustainable pace is non-negotiable. AI makes nonstop work seductive: late-night agent babysitting, context spirals, and fake urgency. A process that burns people out or degrades judgment is broken. 9. Technical excellence matters more when generation is cheap. Understand the architecture, probe the output, push back hard, and review security before plausible broken systems become production systems. 10. Simplicity is the art of refusing generated complexity. AI can generate code, dependencies, abstractions, and documentation faster than you can own them. 11. Good systems emerge from iteration and pruning. Prototype, learn, rewrite, document, and refactor. Do not expect unsupervised agents to develop taste or conviction. 12. Use AI to amplify agency, not replace it. It should help you learn faster, explore further, and spend more time where your taste and judgment have the highest return. If it makes you passive, you are using it wrong.

sorry folks: htmx.org/CVE-2026-3682-1/

Got some free coins so I tried Cursor again.. completely different at this point, but i really like it I have no horse in the race, but one thing i feel pretty confident in: there's no reason to raw dog codex or claude code at this point, why would you lock yourself out of other models whatever UI or interface you prefer, there's like a dozen good choices, where you can freely pick between models dont sleep on the chinese ones, they cook

The "AI experts" flexing in your feed are full of shit. Weirdos like @bcherny exist, but this is the secret sauce for everybody else: 1. You talk with the clanker until you agree on the thing. 2. It does the thing. 3. You test the thing. 4. You tell the clanker how to improve the thing. Codex, Claude Code, Amp, Pi... doesn't matter. Add an AGENTS.md and a couple skills if you're feeling fancy. That's it.

When I was an intern at Microsoft, the dude I shared an office with used a blank keyboard so he could switch back and forth between QWERTY and DVORAK. It was basically magic to me that his brain could do both!

When I was an intern at Microsoft, the dude I shared an office with used a blank keyboard so he could switch back and forth between QWERTY and DVORAK. It was basically magic to me that his brain could do both!

One guy. One Navy ship. One file. 1 trillion databases. He built it alone in 2000. And gave it away forever. 🤯 Meet D. Richard Hipp 🇺🇸 > American developer. Born 1961 in North Carolina. > In 2000, working as a contractor on a US Navy destroyer. > Got frustrated with bulky databases that needed servers and setup. > Built SQLite in his spare time ~ a single-file database engine. > No server. No installation. No configuration. Just one file. > 25 years later, every iPhone, Android, Mac, and Windows PC runs SQLite. > Powers Chrome, Firefox, Safari, WhatsApp, iMessage, Skype. > Runs inside Tesla cars and commercial airplanes. 🚀 > Over 1 trillion SQLite databases active worldwide today. > Put the entire codebase in the public domain. Zero royalties forever. > Trillion-dollar companies use his code. He's never charged a cent. > Still maintains it full-time with a tiny team of 3. > Pledged free support and updates until at least 2050. > No VC money. No acquisitions. No spotlight. Just code. Every app on your phone runs his invisible masterpiece. Most engineers build for fame. He built for forever. Database GOAT. 🐐

here's a chart showing them being a few months behind and catching up modern day is amazing you can have whatever narrative you want!