danfritz

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.

Alternative https://github.com/peterldowns/localias

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

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.

Whats the improvement here? I spend more time fixing it then doing it myself anyways. And I have less confidence in the code Opus generates

Every time I see a post like this on HN I try again and every time I come to the same conclusion. I have never see one agent managing to pull something off that I could instantly ship. It still ends up being very junior code.

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...

Related to the recent announcement they are moving to Azure?

Looks cool but how much does it cost?

Not my experience, I have done fairly complex things like building / releasing a whitelabel ios and android app which is branded in ci per customer.

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

I've always used https://github.com/pzavolinsky/ts-unused-exports

Has more features (like excluding enums) and works very well in large code bases.

Clearly the real good refactor was using reduce instead of filter / map.

No need to loop twice over the array. Always use reduce if there are chained methods going through arrays

Ha great we finally arrive at the "Next.js React features" which basically forces everyone to use Next.js or an additional framework on top of React which now have to play catchup with whatever react - next.js think is "best" (for Vercels wallet). Expected outcome if half or the react core team is a Vercel employee.

Kinda new this day was coming, sad to see it actually happen

It seems dead? https://github.com/aws/chalice/issues/2067

I'm a long time material ui user and always disliked the tailwind approach of slapping classnames in a long string.

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...

Give it a couple of months: Why the f*ck are we templating JSON

This article feels very ironic to me hence the sarcasm.

Give me code as configuration and I'll be interested

Cut costs down to 90% by going serverless and run everything on lambdas?

Nothing keeps humming if it's not being used

Cannot get past rule 5, tried a bunch of different solutions from this thread but nothing works. Maybe a browser quirk ( I'm on Brave IOS)

Anybody else have the same problem?

Will definitely check this out! I'm a long time asdf user but I always struggle with the shims and long timeouts.

I occasionally hit 2sec until my node version is resolved.

With lambda you pay for what you use. It scales endlessly and is quite cheap. Depending on your typical usage and load it can be a huge cost saver (also mentally) as lambda will scale.

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.

You can enable the experimental `browsersListForSwc: true,` option which uses your browserlist to determine the appropriate target. You can also disable `legacyBrowsers`

ref: https://nextjs.org/blog/next-12-2#other-improvements

An article on how to not break to new lines in the middle of a word, makes it hard to read. You can improve by running

  $('.content').style.hyphens = 'none';

Sadly Lottie is a huge dependency, for one or two animations I find it wasteful to even add it. Another downside is that your lighthouse score gets negatively affected since the animation is seen as busy time so your time until interactive becomes very long. I'm always looking for a smaller alternative

I've worked with angular 1.x never made it to the upgrade of v2 and moved to React. I couldn't grok the two way data binding which seems odd let alone all the decorators / services / controllers patterns. In the end I had no clue what I was doing.

I do like to read up on these kind of things, but why should I be excited about Angular 13? Except from yay faster because of esbuild (like any other frontend framework).

Looks like CSV described. Gzip the json and don't care about the biggest selling point

This will never get any traction except for startup hype. The economics just don't work and the end user sees nothing changed since frontend stays the same?

How complicated and expensive can you get. Engineering is about solving problems with the right tools and with the least amount of maintenance.

This is inventing a whole lot of stack for what? Your pipedream of "decentralised" internet. They fork Ethereum chain continueslly for their own gain, aka it's managed centrally!

/endrand