danfritz

Ever used a time field in pure html? And then you get reports users can enter 99 minutes.

Yes that's why

I didn't check it yet but I hope being in EU macOS 27 upgrade is basically small UI tweaks and thats it :D

Still holding off for now

Yep, it seems that if you hammer messages things get easily dropped or the async behavior is not executed.

IMO the reset should fire regardless what happens after it.

This feels a lot like sagas and redux sagas. Anyone else got that vibe?

It's my daily driver, it's fast affordable and with a bit of guidance gets the job done.

I only reach for Claud when i need to plan something big or want to have a sparring partner to fire of some ideas.

I think what a lot of people don't realize is that you don't need a fronteer model for 80% of coding tasks. Composer 2.5 is often more than good enough, less token hungry and way faster

This resonates a lot with me. I often use AI for the plan and let it propose multiple possible implementations, I often have to point out the glaring easier / logical solution.

When implementing its often a lot of misses with a few golden hits. The other day it used flex for a table layout while our app uses tables everywhere sigh.

Another typical one is that it tends to prefere frontend aggregation and looping of data instead of letting the database and backend deal with it.

Using mix of claude, cursor composer and codex.

Always let your db generate uuids. On postgres this is easy since v18 it supports uuid v7!

There is no need to set uuids through javascript or node imo

I wonder how well this corolates with azure incidents. Especially for the US regions.

I can only say: learn how to use reduce and you never loop twice through a list of items or objects.

To me reduce is very easy to reason about and makes it super easy to properly filter, combine, extract values without ending with filters on filters on maps and maps

Ha yes classic showcase of:

1) obvious green field project 2) well defined spec which will definitely be in the training data 3) an end result which lands you 90% from the finish

Now comes the hard part, the last 10%. Still not impressed here. Since fixing issues in the end was impossible without introducing bugs I have doubts about quality

I'm glad they do call it out in the end. That's fair

Indeed totally unbearable to even read the article

By the time I have figured out all those quirks and guardrails I could have done it myself in 45min tops.