In the moment, writing a blog is a nice way to indicate to myself that something is done. But the process of writing the blog forces me to find some lessons and takeaways, and that makes my next project better.
3,173 karma · joined December 24, 2011
I'm based in Brooklyn. You can reach me at eieiogames at gmail dot com
alum Jane Street Capital, Recurse Center (F23, W25)
In the moment, writing a blog is a nice way to indicate to myself that something is done. But the process of writing the blog forces me to find some lessons and takeaways, and that makes my next project better.
[1] https://imgur.com/a/how-to-use-print-runs-to-gain-advantage-...
My memory is fuzzy, but it was something like "Kai looked at a few of the boosters in a practice draft, and then was able to tell us (something) about the cards that should be in the remaining packs just by reasoning about print sheets."
I'm sure I'm getting the details wrong here - I'm not positive that it was Kai, and I don't have a good enough mental model of print sheets to know what was possible back then. And I think these skills aren't relevant today (?)
But I thought it was a fascinating detail. It's always fun to hear about the wrinkles that serious players of a game pick up on in order to find an edge.
(I've searched for the story a few times and haven't been able to find it; I just don't remember enough about it now)
edit: some discussion below, but I think the story here is approximately "Kai memorized all possible print runs, which was feasible to do back then, and was therefore able to back out which cards had probably been drafted and who was probably holding them" or something like that. Nothing about reasoning about runs across boosters!
Seems like there is probably some set of clever hacks here that could get you around this (although I don't know enough about radio to propose any); I think I asked about pre-computing some state for each song on its own and he had a good response to why that either didn't work or didn't help much, but unfortunately I don't remember it!
[1] we are both currently at the Recurse Center / https://recurse.com
My experience is that chucking the Steamdeck in my backpack for a flight is doable if I don't put it in the case, but if I put it in the case it takes up enough space that it's annoying to fit my laptop / other stuff too.
I normally deal with this by either not using the case or just taking my switch instead. But I respect the author's choice here a whole lot :)
From your website it looks like we're in the same city; feel free to shoot me an email (mine is in my profile) if you'd like to grab coffee sometime :)
It's fun to compare it to "A blog post with every HTML element" [1][2], which gets at a (very!) similar thing but in a very different way. This post primary shows, and is a little more chaotic (meant positively!) whereas the other post is much more prose and explanation heavy (also good, but very different).
[1] https://www.patrickweaver.net/blog/a-blog-post-with-every-ht...
[2] HN discussion: https://news.ycombinator.com/item?id=37104742
Jeff's blog mentions Imran. Jeff's blog is still up, but Imran's isn't! However it is up on the internet archive, and Imran's post is also from 2007[2].
My sense is that Imran wrote a blog in January 2007 mentioning FizzBuzz and that Jeff's post in February 2007 is what made FizzBuzz the meme that it is today. This is probably very obvious to some readers of HN, but Jeff's blog (Coding Horror) has been around for a very long time and was one of the 'big' tech blogs back in that era of blogging (Jeff went on to, among other things, cofound Stack Overflow with Joel Spolsky a year after writing about FizzBuzz).
Thanks for asking this - if someone asked me yesterday "who invented FizzBuzz?" I would have pretty confidently said "Jeff Atwood!" and I would have been totally wrong.
For completenesses sake, the other really influential interview question blog I remember from this era is Steve Yegge's "five essential phone screen questions," which is even earlier (2005!)[3]
I think interviewing discourse on message boards is tricky; folks have strong opinions, and if someone says "this is an essential question" and the question is hard for you, it's hard not to take that personally. In a past life I thought a lot about interviewing (here is a resource on interviewing I helped create for Jane Street back when I worked there[4]). I have never asked a FizzBuzz-style question, but I do think that "explicitly telling the candidate what you want and give them lots of help to get there" is really important.
[1] https://blog.codinghorror.com/why-cant-programmers-program/
[2] https://web.archive.org/web/20080405225407/http://imranontec...
[3] https://sites.google.com/site/steveyegge2/five-essential-pho...
FWIW the place my brain went was some kind of magic trick, since having control of this could function kind of like a forcing a specific card or something
Anyway steal away!!
but agree that it can be really hard to take a step back and realize that you can employ it instead of writing something "perfect"
back when I was vim golfing the normal solution was to make the macro recursive. So you'd record your macro, and you'd end it with '+@q' (move to next line and run the macro again). Then you run the macro once and it runs over every line.
This ends up being really efficient in terms of keystrokes but in practice I think it's hard to think about and not very ergonomic, so I don't end up using it much. But it's a fun trick for golfing.
I have uploaded several games to itch (although it's been a while) and a cool thing I found was that even with no followers back when I started making things, a decent number of people played some of my games! Nothing crazy, but I remember being delighted that the second game i ever made[1] got a few thousand plays and some actual comments.
My experience is that:
* tags matter! For example, a decent number of people seem to be looking for new incremental games and are willing to try new stuff in that category
* your primary image, title, and description matter a lot and it's worth spending some time taking a good screenshot (I'm really bad at this)
* you can upload a gif instead of just a screenshot to include a little gameplay in your title image and that might help
* participating in gamejams can help a lot because you get some guaranteed players (everyone plays each others games and rates them; maybe you get some feedback too)
I'm not sure where you are in your gamedev journey (there's a good chance you're way ahead of me and this advice is useless!) but "just make some stuff and put it on there and see who bites" was effective and motivating for me early onLike jchw said, this was a single-day project (although I did the writeup for it the next day).
I went from 0-prototype in one sitting; I think that was around four or five hours of work? Then I went home, had dinner, and spent maybe three hours optimizing and cleaning it up.
edit: I should say, i have done a lot of dumb things like this and I'm pretty sure it would have been at least a week of work for me 2 years ago. "making the computer do dumb stuff" is a skill like any other!
I suppose I shouldn't be surprised that German has a great word for this, although I admit when I started reading your comment I expected it to be a compound word.
I quite like the literal translation too!
When I see something like this it makes me think about how a spreadsheet structure is "obvious" - but I mean it positively! It's a beautiful, intuitive, almost inevitable way to lay out data, and I'm delighted that folks came up with something like this so long ago.
I feel this way about a lot of my favorite posts on HN, whether they're a bit of history, a totally new invention, or something different entirely. And I certainly feel it here.
(We of course, both know why! And if you haven't seen the names before but you're a programmer, youprobably still make some assumptions about edge cases, precision, etc. But I'm assuming that is not the experience of the typical Google Calendar user?)
In the states, I think most people I know are familiar with "eastern time" or "pacific time." But I doubt that many of my friends recognize "Americas/New_York" or appreciate why they need to select that instead of "Americas/Indianapolis" when referencing eastern time[1]. I certainly wasn't familiar with referencing timezones this way until I had a job that cared a whole lot about timezones and had offices in several countries!
I like the idea of solving this by just asking for the location of an event.
[1] having lived in indiana a while ago, I'm assuming that Indianapolis gets its own TZ entry because it wasn't on daylight savings back in the 90s (?). Which was pretty annoying.
very fun to have received so many pointers here, hopefully I'll be able to do a follow up blog once I've finally let people find all the good UUIDs
(I'm also super curious how those numbers were chosen and about what would start breaking if the limits weren't there - maybe your example of weirdness around clientHeight etc gets at that)
I think the biggest rabbit hole I went down was trying to use FEAL (which is very breakable) and exploiting the things that make it breakable. But this is very much not my area of expertise - I was learning as I was working - so it's very possible either that that was a dumb idea or that it was a great idea that I didn't figure out.
I also considered things like "focus on add lots of entropy to groups of 200 or so UUIDs, but have obvious patterns beyond that" which I think would be a reasonable strategy; here I just kind of ran out of time (I told myself I'd make this in a week)
Did some light reading about a few other things but nothing substantial
But I'm gonna try to get a few more crypto-knowledgeable friends to chat with me about this and write up what I learn!
And of course, I'm proud to be providing so much utility here - finally we can find and use UUIDs tailor-fit to our needs