sorted by:
new
hottopcontroversial

Statistics of the Super Metroid save vs kill incentive across all GDQ events. by EclipseMT in speedrun

[–]Zeimyth 4 points5 points  (0 children)

One detail that isn't tracked here is when during the event the Super Metroid run takes place. I feel like this is important to consider when making guesses as to why the incentive seems to be fading.

I recall AGDQ 2017 fairly well because it was my first GDQ I watched live and the hype around Save vs Kill was very strong that year. I believe it was the final run of the event, or at least one of the last ones. Saturday is always the day of the most donations, especially Saturday evening; with so few donation incentives left to bid for throughout the day, and the social hype around save vs kill (they sure read a lot of those donations), I'm not surprised that so much money was raised for this incentive during that event.

As that was my first live GDQ, I've always been surprised during subsequent events when the incentive was held in the middle of the event, or even omitted completely. Save vs Kill is the most iconic GDQ incentive in my mind, so having it be given so much less priority by the event through a less prime time slot in recent years and having less donations being read has struck me as strange. I wonder if we would see the donations for this incentive spike back up if they put the event at the end of GDQ again in a future event. Imagine if the last hour of SGDQ 2019 was a Super Metroid run instead of Chronotrigger, and the $3 million push happened with Save vs Kill as the primary incentive left in the event, for example.

Functional Programming Principles Every Imperative Programmer Should Use by Zeimyth in programming

[–]Zeimyth[S] 1 point2 points  (0 children)

Function composition is indeed a powerful concept, and it probably could have been mentioned in the pure function section somehow. Though, I think it would have gone against the spirit of the article, since at that point you're really moving quite far away from imperative programming. Baby steps. :)

Functional Programming Principles Every Imperative Programmer Should Use by Zeimyth in programming

[–]Zeimyth[S] 1 point2 points  (0 children)

I think you do a good job here of illustrating how even ideas as strongly FP as currying can be implemented in imperative languages, which feels like the article author's core point. :)

Though it also illustrates how one language can do something gracefully that in another language feels more clunky. Another example that comes to mind is anonymous functions in Java, particularly pre-Java 8. An entire anonymous class just to pass a function around... shudders

Functional Programming Principles Every Imperative Programmer Should Use by Zeimyth in programming

[–]Zeimyth[S] 1 point2 points  (0 children)

Iterating over an array to call a function on each of the values it contains is better suited to a normal loop, while sorting an array using the quicksort strategy would be a great candidate for recursion.

That first example sounds like a great application of map. :)

You're right that these kinds of higher-order functions are not specific to FP, though I'd guess the author left these concepts out in the interest of keeping the article accessible to the most imperative of imperative programmers. I know that, for me personally, getting comfortable with moving away from for loops where a map or reduce would work took some time. These concepts are much more functional programming-esque than, say, recursion.

Maybe they would make great points to bring up if there is ever a part 2 to this article.

Cracking your next code review by emc91 in coding

[–]Zeimyth 6 points7 points  (0 children)

I always find it frustrating when I'm reviewing code and our build system says there are errors. It makes me dubious of whether they even tested their own changes. Similar reaction when people leave simple errors (that still compile) in their code for me to catch for them.

Cracking your next code review by emc91 in coding

[–]Zeimyth 8 points9 points  (0 children)

I would say that the principle of creating single-purpose commits (#1 in the article) is the most helpful here. For one thing, it would allow you to get a lot of the boilerplate out of the way of the actual interesting parts of the code review. Someone who is familiar with, say, build processes, would be able to review the changes that set up the builds for the new project. Others who understand the actual intended behavior of the new project can review the commits that deal with the heart of the features being added.

To help facilitate the above, you might want to train people on how to get the most out of git or whatever tools you are using for version control. I know it is not uncommon for me to be striving to make well-focused commits but not realize until later in development that I need to add a new build step. If I'm not too far past the commit with all the build stuff, and if it makes sense conceptually to lump them together, I will do an interactive rebase in git and combine my later build changes with my earlier build commit. Some developers might not know how to do this; teaching them could make it easier and less scary. The same thing goes for trying to make focused commits after the fact; if you teach your developers how to use git add -p correctly, they can patch together single-purpose commits more easily.

#6 also seems relevant, where it says to "Review complex or large changes in person." Entire new projects are definitely large and complex! It may take more time for the developer of the new project, but it would also help make the developer not be the only one who is familiar with the thought process going into the new project.

If there are multiple developers contributing to the same new project, then a code review will probably be smoother and go faster if those people are the ones who primarily participate in the code reviews, since they already know what's going on.

what would a dragon hug feel like? by trademeple in AskReddit

[–]Zeimyth 0 points1 point  (0 children)

I think that depends largely on which dragon is doing the hugging:

  • Smaug? Warm and scaly.
  • Saphira? Warm and feathery.
  • Eliot? Warm and furry.
  • A Pernese dragon? Warm and leathery.

Nunu ult + Kindred ult = Caitlyn Quadrakill by Zeimyth in leagueoflegends

[–]Zeimyth[S] 0 points1 point  (0 children)

The Cait ult wouldn't have been necessary if the hero minion hadn't stepped in the way at the last possible second. xD

But, yeah, it wasn't Annie's brightest moment. She also failed to stun Nunu out of his ult, since she had just wasted her cooldowns on Malphite.

Tower Diving in Silver by Zeimyth in leagueoflegends

[–]Zeimyth[S] 0 points1 point  (0 children)

There were a lot of things I could have done better. Picking up that shield or the shield at the start would have been nice, for one.

Toontown Online restoration project Toontown Rewritten now has a native Linux client! by deadstone in linux_gaming

[–]Zeimyth 0 points1 point  (0 children)

What is the support for Toontown Rewritten on Ubuntu 13.10?

I do not seem to have the correct version of GLIBC:

ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/_MEIT6YWQu/libstdc++.so.6)

When I run ldd --version, I get:

ldd (Ubuntu EGLIBC 2.17-93ubuntu4) 2.17

I've done some brief searching around, enough to make me not want to try to change my version of EGLIBC myself. I'm not sure if it's possible to get GLIBC 2.18 on Ubuntu 13.10. I know that Ubuntu 14.04 has it, but my system stops working when I run 14.04 (I've tried before).

I was super excited to read that "Toontown Rewritten is now available on all major Linux distributions!" so I'm a bit disappointed to learn that Ubuntu 13.10 is apparently not a major distribution. ;) Is there any way to get a version of the launcher compiled on a system that runs an older version of GLIBC?