I needed some wood filler this weekend and asked one of my personal agents to buy some for me. Apparently @amazon is now blocking agents, so I had to buy off @Walmart.
Amazon has a better user experience, but Walmart has a better agent experience, so I guess that is where I shop now.
My god this is such a good speech that every SWE needs to hear. You know what? Every person should hear it
Keep the happy memories, eyes on the reality, be excited about the future. That’s the best that anyone can do
Two things early founders often get wrong, and should remember:
1) Building culture can feel like it's just fluff at the start. Until you start to raise capital or hire teams, and then you see how it shapes everything you do moving forward.
2) You should build a team so talented that it makes you slightly uncomfortable to be with them, because you know you are going to have to raise your game to keep up.
Waiting for models to respond has me context switching constantly trying to multi-task work across pauses.
I wish I had multiple brains or some sort of biological threading capability...
Telegram founder Pavel Durov on what separates A Players from B Players
“I can recall a few instances in my career where firing an engineer actually resulted in an increase in productivity,” Telegram founder Pavel Durov begins.
He gives an example of two Android engineers building an app that are having a hard time hitting deadlines:
“You think, ‘I probably have to hire a third engineer.’ But then you notice that one of [the engineers] is really weird — falling behind schedule, complaining, not assuming responsibility — and you ask, ‘What if I just fired this person?’ Then you fire this person, and in a few weeks you realize you never needed a third engineer. The problem was this guy who created more issues and problems than he solved. It’s so counterintuitive because in developing tech projects, you tend to think that you just throw more people into something and things get solved miraculously.”
Pavel continues:
“The other thing that people don’t realize is how demotivating working with a B Player is. Everyone can tell if the other engineer they’re working with is really competent. If the person is asking the wrong questions and they keep lagging behind, at a certain point if you’re an A Player, you get get this dissatisfaction and feeling that you are not able to realize your full potential and accomplish what you’re really meant to accomplish because of this person working next to you (or pretending to work next to you).”
Pavel reflects on what it is exactly that separates these B Players from A Players:
“In some cases it’s not because the person is lazy . . . It’s not about experience. More often it’s about natural ability and persistence. In 90% of cases, it’s just the inability to focus on one task for an extended period of time. Not everybody has this ability. So for people who do have this ability, it’s an insult to work alongside someone who is distracted and cannot go deep in the projects that they’re responsible for.”
Source: @lexfridman (Sep 2025)
Today we're highlighting insights from our CEO, @iantien, as he breaks down what AI transformation really means for organizations operating in high‑stakes, security‑first environments.
As AI reshapes how teams coordinate, decide, and execute, Ian underscores why secure, self‑hosted, and sovereign collaboration is becoming essential infrastructure for defense, government, and regulated industries. His perspective focuses on practical, mission‑aligned AI adoption, strengthening operational agility while maintaining full control over sensitive data.
#AITransformation #SecureCollaboration #MissionCritical #SovereignAI #OpenSource #DefenseTech #GovTech #DigitalModernization #OperationalResilience
Everyone thinks "do things that don't scale" is about building relationships with early users.
Yes AND it's about generating mistakes at maximum density.
When you're doing everything manually (onboarding, support, delivery) you hit errors every hour. Each error teaches you something the dashboard never will.
The manual work IS the learning. Automate too early and you freeze your ignorance in code (and now markdown).
There is a transition here for people across the workforce: the working world needs fewer measurers and more builders
More revenue means there will be more activity and more building, and in the shorter term less measuring
.@iantien and @lisamartinmedia join @NPetallides to discuss $GOOGL and the AI stack, including the latest partnership and product announcements from its cloud event, such as eighth-generation TPUs, and where the next wave of enterprise value could be generated.
For more market news, tune in at: https://t.co/EVvMrBi3xF
This is the simplest distillation of what I have learned about agentic engineering this year
Push smart fuzzy operations humans do into markdown skills. Fat skills.
Push must-be-perfect deterministic operations into code. Fat code.
The harness? Keep it thin.
Our cracked team just used Software Factory to rebuild and replace Jira in a little more than a month.
We first spent 3.5 weeks planning. This is Software Factory’s superpower.
It allowed our lead PM, Designer and Architect to thoughtfully describe and detail exactly what they wanted. Software Factory then did the heavy lifting in filling in the blanks and allowing our senior tech folks to sharpen the direction of what they wanted.
Then in 2.5 weeks 2.5 junior devs built a replacement.
This will launch as an updated Planner module inside of Software Factory on Tuesday.
It’s beautiful, clean and super useful.
Try it here: https://t.co/fkfTXgdfXK
Airbnb founder Brian Chesky on how to design an amazing user experience
“How do you make something for a million people? I don’t know where to start. But if you pick one person, study them, and take their journey, you can actually build something really personal. You can design something and keep iterating until they love it. Don’t stop improving it until that person loves it, and you’re not allowed to move to the second person until the first person loves it. Then you get the second person and keep iterating until they love it. And so on.”
As Brian argues, designing the perfect experience for one person is a much easier place to start than trying to design something for a million people. You can figure out how to scale it later.
“If you can design something really amazing using the hand-crafted part of your brain, then you can reverse-engineer how to industrialize this millions of times over. And what happens is people love your product and they tell everyone else about your product.”
When people truly love your service, they become your marketing department. But counterintuitively, the biggest and best products seem to mostly get started by solving a very specific problem for a very specific user.
Video source: @StanfordGSB (2023)