Remix.run Logo
digitaltrees 11 hours ago

I think a lot of people are excited at what feels like insane new velocity and tempted to ignore the hard learned lessons of good code vs bad code.

Here is a real conversation. “I built this app so fast it feels amazing, but then I looked at the code and it had a 6000 line class with one function that was 3000 lines of if statements”

“Oh ya that’s bad. You definitely need to refactor that”

“I thought that, but I wonder if it’s actually better to have a big class in a single file because that’s easier for the AI to understand than if it was in multiple files”

“Umm ok but do you even understand the 3000 line function? Couldn’t that be broken into better code that if/else soup?”

That conversation went on like that for a while.

Meanwhile, I have settled on a process where I built a framework that has good architecture built in and my version of using AI is essentially enforcing compliance with my architecture and coding patterns.

When cursor moved to an Agent view to remove human review I built my own IDE to ensure I never have to adopt stupid coding practices. I used AI to build it and had to constantly stop the AI from doing stupid stuff.

I am happy to share patterns and tools with you because AI can be a massive accelerator and produce good code when managed effectively but it requires a commitment to good code and willingness to ignore where the industry hype is right now.