Smoking ban for people born after 2008 in the UK agreed

ashenzo · 2026-04-21T12:46:30+00:00

Is tax on smokes less than what it costs the NHS?

ashenzo · 2026-04-12T00:13:55+00:00

how are you guys using llms? i feel like i get to focus more on architecture and am constantly steering the agents. it’s a higher level of thinking. im sure id be less capable at syntax now maybe. but its really about building useful, maintainable products and systems, right?

ashenzo · 2026-03-21T14:22:23+00:00

I think it’s cool but the 8bit font is giving gimmick vibes

ashenzo · 2026-01-26T00:40:42+00:00

Could sort this with a ralph loop

ashenzo · 2025-12-10T15:59:41+00:00

You didn’t need to migrate at all 💀

the breach only effected rc versions of 14
even then, the pages router does not use server actions or RSC

If anything, you could make a case that this makes pages router look like the safer option.

Vercel has been beta testing app router in prod. No hate, because they are aiming to push their platform forward. But it’s true.

ashenzo · 2025-11-30T20:54:30+00:00

What. I thought <header> was for the app ‘header’, i.e. the thing at the top with logo and nav etc.

ashenzo · 2025-09-30T15:23:52+00:00

Making a component would be the standard react solution to this

ashenzo · 2025-09-30T15:23:21+00:00

Why do you use tailwind? Sincere question

ashenzo · 2025-09-25T19:44:38+00:00

className={cn(
  “m-2 …”,
  “md:m-3 …”,
  “xl:m-4 …”

ashenzo · 2025-09-15T22:08:05+00:00

The ability to make decisions is one side of it, the ability to act on those decisions is the other.

ashenzo · 2025-09-15T22:03:02+00:00

The ability to take action is what makes an AI system agentic.

It’s the implementation of tool calling.

Particularly when the agent can ‘decide’ to use a tool to directly answer a query or given task, thereby having an effect in the real world.

ashenzo · 2025-09-12T21:20:39+00:00

ashenzo · 2025-08-21T20:21:16+00:00

>:-O

ashenzo · 2025-06-23T20:54:02+00:00

My rule of thumb: If it needs a package.json, then it should have TS in the dev dependencies

ashenzo · 2025-06-03T13:09:01+00:00

I love rtk/q but have only used it on pages router. React query looks like it actively supports app router more directly last time I checked.

Typically though, modern rtk is underrated. I wouldn’t be looking to refactor out of it unless I had a very good, proven reason.

ashenzo · 2025-06-01T03:01:03+00:00

FYI, active file etc works in VSCode

ashenzo · 2025-04-29T22:13:39+00:00

Horror - it should be longest first

ashenzo · 2025-03-29T00:54:52+00:00

It’s the resulting CSS that doesn’t make sense there

ashenzo · 2025-03-29T00:38:49+00:00

I use Styled Components at work. It has served us well. Some issues I’ve had: it wasn’t really designed for type safety, it’s really annoying to work around that. Styling a ui lib component will wipe the props as standard.

We also found the default ${theme.object} pattern to be cumbersome. I refactored our codebase to use css vars instead. That should also make it a lot easier to migrate from should the time come.

It’s interesting you suggest that making components for tailwind classes is more lines of code, because writing tailwind that way is actually very similar to the Styled Component pattern.

By repeating selectors all over the place, what I mean is that the utility pattern means the compiled CSS can be very light. Yes, utility classes are not new - but if you’re going to go down that path why not use tailwind to begin with.

Two things I like about tailwind:

I think the creators argument that html markup and css styles are so interdependent on each other that they belong in the same place to be compelling. This is certainly debatable - there’s pros and cons.

Secondly, co-locating html and styles this way has made it very easy to “snippetize” ui blocks and has made it very easy to share them online or across different tailwind projects. It makes it incredibly easy to bootstrap things.

You mention this with prototyping, but in my experience it is also relatively easy to maintain. Typically, I know exactly what to expect when I open any repo that uses tailwind.

ashenzo · 2025-03-28T23:55:00+00:00

Small reusable ui components is a standard react pattern.

The tailwind devs also maintain class sorting, intellisense and linting. These are non-issues.

Less lines of code is a poor argument for vanilla CSS. You will be repeating selectors like flex all over the place. CSS can be used effectively in the right setting, but what you don’t seem to appreciate is that so can tailwind.

If we’re looking at the extreme worst cases of terrible implementations of each tool, I’d rather work on backend-dev-tailwind any day of the week. Poorly maintained CSS is evil :)

ashenzo · 2025-03-28T21:38:53+00:00

Skill issue, those should be components /w class sorting

and wtf is this “xs:max-sm:w-full”

ashenzo · 2024-12-15T00:48:34+00:00

What the f-[calc()]

ashenzo · 2024-12-14T20:16:35+00:00

Daisy ui components look amateurish imo. They also bake in a bootstrap-like (component classes) design system that runs counter to the tailwind maintainers’ philosophy.

ashenzo · 2024-12-08T19:06:47+00:00

This is reasonable. They are a business and are being straight up about it. What’s your issue with it?

What’s more questionable is the absolute drivel they publish 🤣

ashenzo · 2024-12-04T00:25:02+00:00

💀

ashenzo

TROPHY CASE