@QuanSai@mike_kenyon@pivotal The even cooler part is you can be a Pivot too. It's a mindset about devoting ones self to continuous improvement, being kind, doing the right thing, and doing what works
I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.
Don’t underestimate the value of a skill you have simply because it comes easy to you.
People often tell me how phenomenal of a leader I am and the first thought I usually have is “I’m not doing anything special”.
But the longer I’m in my career, the more I realize the things I view as table stakes don’t come naturally to other leaders.
They can do them, but it takes some level of effort. Where for me, these tasks and/or ways of working often energize me.
POV: claude traveled 6 months into the future and told you exactly how your next move failed.
it's called a premortem.
daniel kahneman (nobel prize-winning psychologist behind "thinking fast and slow") called it his single most valuable decision-making technique.
google, goldman sachs, and procter & gamble all use it before major launches.
here's the problem it solves.
when you ask claude "is this a good plan?" it finds all the reasons to say yes.
that's what it was trained to do. so you walk away feeling confident.
you execute, and spend weeks / months building on top of that plan.
then it blows up.
and you realize the problem was obvious in hindsight, you just never stress-tested it because claude told you it was solid.
a premortem fixes this by flipping the frame.
instead of asking "what could go wrong?" you tell claude "it's 6 months from now and this is already dead. tell me how it died."
that shift turns off claude's optimism because there's nothing to be optimistic about. the premise already says it failed.
so claude stops looking for reasons your plan will work and starts explaining how it fell apart.
claude comes back with every way your plan could die, each one with a full failure story and the early warning signs to watch for.
then a synthesis pulls it all together:
> which failure is most likely
> which failure is most dangerous
> the single biggest hidden assumption you're making (often the most valuable part)
> a revised version of your plan with the gaps closed
you say "premortem this" and give it your plan. the skill handles the rest.
If you bought the S&P in late 2024 betting on 8-10% returns, you're about to lose a decade of your financial life.
Billionaire investor Howard Marks on the JP Morgan chart everyone's ignoring:
At the end of 2024, the S&P was at a P/E of 23. Historically, every single time the market hits a P/E of 23, the next 10 years returned between 2% and -2% annualized.
NO exceptions.
What this means: if you invested $100K at the end of 2024, by 2034 you'll have between $82K and $122K.
Best case (2% annualized): you barely beat inflation
Worst case (-2% annualized): you lose 18% of your money
Either way, high-yield savings beats your "aggressive" portfolio
This isn't a bearish prediction. It's a historical certainty based on the price you chose to pay.
@thesamparr@ShaanVP
NEW POST
Thoughtworks internal IT use a workflow for agentic programming called Structured-Prompt-Driven Development (SPDD). @WeiZhang595190 and Jessie Jie Xia describe how this works with a simple example plus details in a github project.
https://t.co/6cHnSPWr6L
Over the past month, some of you reported Claude Code's quality had slipped. We investigated, and published a post-mortem on the three issues we found.
All are fixed in v2.1.116+ and we’ve reset usage limits for all subscribers.
Contrary Take: Self-esteem & self-belief is the greatest gift you can give a child entering adulthood.
Don't remind them they are just ordinary or kick them down a notch. Life will do that enough.
Make every kid (academic or not) feel like they have something that is special..
I was having a conversation with @mitchdennydev about how we can use agents more effectively to burn down our backlog with high quality.
This what he said:
"This is probably the true economic barrier right now - attention.
We need to make it so that identifying the problem is effectively the same as solving the problem."
This doesn't apply to all problems equally, but there are a large set of low hanging fruit, easy to fix problems that a background agent can burn through pretty much autonomously with minimal review assuming the right systems are in place to ensure high quality (this is the hard part right?). This is the infrastructure I am now obsessed with creating.
As I volunteer for more orgs, I’m realizing the sheer number of employees that simply don’t feel appreciated.
Coupled with leaders not realizing how far simply acknowledging and appreciating someone’s efforts can go.
People may like their companies to show appreciation in various ways, but if you’re only telling your people what they do wrong, make it a goal to also tell them what you appreciate about what they do.
Can’t think of anything you appreciate about their work? Let them know how they can do better and coach them.
everyone wants a village, but no one wants to be a villager
> drive your friends to the airport
> go to their party even when you're tired
> stop cancelling last minute
> host at your place
> support the wins & losses
it's worth every ounce of effort
The token cost to build a production feature is now lower than the meeting cost to discuss building that feature.
Let me rephrase.
It is literally cheaper to build the thing and see if it works than to have a 30 minute planning meeting about whether you should build it.
It’s wild when you think about it.
This completely inverts how you should run a software organization. The planning layer becomes the bottleneck because the building layer is essentially free. The cost of code has dropped to essentially 0.
The rational response is to eliminate planning for anything that can be tested empirically. Don’t debate whether a feature will work.
Just build it in 2 hours, measure it with a group of customers, and then decide to kill or keep it.
I saw a startup operating this way and their build velocity is up 20x. Decision quality is up because every decision is informed by a real prototype, not a slide deck and an expensive meeting.
We went from “move fast and break things” to “move fast and build everything.”
The planning industrial complex is dead.
Thank god.
🥈 Elisa by Jon McBee
A visual programming environment for kids where you snap blocks together and Claude spins up agents to build the real code behind the scenes.
The first user: his 12-year-old daughter.