57 karma · joined December 15, 2025
What if we built things that are meant to last? Would the world be better for it?
I don’t think Russia can continue to sustain losses at these rates. Putin can remain as stubborn as he wants, but if Russian soldiers are being hunted down by drones faster than they can be mobilized, the frontline will recede.
The fast transition suggests there was a strong pressure to switch, which probably didn’t come from animal hunting patterns.
I'm wondering about temporary gamestate that doesn't need to persist. Things like terrain or destructible voxels, where the size could be prohibitive to keep in a databases, but would work well in memory or with a cache.
How does it distinguish which tables have foreign keys to other tables? Can with work without defining constraints?
You ask the coding assistant for a brand new feature.
The coding assistant says, we have two or three or four different paths we could go about doing it. Maybe the coding assistant can recommend a specific one. Once you pick the option, the coding assistant can ask more specific questions.
The database looks like this right now, should we modify this table which would be the simplest solution, or create a new one? If you will in the future want a many-to-one relationship for this component, we should create a new table and reference it via a join table. Which approach do you prefer?
What about the frontend, we can surface controls for this in on our existing pages, however for reasons x, y, and z I'd recommend creating a new page for the CRUD operations on this new feature. Which would you prefer?
Now that we've gotten the big questions squared away, do you want to proceed with code generation, or would you like to dig deeper into either the backend or the frontend implementation?