4 ms·
Isn't that something you just open a devtools for and have fixed in like 2 minutes? For me, it got frustrated debugging on a real LPDDR4 controller/phy and hav
by megous 4mo ago
Isn't that something you just open a devtools for and have fixed in like 2 minutes?
For me, it got frustrated debugging on a real LPDDR4 controller/phy and having me in the loop slowing it down, so it wrote an HW emulator to be able to run the original LPDDR4 training aarch64 binary from the manufacturer, to see what register writes it was making and to compare with the opensource rewrite it was implementing.
Mildly amusing. :)
- bschwindHN 4mo ago> Isn't that something you just open a devtools for and have fixed in like 2 minutes? Not if you're an LLM influencer! Gotta keep up with the downpour of blog links or you'll look like you're falling behind on the latest and greatest.
- fg137 4mo agoThis. Depending on who you are talking to, that's the wrong question to ask. ROI is not measured in terms of actual productivity. It is measured by how many people read their article/watch their video.
- system2 4mo agoPeople burning tokens for the most beginner HTML/CSS problems and writing about it is concerning.
- simonw 4mo agoI dunno about beginner, I've been doing HTML+CSS for a few decades and I still find bugs where Safari differs from Chrome+Firefox pretty hard to figure out.
- NichoPaolucci 4mo agoWe are at the point where AI starts to seriously impact abilities. Sure, a 2 line CSS fix is the solution, but the human “behind the wheel” has already prompted 6 times and gotten 80% there. It’s been “easy” thus far. No shot they are going to FINALLY look at and edit the code. It’s just one more prompt and the agent will probably fix it, right? It’s wild. I’ve been in the situation. 80% into a project I COULD probably take over, but realistically? 2 more lines of me prompting could fix it, it’s too easy to avoid the hard work of understanding the code, logic, architecture, etc…
- AtNightWeCode 4mo agoWell the solution is incorrect. The problem seems to be that the css code does not normalize to box-sizing: border-box; among other things. The bad prompt by the author probably sent fable into the wrong rabbit hole
- eclipticplane 4mo ago$12 in tokens and the OP wasn't even at the computer. OP was working on a personal matter, arguably way more valuable than fixing a CSS scrollbar.
- uludag 4mo agoHere's what the $12 payed for: https://github.com/datasette/datasette-agent/commit/a75a8b727b42c30ced1fc41dc8add7eb9f04fefe https://github.com/datasette/datasette-agent/commit/a75a8b72... Such a fix would have only required basic CSS knowledge and taken max 5 minutes with the HTML inspector. Paying $12 to save 5 minutes ($144/hour) is a decision that a lot of people wouldn't be comfortable making.
- deleted 4mo ago[deleted]
- fg137 4mo agoTheir response: https://news.ycombinator.com/item?id=48499478 https://news.ycombinator.com/item?id=48499478 I am amused by the "I am an LLM researcher, so wasting tokens to do basic things is totally justified" perspective. I have a lot more critical views of this author, but I'll just stop here.