I'm engaging in the kind of procrastination today where there's this important thing I should be doing, but instead I'm doing a bunch of smaller, slightly less important tasks instead.
Today on Dwarf Fortress: The Sinister Start in the Plane of Myth, we hit magma! We're producing green glass and are working towards kicking off our steel industry. Just in time, too, because we're now a County and the Count wants fancy rooms! I hope he likes steel walls.
We're upgrading our fortress defenses and will be building an above-ground fort pretty soon, provided the smelly goo doesn't drive everyone mad!
So, I don't know if this works for everyone, but this might be useful if you have noticed (like myself) how time passes faster and faster the older you get, as if fate wasn't cruel enough.
One simple trick: think in terms of what calendar year things happened rather than how old you were.
It's not perfect but it's better to have that "2020 seemed so long ago" feeling than it is to have that "WTF happened to my forties!?" dread.
@zalasur
In the old days, I would walk to a colleague's office to ask for help, formulating the question on the way. On reaching their office, they would look up and I'd say, "Never mind. I've got it now."
Today on Dwarf Fortress: the Sinister Start in the Plane of Myth: we found magma! And also we have a Hillocks? Our Baron is nice and settled in and I'm making room for the eventual monarch and the unceasing waves of migrants. Lots going on in this world of smelly goo!
We're kind of ignoring petitions for now so no guild halls or specialized temples until we get our furnaces up and running.
The announcement that NetBSD is banning AI generated code is a noble gesture and all, but the main problem, as always, is detection. If everyone is acting in good faith, then all is well. But if someone generated code using Copilot then it may not be easily distinguishable from hand-written code. It's not like code has a watermark or anything like that. It's text.
I fear that this might end up with people getting falsely accused of submitting AI code. How does one prove their innocence?
It's fun when you edit code that's been written by someone with the job title "Software Architect" and there are so many mistakes in it that it takes you two days to clean it up. 😅
Hmmm, I keep getting deeper and deeper into this rabbit hole and I keep running into more problems. I may have to write all this code from scratch, it at least the part of it I need.
This is the danger of copying code verbatim from other projects. Errors are cumulative.
I managed to get the code to compile, but it doesn't run, and I suspect it's incompatible with the architecture it was supposed to run under in the first place.
I think cutting my losses at this point and starting over is the best plan.
I'll get an older version that I wrote myself to work. I really wanted to avoid that since the whole idea is to replace my old boilerplate code, but at this point time is more important than correctness. I need to get this working to get the project done soon.
Today on Dwarf Fortress: The Sinister Start in the Plan of Myth, we captured our first goblin invasion force of child snatchers. We'll be sure to melt their armor before tossing them into the magma pits. But fist, we need to build the magma pits.
A Dwarven caravan is on its way and the migrants are arriving en mass. We need to get our magma industry going soon and let the steel flow!
In case you're wondering, the part I'm complaining about is the useless comment above the line of code that is a literal restatement of what the code does without contributing to clarity or understanding for anyone reading said code.
Today, in our sinister start of Dwarf Fortress, the search for more iron ore continues. We found it, but it's locked away in a light aquifer! But no worries, we just need to provide some adequate drainage and we should be fine. What's the worst that could happen?