Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)QU
quilan @lemmy.world
Posts 0
Comments 113
Dawn - The Knell And The World [Melodic Black Metal | Sweden | 1998]
  • I remember first listening to this album back in ~99, and man I couldn't even process its greatness. Love it. I remember reading, seemingly a million years years ago, that a follow up album was still in the works, but it's been 26 years now... I'll huff some more copium I guess.

  • Yoshi P apologizes for Final Fantasy 14 Dawntrail issues. The expansion is currently in early access.
  • Aye. Granted, I'm on Dynamis so my experience is going to be wildly different from, eg. Aether, but I've only had one occasion of long queues, and that was when Aether died. And even then, it was steady progress, unlike the Login Roulette of Endwalker.

  • What demos did you play today? | DAY 3
  • I've been playing Heart of the Machine, and really enjoying it. It's a fascinating 4x ish in a future city, in a bit of an inversion of AI Wars (same developer). Before playing, I was merely intrigued, but now I'm excitedly awaiting where it goes. It was, however, initially difficult to figure out what to do. Perhaps more UX is going to be useful here.

  • Meet the woman who cannot forget
  • I'm pretty sure this is what Tim Rogers from Action Button Reviews has. His masterpiece Boku no Natsuyasumi review goes into a lot of detail about it. The end of part 5 had me literally sobbing in my chair for the first time in perhaps 20-some-odd years, followed immediately by a very confused laughing at a surprise hbomberguy appearance. I'd highly recommend watching it - it's quite the long form journey.

  • Should i continue programming?
  • As someone with decades in the industry, the amount of awful code out there is staggering. The code that I write is also often awful - at least the first time I'm exploring a new complex problem. Once you've done something once though, your second or third time writing it is typically a lot better.

    Typically my first pass ends up being a "get it done" pass. Explore the space with as best effort as you can to get something that works. Then identify what issues or problems you had with the process.

    Refactor your code, back up frequently! Prefer to keep things to generally one abstraction per function. This allows you to quickly look at a something and identify what it's doing, and to (with experience) sus out any potential bug areas. Make your code consistent in naming & code flow if you can. Test your code frequently.

    It's like playing a factory-genre game; your first pass is likely going to be some spaghetti monstrosity that quickly runs into scalability problems because you didn't know what you'd need ahead of time. With the knowledge of what pain points you had, you make a new base, maybe incorporate a bus setup and your scalability now goes much higher before it reaches problems. On your nth pass, your base is now a train based system that runs like clockwork and can do things you never thought possible before.

    Tl;dr: Everyone's first approach often sucks and eventually runs into problems. Understand what didn't work and learn from your mistakes. Do it again with these lessons in mind when you feel inclined (if you're experiencing scalability problems). Look at other code & learn from others. Keep writing as much as you can - programming is difficult and hard learned experience is often the best teacher.