12,395 karma · joined March 23, 2009
I hang out a lot on Stack Overflow: http://stackoverflow.com/users/28169/unwind, mainly answering questions about C. I love C.
I was just starting to think "doesn't Big Clive visit Edinburgh periodically?" and then OP's suggestion scrolled into view. :)
Sounds like a great video idea for him, really.
Uh, as in "excessive paperwork", like brochures/leaflets [1] about the new products? Not a native speaker, had a parse error I'm just trying to resolve ...
[1]: https://www.reddit.com/r/EnglishLearning/comments/1hlbxv7/co...
Note to others: that tester board looks fairly passive, i.e. I don't see (mention of) a microcontroller to talk to the chip that high-powered cables must have. So I guess it's somewhat limited in the number of things it can check?
I think the home page is LLM-aided, the design looks very familiar and wording like
[...] no software to install, nothing to set up. Plug in an Arduino, flash the firmware [...]
gives me pause. I am an actual embedded software engineer, and I would not classify finding, wiring (with resistors!) and flashing a microcontroller board as "nothing to set up".
I tend to think that the bar for building e.g. a small synth is like those by mitxela [1], with a tiny microcontroller running C on the metal.
Then the author here uses multi-threaded Python to schedule notes and do millisecond-length powering of 30+ solenoids and make thousands of people feel it's a proper instrument?! Wow!
Small boards have less I/O pins than larger boards typically, and small/cheap FPGA chips on small boards are also more limited than larger, more expensive parts.
Edit: precise price.
Edit: syntax.
The patched version might even work on some Swedish-speakers if you nail the pronounciation! :)
Your suggestion sounds a bit like spelling Apple like AIILE and using the circles to form a cool infinity symbol. Or something.
Epic to see that it has "No Man's Land" [0] and really really weird feeling to read the readme. No idea why it's listed as a "17 Bit" title though, perhaps they distributed it at some point but they certainly were not involved in creating it. Source: I wrote it. Fun times.
Edit: formatting.
Since this is one of the bugs, I always recommemd writing
game->boardPieces = swAlloc(sizeof(ThingHandle*) * row * column);
Like this instead: game->boardPieces = swAlloc(sizeof *game->boardPieces * row * column);
It's not 100% better, but it cuts out a few tokens which helps readability and moves the significant asterix further left where I think it's easier to spot.Also there some "C icks" (to me, I'm very picky and used to know the standard awfully well from answering many SO questions) that you might want to look into. The two I remember now are the casting of `void` pointers from allocation functions, and (worse) the assumption that "all bits zero" is how a NULL pointer is represented.
[1]: https://www.penguin.co.uk/books/31374/pinocchio-by-collodi-c...
Found a tiny typo, this sentence from quite early (page 17):
Notice how apparently wasteful this file format is: some of the triplets contain only byte.
I think the word "one" is missing before the final "byte".
There was some kind of editing snafu though, the loop header in the big (first) code block reads:
for (i = 0; i < 10; i++, nuke_count++)
But the references to it in the text, and updated versions in the patches, show it as just for (;;)
That was confusing me a bit.I also have read their backstory/naming thing [1] several times but I still don't quite get it. I first thought they were related to the historical Grog, but that was a misunderstanding. I think.
I'm no native speaker but that is backwards, right? Shouldn't it be overstated if it was a success?