nycki

joined 1 year ago
[–] nycki 2 points 13 hours ago

wait, what? didn't that exist well before the labo tho?

60
gameboy mode (rule) (lemmy.world)
submitted 1 day ago* (last edited 1 day ago) by nycki to c/[email protected]
 

using an android phone running retroarch, an 8bitdo Zero Two wireless controller, and this 3D printable mount https://www.thingiverse.com/thing:5998094 .

works pretty good for gb/gbc titles, and its much smaller than other controller attachments! I've been using it for some gba stuff too, like Game and Watch Gallery 4 or Pokemon: Too Many Types, which don't require the L/R buttons.

if this makes you want to buy a controller, I recommend the 8bitdo Micro, which is the same size but with two extra buttons.

[–] nycki 1 points 6 days ago
[–] nycki 10 points 1 week ago* (last edited 1 week ago) (1 children)

I didn't see what c this was, and I was all set to say "Brother multifunction b/w laser printer", along with some colored copy paper and a long stapler that can reach the middle of a page. Everything you need to make some bitchin zines.

[–] nycki 1 points 1 week ago

Good callout! I agree, don't rewrite just for the sake of rewriting. By "barely works" I am referring to code that functions but where a small change to the requirements would make it incorrect. In that situation you should "break it" in order to add changes, rather than calcifying the legacy code by building around it.

[–] nycki 8 points 1 week ago (2 children)

I've worked in programming for the last ten years and the most important skill you might not have guessed: Bravery. People are going to say "if it works, don't fix it", but a lot of real-world code barely works, and you need to be willing to break it to make it better.

If you're good at your job, you will spend a lot of time reading other people's code and testing small changes to see what happens. Write "new" code for yourself, because it's fun and its good practice, but also learn to read and repair "old" code.

[–] nycki 7 points 1 week ago

there's an excellent joke in Cassette Beasts where you cross the cliffs of Eastham, and on the other side is a big boring dust bowl labeled "ham".

[–] nycki 10 points 2 weeks ago
59
submitted 2 weeks ago by nycki to c/196
 
62
submitted 2 weeks ago* (last edited 2 weeks ago) by nycki to c/[email protected]
[–] nycki 1 points 2 weeks ago

wow i cant believe nobody else pointed this out but today someone on discord informed me that I accidentally misplaced a bit when multiplying 10 by 101. According to this chart, two times five is eighteen.

[–] nycki 3 points 2 weeks ago

I'm using octal as a sub-base to make it easier to count digits, just like using commas to group decimal digits. I think that still counts as binary tho!

[–] nycki 7 points 3 weeks ago (4 children)

I have Syncthing set up to copy save data between my pc and steam deck, but not just for emulator stuff: its got my entire modded minecraft directory and my balatro modloader nn there too.

[–] nycki 3 points 3 weeks ago (2 children)

wait how does your clipboard shortcut work op? that sounds nifty!

 

inspired by The Best Way To Count.

91
mermaid diagrule (lemmy.world)
submitted 1 month ago by nycki to c/[email protected]
 

made this to demonstrate mermaid flowchart generator

 

Homeworlds is a pure strategy game played using a set of colored pyramids. The colors and sizes represent different resources, and the goal is to build an interstellar supply chain to destroy your opponent's home planet.

Because the game is pure strategy, there's a risk of the meta becoming stale someday. Chess and Go are intimidating to new players because you basically have to study centuries of meta before you can do anything new in them.

So I've been thinking about ways to modify Homeworlds to be "imperfect strategy". This is my favorite pitch so far: the Secret Weapon.


When building your homeworld at the start of the game, each player also secretly places a 12mm dice under a large opaque pyramid. I'm using black 'mids here because they're not used for any purpose in game. The number on the hidden die represents one of the four resource types: 1 = yellow (warp), 2 = red (steal), 3 = green (replicate), 4 = blue (transform).

Once per game, without costing an action, you may reveal your Secret Weapon. Immediately take any piece of that color from the bank, and build it at your homeworld.


I haven't playtested this yet, so let me know if you do. I'm hoping it would lead to situations in the early- to mid-game, such as "hmm, I think it's safe to build a large piece, because you can't steal it this turn... unless your secret weapon is red, of course." The bluff and counter-bluff would make it impossible to play perfectly, so the meta would always have room to evolve.

92
budget vr rule (lemmy.world)
submitted 1 month ago by nycki to c/[email protected]
 
 
109
dinosaur.png rule (lemmy.world)
submitted 1 month ago by nycki to c/[email protected]
 
 

I'm just not interested in hearing what bullshit FAANG is up to, I want to talk about linux kernel patches and raspberry pi revisions and maybe hear what people other than grifters are doing with neural networks.

 

I'm currently trying to set up a homebrew cassette tape storage format, but trying to use existing tech where possible. I was excited to see that minimodem already exists for converting an audio stream to a byte stream, and is even available in termux for android, so I could decode cassettes with my phone! However, I'd like some sort of higher-level tool to encode and decode "packets" or "slices" so that I can add error correction. I'm sure this sort of thing must exist for amature radio purposes.

I could write a script that cuts a file into slices, with checksums and redundancy for each slice, and then pads them with null bytes so I can isolate each frame when decoding. What I want is to find out if that's already been done. I've heard of AX.25 packets but I can't find a tool that does that with stdio.

 

This article says that NASA uses 15 digits after the decimal point, which I'm counting as 16 in total, since that's how we count significant digits in scientific notation. If you round pi to 3, that's one significant digit, and if you round it to 1, that's zero digits.

I know that 22/7 is an extremely good approximation for pi, since it's written with 3 digits, but is accurate to almost 4 digits. Another good one is √10, which is accurate to a little over 2 digits.

I've heard that 'field engineers' used to use these approximations to save time when doing math by hand. But what field, exactly? Can anyone give examples of fields that use fewer than 16 digits? In the spirit of something like xkcd: Purity, could you rank different sciences by how many digits of pi they require?

view more: next ›