Yet the simple blog website static page saying that looks very weird and broken on the desktop firefox.
How large should be a development team to make proper margins in 2026?
Yet the simple blog website static page saying that looks very weird and broken on the desktop firefox.
How large should be a development team to make proper margins in 2026?
Normally I'd just switch into FF reader view when it's that badly done but that doesn't work either.
This is my first blog post with graphics. so your comment helps me guage proportions
Weird, yes. Broken, I don't think so. Seems to just be a matter of taste.
The overall layout is fairly odd & weird - but it's the same in Chrome & Firefox. There is one technical bug with the main body font-size - it uses some invalid syntax (should be invalid in both Chrome & Firefox) & Chrome seems to be accepting it (against spec). The rule:
font-size: clamp( 1.125rem, 1.125rem + (1.333rem - 1.125rem) * (100dvw - 24rem) / (80rem - 24rem), 1.333rem );
Firefox drops it & falls back to the default body font, making the article text slightly smaller. But it's definitely not a layout-breaking bug.It's entirely possible I'm misreading the spec on clamp() but as far as I understood it, clamp() performs math on a bunch of comma separated fixed values, calc() handles arithmetic operators - this seems to be combining those without a calc invocation, but maybe I misread & overlooked clamp arithmetic operators. Firefox just says it's invalid, no detail on why.
I have LLMs align stuff for me all the time because I'm too lazy. It takes the screenshot, changes the code, code auto reloads and boom, done.
If everyone is doing the job of hundreds, extremely productive and everything is so easily fixed, why everything feels so slow and broken, even so basic things? That's kind of the point. I'd expect nearly perfect websites everywhere, especially from "productivity" people who mastered the flow.
This doesn't make sense. There were slow and broken things before AI. This was true even when the things were made by hundreds or thousands of engineers.
If an organization doesn't care about making their app or site fast or correct, then unless they have a truly ludicrous amount of free manpower (more than is available now with AI, because review and architecture are still bottlenecks), it probably won't happen.
AI doesn't change this. AI doesn't change the priorities of an organization, it just changes how quickly and cheaply they can build. And every org has a point in their priority queue where things are no longer worth it to spend resources on.
If Venmo didn't care about making their login page work well with Firefox (which, in my experience, they don't) before AI, why would you expect it to be better with AI?
Where it would take 6 hours to make a first cut of a static site, you can now do that in 15 minutes. Obviously that's not going to be perfect.
Excellent feedback, Thank you.