• 1 Post
  • 565 Comments
Joined 2 years ago
cake
Cake day: January 3rd, 2024

help-circle




  • Oh, nice.

    I’m always looking for another ChangeLog tool.

    That said, I never leave my ChamgeLogs up to automation.

    My git logs are open to my users for full details, but my ChangeLogs are how I communicate which changes my users probably need to be aware of.

    So far, this hasn’t yielded well to automation. But my team is still considering standardizing our commit log messages enough to allow it someday.




  • I played E.T. relatively recently to remind myself what the fuss was about.

    The game plays fine (with average Atari bugginess).

    It just stands out as an early huge miss for a movie tie in. Almost nothing about the game feels like the movie, or is particularly anything a fan of the movie would seem likely to enjoy.

    I say “almost” because the exploring kind of fits. The same exploring that is constantly frustratingly interrupted by pit falls.

    It’s really not that bad of a game, though.


  • I’d argue Superman 64 for the N64 is a worse game by all measures.

    I’ve spent some unfortunate time with both, and can confirm. Superman 64 is worse by a pretty large margin.

    E.T. is genuinely playable, after a needlessly awful learning curve. Superman 64 still continues to suck even for (shudder) players who have put in the necessary time to learn to play it.

    Edit: As others have said before: E.T. is a decent game, it’s just a lousy choice for an E.T. tie-in.

    Fans of a beloved highly polished film masterpiece about gentle communication and wide eyed exploration discovered the Atari game was a nearly unfinished punishing high stress race against a merciless clock - which frequently abruptly ended any aspiration a player had of discovering anything beyond the same pit they fell into many times before.


  • I’m mainly interested in making code reviews a little easier to manage.

    One thing I haven’t seen mentioned yet, here: All future diffs become much easier to read if the team agrees to use a very strict lint tool.

    I know, I know. “Code changes should be small.” I’ve already voiced that to my team, yet here we are.

    I understand from another Lemmy thread that the tradition is to toss the offending team members’ laptop into the nearest large body of water.




  • Okay, this is fun, but it’s time for an old programmer to yell at the cloud, a little bit:

    The cost per AI request is not trending toward zero.

    Current ludicrous costs are subsidized by money from gullible investors.

    The cost model whole house of cards desperately depends on the poorly supported belief that the costs will rocket downward due to some future incredible discovery very very soon.

    We’re watching an edurance test between irrational investors and the stubborn boring nearly completely spent tail end of Moore’s law.

    My money is in a mattress waiting to buy a ten pack of discount GPU chips.

    Hallucinating a new unpredictable result every time will never make any sense for work that even slightly matters.

    But, this test still super fucking cool. I can think of half a dozen novel valuable ways to apply this for real world use. Of course, the reason I can think of those is because I’m an actual expert in computers.

    Finally - I keep noticing that the biggest AI apologists I meet tend to be people who aren’t experts in computers, and are tired of their “million dollar” secret idea being ignored by actual computer experts.

    I think it is great that the barrier of entry is going down for building each unique million dollar idea.

    For the ideas that turn out to actually be market viable, I look forward to collaborating with some folks in exchange for hard cash, after the AI runs out of lucky guesses.

    If we can’t make an equitable deal, I look forward to spending a few weeks catching up to their AI start-up proof-of-concept, and then spending 5 years courting their customers to my new solution using hard work and hard earned decades of expert knowledge.

    This cool AI stuff does change things, but it changes things far less than the tech bros hope you will believe.





  • Three thoughts for you:

    1. If you’re not confident, and the stakes are high, just use a separate computer, on a different network. I’ve had my ass saved more times by my humility, than by my cleverness.

    2. Podman/Docker/Rancher does provide some security advantage, but these are not security tools. Malicious code has a history of breaking out of containers. Do not run code you expect malice from with only a container as protection. The container layer is not enough.

    3. When I’m nervous that non-root processes on my device might acccess my most valuable secrets, I take a hard look at my secret management: Does each secret serve a limited purpose? Is each secret easy and cheap to replace? Does unlocking each secret require prompting the human user? Are secrets encrypted at rest and in transit? Does unlocking secrets invoke multifactor auth? Etc.