RickDev retweeted
This is a good example of why I’ll always pay for maintainable software instead of switching to an open‑source personal alternative, which I don’t think will be maintained at all. Most of these "personal software" projects feel like attention farming, not long‑term products.
I’m not just paying for the app, I’m paying for the team I trust to fix bugs, maintain it, and keep improving the tool I work with every day.
RickDev retweeted
Is Muse Wonder full better than opus 5.5?
I gave them the same prompt
goal is to build me a triple aaa level lawn mower simulator i can drink beer and smoke a cigar.
Api equivalent cost :
muse - $4.11
opus - $99.43
It is very clear that muse is not anywhere near close to frontier in 3d tasks like video games, or even printable cad designs.
Even scarier is it burned my $50 plan spending $4.11 in api equivalent tokens.
wut?!
i had to upgrade to $200 plan to finish this run.
RickDev retweeted
- we removed unit tests in favor integration/functional tests
- ci/cd invoice exploded
- we removed cicd, it was slowing down our process
- now our agents deploys our code
- agent decided that database is going to be much faster without users
future looks awesome ☠️
We deleted 800k lines of unit tests from the @sazabi monorepo earlier this week.
Three hypotheses:
1- Unit tests "lock-in" slop code by making it hard to change or remove
2- Unit tests slow down dev cycles by making your agent do more work locally and by increasing CI times
3- Unit tests waste money by making your agent generate more tokens and by adding useless CI runs
Will report back soon with the results!
if you don't look it can't be slop...
RickDev retweeted
junior developers shouldn't be allowed to use AI coding tools for the first 1-3 years of their work.
just as an electrician's apprentice does the menial jobs and learns from their mentor, developers should do the same
developing "code smell" and intuition is so important
RickDev retweeted
Rust devs will spend 3 hours figuring it out themselves.
C++ devs will read the docs.
Java devs will build an entire architecture for it.
Python devs will probably find a package for it.
JavaScript devs : AI, write this for me real quick.
There are two ways to increase B2B sales right now.
1. The Old Way: Send more emails. Pray for a 1% response rate.
2. The New Way: Get deals to come to you.
The old way gets you a 20% win rate on the meetings you do manage to book.
The new way gets you a 50% win rate.
That difference is a 30% lift in sales. In 30 days.
I should know. I helped build the old way.
When I founded ToutApp (backed by a16z), we pioneered the sales engagement category. We built the tools for high-volume outbound. And it worked, for a while. After selling ToutApp to Marketo, I joined the exec team and we ultimately sold to Adobe for $4.75bn. That whole ecosystem was built on the old way.
But today, it's a losing game.
Every company is buying the same lists and using the same AI to write the same emails. Your reps are burning out just trying to get strangers to know, like, and trust them over 10+ meetings from a cold start.
So how do you make the shift?
I get it. Moving away from the playbook that built a multi-billion dollar category feels risky. It feels like you're giving up control. But the math doesn't lie. You can either keep grinding for a 20% win rate or you can build a system that delivers deals with a 50% win rate.
On today's Unstoppable episode, I'm breaking down the new way. A simple, 3-step system to build a machine that brings deals to you.
I'll cover the 3 key principles:
1. The Manifesto Lead Magnet: How to stop selling and start educating with a simple asset that builds trust at scale.
2. The Inbound Engine: How to turn your website and LinkedIn profiles into a 24/7 lead generation system.
3. The Intent-Based Outbound: How to make your sales follow-up 10x more effective by only talking to people who have already raised their hand.
Stop fighting for scraps. Start winning the deals that want to be won.
Watch the full breakdown here:
youtu.be/3J3Bom8eYKI
RickDev retweeted
I just had an experience where fable said I had a memory leak, I asked for details, it refused to tell me any more or fix it
Grok found and fixed it quickly
Fable is generally smarter and more tasteful than Sol, but I'm falling out of love with Fable. Quickly.
1. It's disobedient. It thinks it's smarter than you and follows its own path.
2. It's dangerous. It leaves gaping security holes then refuses to patch them.
3. It's flakey. Some of the best generated AI code I've ever seen has come out of Fable, and at the same time, some of the most bizarre and harmful decision making.
Sol isn't perfect either. It over engineers everything, sucks at writing, and is terrible at design, but I'm now using it about 5:1 over Fable simply because I can trust it.
RickDev retweeted
I am absolutely more productive using agents. I don't know the factor but it's large. However much of that productivity is spent tuning the agents and hardening the product. I'm guessing 30%-40%.
Some might consider that a waste; but I don't. The software I'm creating nowadays is vastly more robust than I'd ever been able to create manually.
I don't mean that the code is better. I mean the surrounding tests are vastly better. I have a higher degree of confidence than I ever had manually -- even when I used very disciplined TDD and Acceptance testing.
And then there's the ability to quickly reorganize the modules and the architecture while keeping those robust tests running. That is a tremendous boon.
RickDev retweeted
Finally non-programmers are leaving the Software Engineering space by becoming "vibe coders". The Software Engineers can now work in peace while those parasites are destroying the codebases of the Big Tech companies. The cancer industry cannibalizing itself. The future is bright.
RickDev retweeted
Azure AI Foundry Service powers this revolution.
Now available, it helps build and scale AI agent ecosystems.
It merges Semantic Kernel with AutoGen for multi-agent applications.
Built for enterprise, it solves adoption barriers.
RickDev retweeted
Lots of apps feel slow nowadays. It must be because of OOP or Clean Code or Design Patterns. It can't be because of microservices or frameworks or just plain sloppy programming.
RickDev retweeted
Voice Chat is now available in all groups—big or small 🙂📷 so when the group chat is going back-and-forth, take it from messaging to talking it out live by swiping up in the chat
RickDev retweeted
New, from the .NET Blog...
We explore C# 14’s extension members that bring coding flexibility! Add methods, properties, or operators to types without altering them. New syntax supports static and instance extensions (cont) msft.it/l/6012Sb8U6
RickDev retweeted
How do you balance architecture and code? #dotNETRocks and Steve Smith (@Ardalis) discuss architectural strategies and the swing between over-designing architecture and getting code written, how the latest tools (cont) msft.it/l/6010SbzN2
RickDev retweeted
The Reliable Web App pattern helps move on-premises apps to the cloud with minimal code changes for a smooth transition. In this #dotNETConf: Focus on Modernization session replay, we learn how Enterprise Web App patterns simplify cloud migration! 🎥 msft.it/6018SnhHa






























