space-nerds-in-space

I recently was sent patches for my open source space game[1] that added cascaded shadow mapping[1] and gravitational lensing[3] for black holes, both things that I've wanted for years, but found too difficult to tackle. The patches were made with Claude Opus doing pretty much all the work, guided by a human. The quality of the patches was, in my estimation, pretty damn good. It didn't do weird things, it used the infrastructure already present, it looked like what I wish I could have written. It was clearly not plagiarized in bulk, in as much as it was so well integrated with my existing code, though I imagine all CSM code/shaders and gravitational lensing shaders tend to look pretty similar, or at least do similar things. It was eye-opening to find out that Claude was capable of doing such a thing. Neither of these changes affect th

> I've got an internal alarm that starts to go off somewhere around 72 hours. Nah, in my experience, if you've got good commit hygiene you can often merge even ancient commits. Here's a pretty hefty commit I merged five years after it was originally written, converting a ~100k line codebase from GTK to SDL2, written in 2015, committed in 2020, with tons of development in between, with "10 files changed, 777 insertions(+), 804 deletions(-)" https://github.com/smcameron/space-nerds-in-space/commit/4ab... I was expecting it to be a bit of a nightmare, but it really wasn't bad at all.

I don't know if this counts, but I wrote a parser for "the ship's computer" in my game, "Space Nerds in Space". It's described here: https://scaryreasoner.wordpress.com/2016/05/14/speech-recogn... (and that reminds me, there's Google's Parsey McParseface: https://blog.research.google/2016/05/announcing-syntaxnet-wo... though I'm not sure how practical it would be to use that in an interactive fiction context.) I also wrote some toy "interactive fiction" things (with less sophisticated parsers) in python and Lua as a way to gain familiarity with those languages, not that they are very interesting in and of themselves, though they demonstrate a fairly standard technique behind these kinds of games in a compact way. https://github.com/smcameron/smcamerons-python-adventure https://github.com/smcameron/space-nerds-in-space/blob/maste...

1. https://github.com/smcameron/space-nerds-in-space Space Nerds in Space, a multiplayer starship bridge simulator for linux 2. Gneutronica, a MIDI drum machine program https://github.com/smcameron/gneutronica 3. gaseous-giganticus a program to generate textures for gas giant planets https://github.com/smcameron/gaseous-giganticus 4. explodomatica, a program to generate "explosion noises" by filtering white noise https://github.com/smcameron/explodomatica 5. note-driller a simple program to drill guitar fretboard notes and chord shapes https://github.com/smcameron/note-driller 6. wordwarvi a side-scrolling shoot-em-up similar to Defender, Stargate, and Scramble https://github.com/smcameron/wordwarvi 7. cosmic-space-boxinator a program (in the Processing language) to create sky-boxes for my space game, Space nerds in space https://github.c

Well, you can replace setlocale() with your own setlocale that uses dlsym() to look up the "real" set locale, and your setlocale can just call the real setlocale with params (LC_ALL, "C"). That turns it off pretty well. Even if other libs call setlocale (looking at you, gtk), they'll get your version. like so: https://github.com/smcameron/space-nerds-in-space/blob/maste...

Also, there's already debian packaging stuff: https://github.com/smcameron/space-nerds-in-space/tree/maste... But I'm not really too interested in distributing packages that will just get out of date. "git pull; make" is easier anyway.

Pocketsphinx. Here is a demo https://www.youtube.com/watch?v=tfcme7maygw and a blog post about how to do it: https://scaryreasoner.wordpress.com/2016/05/14/speech-recogn... Code is in here (gpl2) https://github.com/smcameron/space-nerds-in-space In particular, look at snis_nl.h, snis_nl.c The trick with pocketsphinx is to limit the vocabulary you want to recognize, and create a corpus of the types of things you want to be able to recognize and feed it through here: http://www.speech.cs.cmu.edu/tools/lmtool-new.html If you try to use pocketsphinx to recognize arbitrary English (e.g. dictation) it's not going to work very well in my experience.