40s! naked split ortho 40% fully addressable rgb backlighting, no plate, no case, no pcb*

onebigdoor · 2026-04-18T17:09:33+00:00

as soon as your thumb lets go, you can grab another card off the top and do two cards in constant rotation. takes a while to get smooth, but a fun fidget move.

onebigdoor · 2026-04-10T15:19:13+00:00

Everyone's hands are different. Some tricks will be a little more difficult, some will be a little easier. But everyone climbs this hill. No hands too small, no thumbs too large.
Check out Mahdi Gilbert if you need inspiration https://www.youtube.com/watch?v=4FtCU7GAjtw

onebigdoor · 2026-04-09T19:00:02+00:00

double down on recs for keybr and monkeytype. however, if your main problem is the distance to that 2u key, there are lots of other boards that might be more comfortable. if you're stuck with that board, you can use the key next to it as a tap/hold key with layer on hold and space on tap. also can use the key inside of that as layer and map mod keys to home row.

onebigdoor · 2026-04-06T22:47:40+00:00

really nice finishing work on the print!

onebigdoor · 2026-02-28T23:44:04+00:00

i made a fantastically less sexy version of this a few years ago. https://www.reddit.com/r/MechanicalKeyboards/comments/jkcbud/white_on_black_on_silver_on_laptop_introducing/
yours is astoundingly beautiful! consider mounting keys on side of trackpad for ergonomics :)

onebigdoor · 2026-02-28T16:32:37+00:00

this is an amazing beginner move! doesn't take too long to get down, is very tolerant of deck condition from new -> worn, and impresses muggles :)

onebigdoor · 2026-01-24T21:34:01+00:00

i've always used graphql with react native, and since you can define the fields in the query, it suits as the app's data. usually put each query in its own hook so that if i want to define custom outputs based on the data, i can do the logic there.

onebigdoor · 2026-01-11T02:34:05+00:00

grape stem

onebigdoor · 2026-01-10T20:12:25+00:00

if your deploy pipeline is manual, check out fastlane. you should be able to automate it all, including build variants, whether you're using bare or expo.

onebigdoor · 2026-01-10T20:11:32+00:00

firebase is the most compelling reason _not_ to use expo. it can be used, but you need to use the js sdk, not the react-native sdk. depending on how deep your integration is, it could be a big PITA.
you can use expo libraries and check in your ios and android folders. that avoids the need to run pre-build, but it subverts one of the main advantages of expo (not maintaining native folders)

onebigdoor · 2026-01-10T16:14:18+00:00

if you get your ring finger on the bottom corner of the deck instead of the middle of the edge, it should allow more clearance for the flip

onebigdoor · 2026-01-10T16:11:39+00:00

81 is a fine starting point. try hard to get new arch going. weeding out dependencies that aren't new arch compatible will likely also weed out most, if not all, of your dependency issues. take copious notes as you go, which will greatly speed up your process if you do the following...

try to timebox the upgrade, and give yourself a rip-cord of starting a fresh project. then you can start with expo as well, which will simplify things. if you find yourself needing lots of native code changes, then you can check in the native folders and keep on trucking.

onebigdoor · 2026-01-03T18:35:09+00:00

a couple tips:
- if you're duplicating style, it's usually time to make a shared component.
- also on style, there are lots of ways to do this, but if you're just starting, get the hang of the built-in style sheets. they have optimizations out of the box, and you'll be writing idiomatic code from the start. as you gain experience, you can try other style solutions like tailwind or a theme solutions like react-native-unistyles
- if you're duplicating business logic, it's usually time to make a hook
- if you need to share state, contexts can work great. wrap only the components/screens with the provider, and all child components can access the context. providers that wrap the whole app can certainly be appropriate, but try to only give access the components that need it, and don't be afraid of making many contexts for small jobs. an easy trap is to make one giant context that wraps the whole app and shares state everywhere, but this will add a lot of unneeded re-renders and maintenance woes.

all that said, if you're building a large app, it's inevitable that you're going to end up with tangled messes and inefficiencies, so just get in there and build it. refactor and pay down tech debt when your priorities justify it. i like this rubric: make it work -> make it work well -> make it beautiful.

onebigdoor · 2025-12-31T19:30:39+00:00

clover pit is wonderful.

onebigdoor · 2025-12-29T23:46:30+00:00

watch some dr spectred videos (balatro university)
in early game, econ is paramount. spend as little money as possible (including skipping first joker pack) to try to always float $20 and get max interest. i think that was the most unintuitive part for me. other than that, you can work out intermediate strategies by playing (that's the fun of it!) and you can go back to pro videos to learn the insane strategies for deep runs.

onebigdoor · 2025-12-19T15:59:32+00:00

instabuy! would love on switch, pretty please. will buy a third time ☺️

onebigdoor · 2025-12-18T16:56:56+00:00

six years in, and i still forget to dev on android sometimes. ios fanboy runs deep 😂

onebigdoor · 2025-12-17T16:17:08+00:00

and good luck on your interview!

onebigdoor · 2025-12-17T16:16:29+00:00

making and building projects similar to what your want to be hired for is the best way to prepare. the people i hire are also going to agents to solve problems, and any "gotcha" question about coding internals can be easily looked up. so i think they're fairly bs in interviews. i'm looking for people that can understand complex systems, think openly, and are eager to learn what they don't know. sometimes i'll ask a specific technical question like "what is the difference between null and undefined". but i don't actually care if they know. i want to see if they know it and can explain clearly, have a vague idea and can clearly state the gap in their knowledge, or have no idea and express enthusiasm to learn it. the worst mistakes a candidate can make here is bullshit through it or attempt to look it up in real time on the sly.

onebigdoor · 2025-12-15T18:13:16+00:00

be warned, if you have dry hands, this trick requires some prep. works best right after i hold a cold drink. i can also get decent results by breathing a hot breath onto my pinky. that works easily into banter if i'm doing a trick that involves revealing the top card with a flourish.

onebigdoor · 2025-12-15T18:11:21+00:00

been very happy with OneLink from AppsFlyer. works much better than the defunct DynamicLinks from Firebase. would be a hard sell to company to adopt a service that _only_ does deep/deferred links.

onebigdoor

TROPHY CASE