• 0 Posts
  • 21 Comments
Joined 3 years ago
cake
Cake day: July 24th, 2023

help-circle
  • Yeah I think the route of Norway makes more sense. Prohibition failed historically multiple times. I think education and factful discussions (pros/cons) without irrational condemning drugs would actually be a sustainable long term solution for addiction (because let’s face it, it’s mostly about unhealthy addiction).

    Just legalise all kinds of substances without e.g. ads and other measures that effectively reduce the issue. And give proper education early (ideally from long term addicts, so that it’s believable and properly shows the issues).

    We see with weed, opiates and currently growing cocaine where uncontrolled markets go and promote addiction…

    I doubt that this will be much different with tobacco in a prohibited future…




  • In the end dosage is very relevant and of course even more important: set and setting

    I do think acid is more homogeneous and easier to dose appropriately though (YMMV) But the length of a trip can make it challenging.

    Do heroic doses of either, shrooms for me result in more body load and are more introspective chaotic/mystic. Acid more energetic/clearer/“Neon” wider headspace. But in the end setting is what I think is most important for how the trip plays out (I had my best and worst trip on shrooms).










  • reasonably well

    hmm not in my experience, if you don’t care about code-quality you can quickly prototype slop, and see if it generally works, but maintainable code? I always fall back to manual coding, and often my code is like 30% of the length of what AI generates, more readable, efficient etc.

    If you constrain it a lot, it might work reasonably, but then I often think, that instead of writing a multi-paragraph prompt, just writing the code might’ve been more effective (long-term that is).

    plan it correctly and the actual implementation of the correct plan will take no time at all.

    That’s why I don’t think AI really helps that much, because you still have to think and understand (at least if you value your product/code), and that’s what takes the most time, not typing etc.

    it‘s just different.

    Yeah it makes you dumber, because you’re tempted to not think into the problem, and reviewing code is less effective in understanding what is going on within code (IME, although I think especially nowadays it’s a valuable skill to be able to review quickly and effectively).








  • Welcome to Rust which “solves” this issue…

    Yeah it takes more time than a quick and dirty python script. But when I’m counting the countless hours (what irony) into this equation because of mindless leaky abstractions and resulting debugging, I’m certain that I’m at least not a lot slower writing that. As I said I’m not talking about the last 10-20% of performance that’s possible say even up to 40%, but more like an order of magnitude (at least), i.e. algorithmically insufficient or relying too much on that your abstractions do everything right and you use it correctly (which in the case of react is seemingly not the case, when looking at the modern web).

    Taking that example (Rust) again, I very often get away with .clone() everywhere, i.e. not even caring much about performance while the performance is not significantly impacted. Then I switch to our typescript code-base in my job and get aggressions because of this extreme slowness (because of stupid abstractceptions, like wtf? shadcn needs to be built on radix-ui needs to be built on react etc. which in effect results in a slow abstraction-hell… and leaky abstractions everywhere)