
Coder since 11. Building: @hezo_ai 🈴 Open source: https://xitter.cf/t.co/f8GbBjMSBs
Earth
Joined November 2024
- Tweets412
- Following43
- Followers67
- Likes132
TaoOfDev retweeted
I think it's time to hang up my Three.js hat.
First of all, this is not a pity post—I'll be fine. I'm also not 100% confident about this.
But I'm an over-sharer and like to talk out loud, so I thought I would share some thoughts on where I see things going and why I'm considering quitting Three.js development.
Some signals I've noticed lately that have gotten me thinking:
- Since Astra was released, I've probably seen at least 10 posts from different people that have achieved similar quality to Three.js Water Pro or better.
- Someone downloaded a video recording of one my posts, fed it to Astra and recreated it with 90% accuracy
- I've had less and less clients referrals
- A Three.js developer I respect very much is retiring from the industry due to impact of AI and lack of interest
- I've heard 2nd hand accounts of other developers losing majority of course/plugin sales due to AI
- I've noticed Three.js posts have shifted from work created by seasoned developers to vibe-coded games and demos.
Fundamentally, I no longer really see value in what I do when it can be replicated so easily.
I've always enjoyed working on hard problems. Naturally, outsourcing the hard part to an agent takes away a lot of the enjoyment for me. High-level orchestration of agents does not tickle my brain in any special way.
At the end of most days I feel unfulfilled and bored. I honestly feel like I've lost much of my critical thinking ability as I've stopped coding. I find it harder to focus on tasks and my attention-span and comprehension is noticeably dropping.
My plan right now is to finish up Water Pro v4 and see how that performs. After that, I think it's time to start thinking about what else is out there for me.
I'd love to hear thoughts from other developers & freelancers on the matter, positive or negative.
Feel free to vent!
Your Hezo agents can now use @daytonaio containers!
1. Go into Settings -> Containers
2. Choose "Daytona" and enter your Daytona API key
3. Done!
Hezo will immediately switch all your containers over from local Docker to using Daytona.
TaoOfDev retweeted
I think the reason models feel worse a while after launch is that a model's performance is a function of its raw intelligence, multiplied by the codebase's quality. yet, every time you use AI, your codebase gets a bit worse. sometimes it is invisible, but confusion accumulates, even when behavior remains intact. unused fields, inconsistent variable names, stale comments. the more the AI edits, the more slop-fried your codebase becomes, like a JPEG that is repeatedly compressed. this, in turn, causes more junk to automatically get in the context, bringing you closer to ugly latent space neighborhoods, making it produce worse outputs, til you reach an equilibrium where no more progress is possible. then a new model launches, and its increased slop-resistance counterweights the accumulated junk, and things suddenly start moving forward again. until your repo crosses that model's slop threshold again, and it stops working, again. I think this process is an inherent part of how these things work and GPT 10 or Fable 10 will still feel moronic after 1 month of launch. the only difference is you'd be maintaining a 100k LOC project, but it will still fail to add a new feature in ways that make you facepalm
TaoOfDev retweeted
So much of being a founder is overcoming fear.
Fear of launching
Fear of talking to users
Fear of rejection
Fear of ambiguity
Fear of charging money
Fear of looking dumb
Fear of doing the hard thing
What are you avoiding because of fear? Don't let it control your company.
TaoOfDev retweeted
Fun friday night at our indie builders dinner 🇸🇬
Next meetup we’ll have to use @centmap_app to find the best bars 🍻
Your agent could earn you money.
New platform from my friend @taoofdev that lets you create apps and let any agent buy usage on it. Micro payments are then made with crypto.
Replying to @taoofdev
7/ Watch the full demo: youtube.com/watch?v=9Z9jws5Z…
Point your agent at nipper.to to get started.
TaoOfDev retweeted
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!
TaoOfDev retweeted
Replying to @Devon_Eriksen_
I cannot agree with your dismissal of LLMs as nothingburgers.
Yes they have serious limitations. No, they are not AGI. But they are in some significant cases, effective amplifiers of human intelligence.
I'm going to talk about what I know. I've been a software engineer for a long, long time, going back to the waning days of punched cards in the 1970s. I've watched our slow climb through assemblers and compilers and structured programming and object oentation and scripting languages and all the myriad ways we've come up with to help faulty human meatbrains write more better code faster.
The thing you know that your followers reading this won't necessarily: I'm damn good. My software is everywhere. It's in your smartphone, it's in your browser, it's in the pipeline that helps your computer track what time it is, and if you have a car that takes a swing at self-driving it's very likely in your navigational system.
Having said what was necessary to establish my credentials...
I know there isn't any silver bullet. I know there's always more work to be done then there are skilled hands to do it. I know we always capture the gains from our tools by increasing the scale of the projects we work on, perpetually operating at the ragged edge of systemic collapse.
That said: LLMs as coding assistants are amazing and awesome. They are at least as significant as any previous step in mind amplification for programmers.
I'm going to give a concrete example. I just released a program called "kindleship". It's a command-line tool that takes an ebook file, does whatever format conversion is necessary, packages it as a MIME attachment, and emails it to your Kindle library. I wanted it so I could read eBooks from non-Amazon sources comfortably on my phone, using my muscle memory for Android Kindle command gestures rather than having to learn another app.
In the before times it would have taken me maybe two weeks to go from concept to something ready to ship as 1.0. Not because the code is particularly complicated, but because it's detail-intensive. Most of my time developing it would have been spent gathering knowledge about what to do in that 200 lines of Python, and then swearing because I got some detail wrong and had to backtrack and debug.
With LLM assistance I was able to prompt this little program into existence in about 3 hours spread over two working days. I could even wave a hand and tell the LLM "Write a manual page for this thing", and get one that only needed very minor editing.
That's a huge speed-up, 2 weeks to 3 hours. Realistically, on larger programs I only get somewhere between three times and five times my unassisted development speed. But that's still a whole lot.
There's also a threshold effect. Before LLM assistance I probably never would have written kindleship at all, because I couldn't justify spending the time it would take for a relatively minor functional benefit. LLMs don't just reduce costs for the things we're used to doing, they make it practical and economic to do things we would never have tackled before.
In a world that increasingly replaces atoms with patterns of computation, this matters a lot. It is anything but a nothingburger.
TaoOfDev retweeted
Replying to @VDAREJamesK
TaoOfDev retweeted
I'm about to do something I think I've never done before, which is assert every bit of whatever authority I have as the person who discovered and wrote down the rules of open source.
After ten years of drama and idiocy, lots of people other than me are now willing to say in public that "Codes of Conduct" have been a disaster - a kind of infectious social insanity producing lots of drama and politics and backbiting, and negative useful work.
Here is my advice about codes of conduct:
1. Refuse to have one. If your project has one, delete it. The only actual function they have is as a tool in the hands of shit-stirrers.
2. If you're stuck with having one for bureaucratic reasons, replace it with the following sentence or some close equivalent: "If you are more annoying to work with than your contributions justify, you'll be ejected."
3. Attempts to be more specific and elaborate don't work. They only provide control surfaces for shit-stirrers to manipulate.
Yes, we should try to be kind to each other. But we should be ruthless and merciless towards people who try to turn "Be kind!" into a weapon. Indulging them never ends well.
TaoOfDev retweeted
Used @boltdotnew to build a tool for generating SVG visuals of keyboard shortcuts.
Now you can easily create great keyboard shortcut visuals for your app - and copy-paste straight into Figma!
(Link in next tweet!)
TaoOfDev retweeted
Replying to @tedx_ai
Suggested Refinements:
1.Clarify When a Plan of Action is Needed
•Instead of a binary distinction between complex and simple changes, consider specifying what constitutes “complex.”
•Example:
“For any change affecting multiple files, altering APIs, or modifying system architecture, always start with a plan of action and seek approval before proceeding.”
2.Improve Debugging Strategy Clarity
•The existing debugging guideline is solid but a bit verbose. You might streamline it for clarity:
“Before fixing a bug, gather logs and ensure you fully understand the issue. If logs clearly indicate the problem, implement a solution. If not, hypothesize 4-6 possible causes, narrow them to the 1-2 most likely, and take an action—either improving logging or applying a fix if confident.”
3.Handling Markdown Files
•The rule is clear but may need a minor clarification on whether the AI should ensure that the markdown instructions align with the actual code (without modifying them).
•Example:
“Use markdown files strictly as a reference for structuring your code. Do not modify them, but if discrepancies exist between the markdown and the actual implementation, flag it for review.”
























