Dr. Yamaha Kawasaki
5.2K posts


happy to announce that the nicest guy on twitter @aarondfrancis is gonna MC @BigSkyDevCon this year again!
we've got an unbelievable lineup of speakers over two venues this time (Friday night @ the rialto in downtown bzn, Saturday all day @montanastate)
get your tix kids!
English

@htmx_org The problem is computer literacy. If users weren't expected to "figure it out" UIs would be more intuitive.
It felt so difficult for me to learn how to use an iPhone and I'm not even joking.
English

daily reminder that @scumitchell created possibly the greatest open source marketing video in history (it is, its not close)
(thank u @ahmadalfy for the reminder for the reminder)
htmx 4 coming soon!
scum@scumitchell
@htmx_org htmx4 αlpha 3 has dropped
English

@htmx_org I usually make my clickable resources only LOOK like a button when you hover, otherwise it's just a span.
English
Dr. Yamaha Kawasaki retweetet

@suryanox7 Nah but I worked with a guy that would do this with awk
It was always magical
English

@IgnibyteDev @bendee983 yeah I agree, but this gets to the core problem of testing: it's scientific rather than mathematical.
When have you tested enough? When have you done enough experiments? It's great and probably better than not writing tests at all, but it comes with caveats.
English

e2e during the agent loops are solid. The agent should load the browser and check its work. Then once it’s verified it creates a playwright test for regression.
Unit tests + architecture (phpstan, phpmd, phpcs), mutation testing, e2e and playwright will catch most failures during the build. They must be enforced though through hooks otherwise the agent will ignore them if they can.
English

Prove me wrong. I think the "unit tests is all you need" mentality is wrong. Here's why:
Unit tests verify what the LLM-generated code should do, not what it shouldn't. The AI might hallucinate a bunch of nonsense code and functions that have nothing to do with the intent and goals of the application.
The code will work perfectly fine but will also be sub-optimal. When it is a bottleneck function (something that runs thousands of times per second), you want it to be fully optimized. Every line of code matters.
This is why I think whether AI writes the code or not, you should be able to review and uderstand it, at least the bottlenecks that can cause massive performance issues.
Happy to be proven wrong, or share your experience if you've been able to address this.
English

@potetm literally every stupid thing everyone has written was thought to be better than the other stupid things beforehand
English

I've always found the idea of "tech debt" to be borderline ridiculous.
it meant some programmer wrote and shipped code they didn't understand. that's just a (stupid) choice, not a shrewd calculation.
until now.
now tech debt is one of the realest things in software.
Tim Pote@potetm
@heuristics nope the analogy holds and, for the first time really, is quite apt.
English

@ai_backend_engr @abolorreeeee @uthman_dev yeah my perspective is different. Where I work I am a sort of one man show. I work on my own projects, direct things with my "people", but otherwise stand back.
I really hate working in teams to be honest.
English

@OhMeSoSorry @abolorreeeee @uthman_dev idea could spark from community conversations I guess, also makes you feel like you not alone
Development is a teams work, maybe your perspective is different
English

@ai_backend_engr @abolorreeeee @uthman_dev why do you need a community? Read the docs. Write code. You can talk to an LLM about your code quality, best practices, etc.
Use the socratic method.
English
Dr. Yamaha Kawasaki retweetet

🃏 Interesting fact: Dirty Work (1998) — This cult classic comedy directed by Bob Saget stars Norm Macdonald as a deeply cynical slacker who starts a revenge-for-hire business with his best friend to raise enough cash for a heart transplant. The film’s chaotic production became a masterclass in Norm’s legendary, uncompromising comedic style, as he constantly fought the studio to keep the script’s raw, pitch-black edge.
English
Dr. Yamaha Kawasaki retweetet

@oriSomething @munawwarfiroz If you have to learn all the NaN rules it’s not simple lol
English

@munawwarfiroz I find JS simple. I just learned all the NaN rules
English

@aminnnn_09 youtu.be/SxdOUGdseq4?is…
There is also a Clojure documentary on YouTube that was created recently.

YouTube
English

@OhMeSoSorry Never heard of it, what's this if you could talk about it a bit
Vododara, India 🇮🇳 English












