[go: up one dir, main page]

toofpic

  • 3 Posts
  • 912 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle
  • toofpictoFuck CarsWho Would Win?
    link
    fedilink
    English
    arrow-up
    1
    ·
    45 minutes ago

    I have a phev car, and I almost never charge it - 2.5h of charging and going to parking garage to unplug was too much of a cost to be offset by “almost free” 50km of range. Guess who is charging the car now?











  • toofpictomemesI kinda like it
    link
    fedilink
    arrow-up
    2
    ·
    10 days ago

    Years ago I saw a lot of obscene/agressive cards in Berlin - grandmas flipping birds, punks grabbing their junk with “Fuck off” as a title, etc. Gotta stock up on them if I see them again. You’re right, postcard sending is a lost art.






  • Sure! I’m not a fan of Gimp though. If we talk of free options, Krita is great. It is made mainly for raster art, but it has the vector stuff too. It is much more intuitive, and you probably wouldn’t be asking basic questions, just because in most cases it’s quite clear how to do something.
    Gimp feels like it was made “by designers developers for designers” ;)



  • Yes, I had the same idea. Just weird, because the post is about AI, so if someone doesn’t like it that much, they could just downvote the post without going in. I hoped maybe someone has other ideas regarding the topic. Because even when I agree that AI datacentres have a devastating negative environmental impact and have to be regulated better, LLMs as tools are super useful for some kinds of work - I’m an IT manager, and before AI, if I wanted to build something on my own, I would need to hire developers (I can write some simple code, but not on a level of building a good application from scratch), but now I’m a one-man-team. “Don’t blame the gun…”



  • I am vibecoding an app now, so I started with docs in the repo just because everything is in the repo. But mow I’m relying on this even more. The reason is that problems with session happen - context compacting, being out of tokens mid-implementation and continuing later, etc. So on several occasions, the agent started writing a feature based on my detailed explanations, and finished however it felt like finishing, because my detailed explanations were lost. So now it’s alvays:

    • Keep my ToDo exactly as I phrased it, IN A FILE
    • Plan out the implementation, IN A FILE
      Now, there’s a zero chance any details of my request will be lost completely. And even if something happens mid-implementation, the chat has everything to track back and see what was done, and what wasn’t. We already had a steict TDD policy, so now both tests and docs are there long before any coding actually happens