Yes that's why
562 karma · joined November 10, 2015
Yes that's why
Still holding off for now
IMO the reset should fire regardless what happens after it.
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
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.
There is no need to set uuids through javascript or node imo
Granted no fancy UI to start and stop things but is it really needed?
Tbh this is not a single binary you need dnsmasq go and other things
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
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
I just tried again and ask Opus to add custom video controls around ReactPlayer. I started in Plan mode which looked overal good (used our styling libs, existing components, icons and so on).
I let it execute the plan and behold I have controls on the video, so far so good. I then look at the code and I see multiple issues: Over usage of useEffect for trivial things, storing state in useState which should be computed at run time, failing to correctly display the time / duration of the video and so on...
I ask follow up question like: Hide the controls after 2 seconds and it starts introducing more useEffects and states which all are not needed (granted you need one).
Cherry on the cake, I asked to place the slider at the bottom and the other controls above it, it placed the slider on the top...
So I suck at prompting and will start looking for a gardening job I guess...
Like othes have suggested, keep the actions simple by having lots of scripts which you can iterate on locally and making the actions dump to just run the scripts
Has more features (like excluding enums) and works very well in large code bases.
No need to loop twice over the array. Always use reduce if there are chained methods going through arrays
Kinda new this day was coming, sad to see it actually happen
After reading the excellent article it hit me, I'm already doing the exact same :facepalm:
<Box mr="4" border="1px solid #ee"... />
There is really no difference, instead of a string with classes I have a bunch of props. Time to look at tailwind again...
This article feels very ironic to me hence the sarcasm.
Give me code as configuration and I'll be interested
Nothing keeps humming if it's not being used
Anybody else have the same problem?
I occasionally hit 2sec until my node version is resolved.
With ECS Fargate it costs money even without any traffic and you are responsible for correctly implementing auto scaling.
I'm coming from 10y rails dev background and now full stack typescript. Thinking in pure lambda functions is a breath of fresh air for me.
$('.content').style.hyphens = 'none';
flies away