hakesson

7 ms·

1. 1.▲
   by hakesson 16d ago

   I like the idea - but I have two concerns. Often an AI reads info that might be outdated and then assumes it is right. It doesn't really have the concept of "this is old info, maybe I shouldn't trust it". How about creat
2. 2.▲
   by hakesson 17d ago

   I have a friend who was drugged (date-rape style drug) and convinced to empty his account in an ATM. Woke up in a hospital without any memory of it. Some EU law forces banks to reimburse you when you didn't get the money of your free w
3. 3.▲
   by hakesson 17d ago

   I've had to live with shipping software with really poor quality that had loads of small bugs. My Product Manager forced me to. However, at the end, the customers seemed happy, and I have to admit that I was partially wrong. The QA guy
4. 4.▲
   by hakesson 24d ago

   For the "harder tech" part: I played around with a "vibe code" project to see how far it gets. It's a cargo workspace linter that does things like find unused feature flags, unused pub, etc. Guiding it only on high-
5. 5.▲
   by hakesson 27d ago

   Yeah, I'm a great fan of both HTML and CSS "can do that". I find more useful things on the CSS side like :has, keyframes and container queries. Why duplicate code when you have it for free :)
6. 6.▲
   by hakesson 2mo ago

   How do you detect AI slop today? I mean some 6 months ago it wasn't that hard but today, especially if you give it some simple instructions to be brief and honest, I can't really see the difference... And I am someone that spends