• 0 Posts
  • 464 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle




  • Maybe Ukraine couldn’t retake the areas occupied by Russia, but they could deliver a Pyrrhic blow to Kremlin.

    They have delivered a pyrrhic victory.
    Russia thought they could take Kyiv (Ukraine?) on 3 days.
    The fact that Ukraine has resisted so hard, have redefined the modern battlefield, have conducted huge deep strikes…
    Ukraine is winning.

    The reason Ukraine may not be “winning” is because the Russian war machine is huge. Like really really big.
    The reason that Ukraine is “winning” is because the Russian war machine is outdated and corrupt.

    The western opinion of Russia has been devastated. Russia tested themselves, and failed.
    Russia is holding on by their nukes.






  • especially once a service does fail or needs any amount of customization.

    A failed service gets killed and restarted. It should then work correctly.
    If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
    So, either build your recovery process to account for this… or fix it so it can recover.
    It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

    As for customisation, if it isn’t exposed via env vars then it can’t be altered.
    If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

    It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
    It’s using a chisel incorrectly.


  • I would always run proxmox to set up docker VMs.

    I found Talos Linux, which is a dedicated distro for kubernetes. Which aligned with my desire to learn k8s.
    It was great. I ran it as bare-metal on a 3 node cluster. I learned a lot, I got my project complete, everything went fine.
    I will use Talos Linux again.
    However next time, I’m running proxmox with 2 VMs per node - 3 talos control VMs and 3 talos worker VMs.
    I imagine running 6 servers with Talos is the way to go. Running them hyperconverged was a massive pain. Separating control plane and data/worker plane (or whatever it is) makes sense - it’s the way k8s is designed.
    It wasn’t the hardware that had issues, but various workloads. And being able to restart or wipe a control node or a worker node would’ve made things so much easier.

    Also, why wouldn’t I run proxmox?
    Overhead is minimal, get nice overview, get a nice UI, and I get snapshots and backups






  • Yeh, but you only need 10 vibe code cleaner-uppers per vibe coder.
    And a vibe coder is a 10x developer.
    You just have to mitigate the increased cost of AI API calls.
    It pretty much balances out, with the obvious 20% efficiency boost - which is where everyone makes their money: companies, developers and shovel AI platforms… All 20% efficiency boost. Which directly relates to profit boosts. 20% line goes up!
    Which also pays for the datacenters, the shovels GPUs, the power, the cooling and the water for the cooling. It’s all cheaper, cause AI is at least 20% more productive.

    Even if your vibe-coder-code-fixers turn into vibe-coder-code-vibe-fixers… That’s just another 20% efficiency boost. Basically printing money! Oh, but you need to buy more shovels GPUs. But that’s also a win because shovels GPUs don’t have unions or require holidays. Think of the profits! They work 24/7.
    And all you need are vibe-coder-code-vibe-fixer-code-fixers.

    …As long as your vibe-coder-code-vibe-fixer-code-fixers don’t turn into vibe-coder-code-vibe-fixer-code-vibe-fixers (I’m so lost, I think that’s right).

    Edit: forgot some shovels


  • I find the best way to learn things I want to learn is with a project.
    Don’t learn game dev to be able to create a game. Learn game dev to craft the story you want to tell.

    If you don’t have a story or project that you are passionate enough to see through to a released game, then maybe try and get involved in someone else’s project.

    Or, put what you’ve learned in your back pocket. Maybe you have done enough on that for now, and it’s time to try some other area of programming or even learn some completely different skills.
    Maybe one day you will have a strike of inspiration for a game and you will already have some basic knowledge and ability to see if it will work.