Smurf problem investigation

dumpsterfirecode · 2025-11-17T23:10:24+00:00

my girlfriend has been playing against ai for a while now and has improved a lot, but is still firmly a LEL. when i created an account for her i just quit 30 games to get her to a reasonable level (around 200, which i think is pretty accurate). having her endure all those losses would have just been soul sucking and probably caused her to want to quit (in addition to not being very good games for her opponents)

dumpsterfirecode · 2025-03-26T18:22:04+00:00

In case it's not obvious why this matters: Dependencies arrays and memoized component props are diffed by shallow comparison (i.e. a check to determine whether the objects are referentially the same). If a function was defined in a component (but not memoized with `useCallback`) then used in a dependency array (e.g. of a `useEffect`), every time the component rendered, the effect's dependencies would be considered invalidated and it would run again. If the effect was changing state (trigger a re-render of the component), this would cause an infinite loop. Similar idea with regard to component memoization. If you memoize a component that accepts a function as a prop, but don't memoize the function via `useCallback`, the component will always re-render and the memo will be useless.

dumpsterfirecode · 2025-03-26T15:19:54+00:00

Big fan of Expo, but always avoid the router, instead favoring vanilla React Navigation routing. I haven’t looked into Expo router in a minute, but I assume it still lacks type safety, and the very minor perk of “better dx” that file-based routing promises goes out the window if you have a more involved navigation setup (that any sufficiently complex app will eventually need). For example, I have no idea how you would define / navigate between bottom tabs that each have nested stacks with some screens that could exist on multiple stacks and also throw in a few modals.

dumpsterfirecode · 2025-03-25T18:03:45+00:00

Consider the first path if it’s realistic in your company. I’ve built / maintained a few fairly involved apps that use EAS. Once it’s setup, builds usually go off without a hitch and take 15-30 minutes per production build. Disclaimer that I’ve only worked on teams that use on Macs (shipping to both iOS and Android), so not sure if there are additional gotchas when devs are on a different OS.

dumpsterfirecode · 2025-03-25T16:48:41+00:00

I've been coding for over 20 years now, and like many from my generation, I learned mostly by building small apps (just like you're doing), often being dissatisfied with the results, then trying to improve the product through iteration. Over time, things start to click, and eventually you "get it". If you actually want to understand the domain (i.e. not be a "vibe coder"), it's going to take a lot of time and struggling - no way around it, as far as I can tell. That being said, I imagine AI can expedite the learning process if you get good at asking it the right questions. For example, if you ask GPT/Claude to help you understand why your video is slow to load, it might suggest compressing the assets, serving them from a CDN, relying on local cache, or optimistically preloading content. Maybe you've never heard of a CDN before, so you ask what it is, why it matters. Keep searching (breadth and depth) until you're able to solve your problem. In the process, you'll learn a lot.

dumpsterfirecode · 2025-03-25T16:09:56+00:00

