require('dep1'), require('dep2')); } else if (typeof define === 'function' && define.amd) { // AMD-style define define(['exports', 'dep1', 'dep2'], factory); } else { // Fuck-it style "let's pollute the global scope" // if you haven't included 'dep1.js' and 'dep2.js' before, this will break. var exports = {}; factory

time, and even includes tools like bash, some Unix utils (even vim!), but let me state that once and for all: mingw on Windows is slow as fuck. A much better solution, in fact, is to use mingw on Linux (or others) to produce Windows executables. Apparently, mingw-w64 is a more up-to-date version (fork?) that also supports building 64-bit Windows

since the early versions of rock since we have a few rubyists in our ranks, but only recently Alexandros Naskos took matters into his own hands and just implemented the fuck out of it. rock now offers a syntax similar to ruby for string interpolation. Whereas previously one would have written something like: "Player is at %s, has %.2f health and %d

but the correct error now appears: source/johnq/mob.ooc:100:29 error Undefined type 'Shot' (Hint: there's such a type in johnq/shot) takeDamage: func (shot: Shot) { Which makes a lot more sense. A match made in hell On the way to getting the correct error message, something else went wrong. Something I didn’t expect at all. Match came to fuck

round| round.expect("REASON").our_score()) | +++++++++++++++++ For more information about this error, try `rustc --explain E0599`. error: could not compile `day2` due to previous error Oh, that’s right! Parsing a &str into a Round is fallible. Well, the compiler gives a suggestion (and holy fuck I didn’t see that

memory addresses to be written all at once. Ah for fuck’s sake. This is combinatorics all over again. Ah, I’m sure we can solve that fairly easily. Okay, so we don’t actually need to change our parser at all, because the “floating” bits are simply the bits that are neither in set nor in clear. Let’s set Part 2’s example as our input

can fuck you up. For that reason, it is a good idea to write down exactly what went right, what went wrong, and how you can do better next time. I’ll try not to forget anything, and settle in, this could be a long one. Also, I’ll try to dabble on the technical side of things, just so I can show you guys some code, because I just set up my blog

I resent it for trying to make me do maths. Can we bigints? $ cargo add num-bigint (cut) My guess is that it’ll just get slower and slower and they picked 10K rounds specifically to fuck with me (and anyone who’s using Python/Ruby/etc. for this) So, I’m gonna do that in a branch and roll everything back when it inevitably doesn’t work

ended up seeking help, got on anti-depressants (Escitalopram 10mg, for the data-oriented), and after a rocky start, things got significantly easier. In a “fuck, how many years have I wasted” kinda way. I thought I was broken! I could’ve been happy, emotionally stable, full of energy and productive all this time? Grief set in: it took some

from a year full of harsh lessons. That part is on us, really. In an age where nothing really seems certain, where everything could change at a moment’s notice, it’s comforting to consider that some things do end, eventually, even if it’s just a rotation around the sun. Good fucking riddance, 2020. I won’t really miss you. I’d like to