• 62 Posts
  • 1.03K Comments
Joined 3 years ago
Aquileo | cake
Cake day: July 1st, 2023

Aquileo | help-circle
  • It’s literally the same playbook as all the other shitty tech companies.
    Uber had very generous offers and was totally worth it at first, until they choked out the existing cab market. Then they started exploiting drivers and customers.
    AirBnb was a great option at first, until they choked out the existing vacation rental/hostel/hotel market. Then they started exploiting hosts and guests.
    Hell, even here in Germany we had this pretty neat new Grocery service called Flink. It started somewhere around Covid and at first it was absolutely great. Super fast delivery and generous “20€ off on orders over 30€” coupons. As soon as they got a solid grip on the market and people got used to it they raised prices, cut all good promotions and their drivers honestly look super miserable nowadays.

    What I’m saying is, you really have to be a sucker to fall for this scheme over and over again with every new tech company that comes along.








  • Not too long ago, I was assigned Review on a clearly vibecoded PR. It was for a feature that parsed hourly values from a csv file and put them into the Database. Easy enough at first glance, just loop through the hours of the day and grab the value for each hour, with an error if your file doesn’t contain all the hours of the day. But for some reason my coworker not only decided to introduce a whole new “hour of the day” type to loop over instead of looping over numbers, but that type explicitly contained 25 values. It was the numbers 0 to 24. There was even a comment next to it saying that it had 25 values. All test cases were green too, because the test data was generated specifically to satisfy the tests. I had to explain to a grown ass adult that the day only has 24 hours and it wouldn’t work because there will never be a value for “24:00” in the real data. That specific coworker already made really stupid mistakes before AI was a thing, but at least those mistakes were easy enough to spot and didn’t secretly propagate themselves through thousands of lines of code.



  • python@lemmy.worldtoProgrammer Humor@programming.devWelp
    Aquileo | link
    Aquileo | fedilink
    Aquileo | arrow-up
    21
    ·
    24 hours ago

    I spent like an hour yesterday bullying Claude out of using a ResizeObserver, Refs and a useEffect construct just to fix the height of a container (there was a bug where the container didn’t properly scale down in height because some weird hard-coded properties in an external component inside of it). I knew that it had to be solvable with just the right css selector, but I was lazy and didn’t want to manually go through the html and figure out which selector on which component would be the right one. And on paper “Go through this massive block of html and check which property is out of place” should be the kind of use case where LLMs actually work. The stupid thing introduced two new different catastrophic failure modes where the entire browser crashed due to excessive rerenders before it found something that even remotely worked. And then I had to spend another hour stripping out unnecessary style properties it glued on while looking for a working solution. In the end, I probably would have been much faster doing it by hand.