• 0 Posts
  • 12 Comments
Joined 5 months ago
cake
Cake day: May 22nd, 2026

help-circle






  • I use Signoz and OTel collectors to bring in everything from Kubernetes (and also SNMP-to-OTel for the network and NAS stats.)

    That covers dashboards and basic alerting. Then on top of that I have an n8n workflow that runs every morning - it pulls all the main stats out of Signoz, as well as issues and their status from my infrastructure repo in Gitlab, and feeds it all into a local LLM (Qwen-3.8-Flash-Next at the moment), which emails me a report on overall cluster health. It also automatically opens a ticket in Gitlab for anything that might need fixing.

    It works really nicely, gotta say.


  • I just finished Pragmata (had to speedrun the last few levels to fit in Control: Resonant, which I feel bad about - but I’d had C:R preordeted for ages and love anything from Remedy… Anyway, I digress.)

    Pragmata I thought was good, and Capcom deserve some credit. An actual new IP, a genuinely fun and different game mechanic, visually looks good - and is bright and striking rather than regulation brown - and was just good fun to play. My only criticism would be that the dialogue/plotting felt like it was kinda rushed - like they skipped a couple of chapters and you go from “just met” to “devoted partners” in one scene and missed the plot/character development needed to get from A to B. I feel bad saying it though, because it’s a decent and topical plot and has some genuinely affecting moments.

    Credit where due; I hope it does OK because God knows it’s hard enough to find games doing anything new these days.



  • The patent is not on haptic feedback. The patent is on a very specific means of implementing haptic feedback using ferrofluids and electromagnetic actuators that it is claimed (and Apple deemed it good enough to copy, so presumably truly) allows for both a smaller implementation than typical mechanical haptic feedback (i.e. the off-balance-flywheel approach of phones of old), while also allowing for low- or zero- noise compared to “speaker or piezo” based haptic feedback.

    There are a lot of shit patents in the world, but on a surface reading at least this seems sufficiently novel that I don’t see why it should be invalid. One also presumes that if Apple had any grounds to invalidate it on prior-art they would have done so.


  • Writing code was never “the job”, that is just the trivial typing part you do when the thinking and designing ends. The job is solving problems (which I enjoy very much thanks.)

    This is like people who refuse to program in another language because they are “a .NET programmer”. That just tells me you’re a coder not an engineer. In my career I’ve been paid good money to write C51 assembler, C, C++, Tcl, Limbo, Java, C# and Rust (roughly in order) - LLMs are just what’s next.


  • It’s not going away.

    Everyone who complains about the quality of the code it produces is overlooking one important fact: 90% of the code developed by the software engineering profession is utter dogshit, pasted together by people whose understanding just about extends to typing in stackoverflow.com by banging their head against they keyboard.

    LLMs are not replacing artisinal hand-crafted code developed by a skilled engineer from a top-10 university, it’s replacing the utter shite produced by the people with an NVQ from Timbuctoo Community College that actually powers the vast majority of websites and enterprise software.

    And it’s fucking good at it.

    Look, when I started my career I used to hand-write assembly code. I used to personally review the output of the Keil C51 compiler because its optimiser was objectively dogshit. Nobody is doing that any more - partly because the compilers are better than programmers at writing assembler these days, and partly because we have so much CPU and memory we don’t know what to do with, so who cares if they aren’t. Both apply to LLMs, and we will soom be at a stage where reviewing - or even caring - about the quality of LLM produced code is as anachronistic as thinking you need the check the compiler’s output. (TBF, Clang/LLVM for AVR still produces dogshit assembler, but that’s by the by.)

    Just as assembler did before, high-level code is going to become just another intermediate representation that isn’t really important; what will matter are the prompts and context you give to the LLMs. And there’s still a hell of a lot of engineering skills that need to go into that.

    Software Engineers - the real ones - have nothing to fear from LLMs, and in many ways it’s much more satisfying working with an LLM than a team of barely skilled “coders”. The barely skilled coders who wouldn’t know malloc from a semaphore though? They’re fucked.