[–] 2 points 9 months ago* (last edited 9 months ago) (1 child)

No, it's not on the user's end. It's because you didn't use correct Markdown syntax for your link. I verified this in your post source before commenting.

You used: [https://joinhideout.vercel.app/]() - which is a link without a target, so it defaults to this page we're on.

You should have used one of

  • <https://joinhideout.vercel.app/>
  • [https://joinhideout.vercel.app/](https://joinhideout.vercel.app/)
  • [joinhideout.vercel.app](https://joinhideout.vercel.app/)
  • source
  • parent
  • context
  • [–] 13 points 9 months ago*

    Great analysis / report. At times a bit repetitive, but that could be useful for people skimming or jumping or quoting as well.


    Despite 91% of CTOs citing technical debt as their biggest challenge, it doesn’t make the top five priorities in any major CIO survey from 2022–2024.

    Sad. Tragic.


    I'm lucky to be in a good, small company with a good, reasonable customer, where I naturally had and grew into having the freedom and autonomy to decide on things. The customer sets priorities, but I set mine as well, and tackle what's appropriate or reasonable/acceptable. Both the customer and I have the same goals after all, and we both know it and collaborate.

    Of course, that doesn't help me as a user when I use other software.


    Reading made me think of the recent EU digital regulations. Requiring due diligence, security practices, and transparency. It's certainly a necessary and good step in the right direction to break away from the endless chase away from quality, diligence, and intransparency.

  • source
  • [–] 5 points 9 months ago*

    That's wonderful to read, that it caught and motivated you.

    I suspect these systematic issues are much worse in bigger organizations. Smaller ones can be victims, try to pump out, or not care about quality too, but on smaller teams and hierarchies, you have much more impact. I suspect the chances of finding a good environment are higher in smaller companies. It worked for me, at least. Maybe I was just super lucky.

  • source
  • parent
  • context
  • [–] 1 point 9 months ago

    It's crazy how border control and sanctions are normalized political topics, yet I've never heard suggestions of applying that to the internet.

    Suppressive regimes often control their network and network borders. Everyone outside not doing so is quite asymmetric.

  • source
  • [–] 4 points 9 months ago*

    A library with no code, no support, no implementation, no guarantees, no bugs are "fixable" without unknown side effects, no fix is deterministic even for your own target language, …

    A spec may be language agnostic, but the language model depends on trained on implementations. So, do you end up with standard library implementations being duplicated, just possibly outdated with open bugs and holes and gaps and old constructs? And quality and coverage of spec implementation will vary a lot depending on your target language? And if there's not enough conforming training it may not even follow the spec correctly? And then you change the spec for one niche language?

    If it's a spect or LLM template, then that's what it is. Don't call it library. In the project readme don't delay until the last third to actually say what it is or does.

  • source
  • view more: ‹ prev next ›