This workbook takes the code review anxiety intervention that we designed and tested in our empirical research (https://osf.io/preprints/psyarxiv/8k5a4) & distills it into a self-paced workbook for you. It's designed for you to read & work through as many times as you wish and provides you with the tools you need to mitigate & manage your anxiety about giving or receiving code reviews.
I'm not sure what I'm going to make with this dungeon yet.
It started as a Random Map Maker for Android, for use with TTRPG, but I think I could turn it into something. Some kind of neo-Roguelike?
Once I've got proof-of-concept for a Map, I'll see what next.
Suggestions welcome.
A clean Git history is the key to successful teamwork and quick bug fixes. Errors can only be successfully tracked down if it is always possible to trace when and where code was changed by whom and for what reason.
🥴 However, in the rush of the battle, the changes that are packaged in a commit are sometimes not taken very seriously. Who has never experienced this? A change that is actually unrelated to the current work package has made it into the commit because the file has already been saved temporarily.
💡The solution: With an "interactive add" (git add -i), you can pack partial changes ("hunks") into a commit and specify line by line what should be included in the next commit.
I just read this article on HTMX being a big deal for WordPress and I just don't see it. To vastly simplify the article, give the code below and using the HTMX JavaScript library:
I've managed to convert my Dungeon Generator over to Godot.
Took me literally all day to get the Corridors code working, and it still needs a lot of tweaking.
And this is just a Map. So much more to turn it into anything useful.
Rooms generated as random, non-overlapping, rectangles, then centres joined in turn.
I believe anyone who posts complex and complicated solutions for people who ask for help on logging to a console are sociopaths and most likely evil. #programming#code#stackoverflow#rant
Modern current code should run asynchronously if possible and useful. Slowly but steadily, it is being implemented in almost all popular programming languages, including WebDev.