Sandman

Some GMs love to play against the players, instead of recognizing he’s there to support them.

Start a cocaine or ketamine habit and you will always remember to have it on hand.

You can always encounter a traveling salesman. He will buy your stuff for cheap and sell you useful overpriced trinkets and exotic snacks.

Take a strong dose of magic mushrooms and ketamine to get that experience.

Never use numbers when calculating dates. Use the data formats and constants the calendar library provides.

It’s correctly used in the text.

Number of steps < 500 is equivalent to 500 > number of steps.

When learning a new human language, it’s good practice to also learn sentences and practice speaking and writing, not just rote vocabulary memorization.

When learning a new human language, it’s good practice to also learn sentences and practice speaking and writing, not just rote vocabulary memorization.

The waste and corruption in private industry is mind bogglingly huge compared to the public sector.

ADB was superior.

Today I learned my collection of boxes are doom boxes.

Raw egg right into my mouth.

Start with designing a physical card or board game. Play test it until it’s fun.

For artwork practice drawing on paper.

For writing write stories and dialogue.

Make or choose some music.

Use the above to make a video.

No programming required.

Java has been running serious server software since the mid 1990s. Think WebObjects running on Solaris. Lots of business stuff with big databases still run infrastructure like that.

Java still has the big advantage of being machine agnostic. No need to recompile for ARM or Intel.

Early Swift was very slow to compile and start. The debugger was nonfunctional.

Otherwise it was pretty usable. Especially since it got to leverage the huge libraries written for Objective-C.

Which meant it lacked some basic collection types. A Swift native Set was introduced with Swift 3 IIRC. Before that you had to bridge back and forth between Swift and Objective-C. Sometimes leading to unexpected behavior at runtime.

In Objective-C if an object reference was nil, you could send it messages (call methods) without a problem. Swift however did away with this. Optionals had to be explicitly unwrapped. So if the annotations weren’t correct, Swift code would crash at runtime where Objective-C would have been fine. Lots of bugs related to that existed.

Swift peaked around version 4. Since then, they have been adding kitchen sink features and lots of complexity to feel smart.

I still would have preferred an Objective-C 3.0. Chris Lattner was a C++ guy and never really understood Objective-C culture and strengths.

Toxic place that suppresses all dissent and thus is unable to change, adapt, or even recognize problems.

Emotional dysregulation and maladaptive coping mechanisms.

You can generate the code with a simple macro.

Always put a ticket number in the commit message. That can make it much easier later to find out what the context was for some weird solution.