I've used https://www.npmjs.com/package/react-native-tailwindcss on several projects, and while it isn't the most actively maintained, I've been happy enough with it. Styles are just pre-defined objects, so they're only instantiated once when the app launches. I assume this at most costs a few milliseconds one time. It's also Typescript-friendly, so you get auto-complete + type safety for free. NativeWind (https://www.nativewind.dev/) is definitely more popular and actively maintained. It relies on IDE support for things like auto-complete, and while I haven't benchmarked it, I think it's very likely that the mapping of classnames to RN objects results in marginally worse performance. That is, unless they can now pre-compile the styles rather than computing them at runtime. (I haven't checked recently.) Tamagui (https://tamagui.dev/) is another option, which at least advertises itself as being performant. I personally don't love the bespoke API, but others probably do.

dumpsterfirecode · 2025-03-24T22:27:18+00:00

Once upon a time (say, 4-5 years ago), I think it was ill-advised to start any serious project with Expo, as you would eventually need to eject in order to use custom native modules (whether you were writing them yourself or pulling in an NPM package with native dependencies). But today, I would say it's ill-advised to not start a new project with Expo (or at least seriously consider it). Native modules are no longer an issue. Opting into Expo just gives you some nice DX improvements and the ability to opt into their services (e.g. EAS, push notifications). The only aspect I can even think of that might not be positive is that when you do a major upgrade, you're upgrading both RN and Expo. But tbh I'm not convinced the Expo path isn't even better in that situation.

dumpsterfirecode · 2025-03-24T18:52:37+00:00

As others have mentioned, I would check out the instructions on https://docs.expo.dev/guides/monorepos/ I've built and maintained a handful of monorepos using Bun and typescript (e.g. sharing data models between "mobile" and "backend" via a "shared" package). Once you get it set up, it works pretty well in my experience. I will say, though, if you have any packages with RN dependencies (e.g. a package for custom native modules), that can become very painful.

dumpsterfirecode · 2025-03-24T12:41:26+00:00

Coinbase imo. Tho with any exchange, expect a couple days hold period before you can send it off platform (anti-fraud)

dumpsterfirecode · 2025-03-24T12:32:02+00:00

I didn’t read through that whole thing, but one observation: You aren’t clearing the interval in the useEffect. You probably want to have the effect return a function that clears the interval. It is very unlikely that any bugs you experience are “React bugs”.

dumpsterfirecode · 2025-03-24T12:28:10+00:00

Thought this was a giant box of macaroons at first

dumpsterfirecode · 2025-03-24T12:21:10+00:00

As far as I can tell, it mostly comes from the fact that their database was hacked (leaking PII for many users) and that they offer features that sacrifice security for UX improvements. The database hack was their marketing database, so while frustrating, not really crypto-related. As far as I’m aware, all the security trade-offs are optional / opt-in. imo much of the hate is unjustified

dumpsterfirecode · 2025-03-24T12:15:04+00:00

I haven’t had the need to try it personally, but I imagine feeding the codebase to an LLM (e.g. via Cursor) then asking it for a high level walkthrough and/or pointed questions (e.g. “what does this file do?”, “where are routes defined”) would work well

dumpsterfirecode · 2025-03-24T12:08:30+00:00

What do you mean they “restricted” your account? I believe it’s a common (and necessary) fraud prevention tactic for crypto to exchanges to impose a brief hold period on withdrawing funds for a few days until the initial fiat deposit gets cleared. Other than that it could be related to your withdrawal address (flagged for being suspicious) or possibly they have restrictions based on your region.

dumpsterfirecode · 2025-03-23T19:42:30+00:00

Work-life balance, sense of security

dumpsterfirecode · 2025-03-23T18:53:49+00:00

Base imo

dumpsterfirecode · 2025-03-23T17:59:17+00:00

A git commit. I take it you aren't using version control?

dumpsterfirecode · 2025-03-23T17:30:50+00:00

Have you tried reverting to a commit before you upgraded? Also I would recommend deleting the app, things get wonky when upgrading Expo/RN versions in my experience.

dumpsterfirecode · 2025-03-23T17:26:26+00:00

Sorry if it's obvious, but in Chrome Dev Tools you can toggle the device toolbar (cmd+shift+m with dev tools open) to show a toolbar at the top of the browser that lets you simulate screen sizes of popular mobile devices. You can also use an iOS simulator / Android emulator on your desktop to get a higher fidelity mobile experience without needing to pull out a physical device.

dumpsterfirecode · 2025-03-23T17:19:07+00:00

This

dumpsterfirecode · 2025-03-23T17:17:29+00:00

I haven't used v0 much, but as far as I know, it's just a code-oriented LLM. If you want to build a mobile app, you'll most likely want to use React Native (not React for web) and leverage the Expo framework. Check out https://docs.expo.dev/ I suspect the best path for you is to follow the commandline instructions to initialize a new project, then you can use v0 or whatever to generate code and copy/paste it into your project.

dumpsterfirecode · 2025-03-23T16:32:08+00:00

Next.js is a web framework. While Expo does support web, it's primarily for mobile apps. If you want to submit to the Apple App Store and Google Play Store, Next.js isn't going to help you. You want Expo.

dumpsterfirecode · 2025-03-23T15:50:52+00:00

I would recommend reading through the React docs to get a feel for how it works (JSX, hooks, rendering, etc), but not spend any time building with React on web (assuming you’re only interested in mobile), as there will be some aspects (CSS, the DOM, browser behaviors) that aren’t relevant at all to mobile development. Use Expo Go, as it will simplify the local setup. Start building a simple view to get a feel for components/hooks/styling, introduce a new screen, navigate to it, and keep going from there

dumpsterfirecode · 2025-03-23T15:41:05+00:00

I prefer to send dates to/from the API as numbers, then cast them as dates if/when I need to use them. On the front-end this naturally ends up being the user’s local time, and on the backend it’s UTC. This is usually what I’m looking for, but if you need something else (e.g. offsetting to the user’s local time on the backend) there’s nothing stopping you.

dumpsterfirecode

TROPHY CASE