Remix.run Logo
▲ catchnear4321 3 hours ago

This feels a bit like the other extreme.

It can meaningfully “type” faster than you.

Take the handicap if you really wish to, I suppose.

▲adamddev1 2 hours ago | parent [-]

I do understand that it is extreme, but I think the principled stand makes my code and my skills better in the long run. I'm banking on building less, but building better. Otherwise where do you draw the line in losing quality and understanding? And for what I'm working on, typing is rarely the bottleneck anyways.

I still use LLMs (cautiously) for searching and troubleshooting API things.

▲RetroTechie 2 hours ago | parent | next [-]

> I'm banking on building less, but building better

Same here. But as opposed to the "use AI" vs. "don't use AI" crowds, I'd prefer a more pragmatic approach:

Do whatever possible to maximize the quality of the software. And with quality I mean correctness, reliability.

AI is just another tool there. Where it helps produce more correct, reliable code, consider using it. Where it doesn't, don't.

Sadly it seems many companies have a different definition of "better" (featuritis, shortest time to market, developer productivity, etc).

▲catchnear4321 2 hours ago | parent | prev [-]

Letting go of the typing isn’t a light decision. And it is harder to get good output when it’s also simply a lot of output.

I’m banking on that being an evolving, but necessary skillset. For a while at least. And I’m still gaining experience in the process.

Plenty of exposure, plenty of prior experience, it’s a weird mix of management-ish context handling and sme mentorship while also providing the research benefits you mentioned.