Haven't pinned down exactly why, but when switching from the Mac to Windows, Windows feels snappier. While the Mac is a faster machine.
I'm a simple man. Writing code with Purple Disco Machine on the background is all it takes to make my day.
Look at me optimizing my workshop instead of building the thing.
The whole dev space is addicted to productivity porn.
"Never ask a barber if you need a haircut."
Never follow advice from someone at Anthropic or OpenAI how much tokens you should burn.
My friend @WdeB released a book! So proud of him, go read it, designer or no designer, it will make you a better builder:
productdesignpsychology.com
GitHub user from almost day one (#825), and I share Mitchell's frustration. Scale and slop are blamed, but it's the enshittification eating the whole web.
Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…
Petar Radošević retweeted
Bullshit. Winning teams have the psychological safety required to win - not because they coddle each other, but because they trust each other to perform, and hold each other accountable. It takes a *very high* degree of psychological safety to do that.
Don't forget the *actual definition* of psychological safety: the shared belief that the environment is safe enough to take personal risks. Everything about building winning teams is helping people get comfortable taking more risk - with the product, with their career, with their relationships to each other.
What those teams aren't is easy to build, or zones of swaddled comfort where nobody does a bad job and everyone gets praised. High performance machines care about psychological safety *because* they care about winning. You have to build honest, real trust - not the kind that comes from telling folks what they want to hear, but the kind that comes from *telling the truth and doing what you say you will do*. Then being judged on the outcomes of your choices.
I get that it's popular right now to say shit like this, but it's just bad advice. Even they don't actually believe it when you hear them talk about how people should behave.
"High performance machines don't have psychological safety. They're about winning."
Keith Rabois (@rabois) was COO of Square, part of the PayPal Mafia, an early investor in Stripe, Palantir, Airbnb, DoorDash, and Ramp, and a 2x founder. He's spent 25 years obsessing over how to build world-class teams.
In our in-depth conversation, we discuss:
🔸 How to identify undiscovered talent
🔸 Keith's barrels vs. ammunition hiring framework
🔸 The three traits of the best-performing companies right now
🔸 Why talking to customers is actively harmful for consumer products
🔸 Why the PM role is dying
🔸 The specific interview question he asks every senior candidate
🔸 Why CMOs (not engineers) are becoming the #1 consumer of AI tokens
Watch now 👇
youtu.be/xCd9ykretlg
AI makes bad architecture fail faster. Clean abstractions aren't optional. Without them, the mess compounds at machine speed.
i have a friend that had access to mythos
he went from being single, to retired and married with 5 kids in two weeks. what a model.
The most powerful form of AI collaboration is not AI generating code but using AI for understanding code.
Things are moving so fast right now. I already read a lot during the week, but I still have a whole backlog of interesting articles that I work through during the weekend.
Design is the work now. Cognitive debt is the newest drag on productivity when building with AI.
petar.dev/posts/cognitive-de…
3rd rewrite of a new agentic system in 48 hours. Frustrating? Yeah, a little. But I'm learning so much.
It's a relentless loop: spend hours on the design, execute fast, hit reality, learn, restart. Each pass I'm making fewer mistakes and building real intuition for how the system I'm building works best.
I created two skills which I always found to be gotcha's when working with #elixirlang and LiveView. Both can have a big impact on user experience.
First, LiveView and optimistic updates, making sure that the UI stays responsive, even when there is latency.
github.com/wunki/amplify/tre…
Second is working with forms, where you have to make sure that forms don't get wiped on reconnect, or when and how to use debounce to make sure you don't spam the backend.
github.com/wunki/amplify/tre…
Let me know what you think and how we could improve them. PRs or comments are welcome. Let's share best practices so we can use LiveView and all its benefits without compromising on the user experience.
#myelixirstatus
