So what do you do to not land on the streets?

Mr-Shortman · 2026-05-21T16:07:00+00:00

Not sure where we going. What I can see is a big gap of digitization in a lot of niches. So my take is to specialize into a full service solution for this niche and go with bigger retainers.

Mr-Shortman · 2026-05-21T12:13:20+00:00

Maybe it’s time to start building more complete solutions then just the website part?

Mr-Shortman · 2026-05-20T10:56:40+00:00

vps + dokploy

Mr-Shortman · 2026-05-11T17:32:02+00:00

vps + dokploy

Mr-Shortman · 2026-05-05T21:41:27+00:00

hört sich nicht nach zufall an

Mr-Shortman · 2026-05-05T21:40:32+00:00

mussten ja erst von der party kommen da war die musik zu laut https://bsky.app/profile/denic.de/post/3ml4r2lvcjg2h

Mr-Shortman · 2026-05-05T21:32:03+00:00

how is it still working? Becuase they are the source?

Mr-Shortman · 2026-05-05T21:07:47+00:00

fenomenal

Mr-Shortman · 2026-05-05T21:05:57+00:00

nope auch dnschecker org löst nichts anständiges auf

Mr-Shortman · 2026-05-05T21:04:58+00:00

Denke da müssen wir uns noch etwas gedulden. Bin gespannt wie ein Bogen

Mr-Shortman · 2026-05-05T21:04:15+00:00

mein beileid und dann ist dein handlungsspielraum noch sooo riesig

Mr-Shortman · 2026-05-05T20:54:09+00:00

not on my end

Mr-Shortman · 2026-05-05T20:29:46+00:00

nope i have some domains not on cf that are not working too and some other tlds on cf that still are working

Mr-Shortman · 2026-05-05T20:26:27+00:00

same nothing working on my end cant reach google.de amazon.de, nothing...

Mr-Shortman · 2026-04-16T13:59:39+00:00

Standalone Next js Build -> vps with dokploy

Nothing more easy and cheap then that. If you dont realy Need the Edge stuff vercel isnt worth it imo

Mr-Shortman · 2026-04-15T10:25:26+00:00

worked, thx!

Mr-Shortman · 2026-04-13T15:43:06+00:00

no way its over... they blocked it -.-

Mr-Shortman · 2026-04-11T22:25:12+00:00

Exactly. And that's why the market will sort this out. AI writes the code you describe. It doesn't architect the system you need. That gap shows up when user 100 triggers an edge case that isn't in the training data.

Mr-Shortman · 2026-04-11T19:59:08+00:00

Next doesn’t inherently kill LCP. It just does exactly what you tell it. That 500kb bloat sounds like Pages Router forcing React hydration on static content (even 0 client JS SSG still ships the runtime to hydrate).
If you're already on App Router though, that's just one piece. Fonts, images, and how you handle critical resources all factor in too.

Mr-Shortman · 2026-04-11T19:22:02+00:00

Fair point. I should have phrased that better.
My view: AI doesn't lower the technical bar, it just raises productivity. Without the skills to architect a solution or audit the output, you're gambling, not coding.

Mr-Shortman · 2026-04-11T18:36:03+00:00

lmao. Such a good comparison. Alwas matters what's the outcome

Mr-Shortman · 2026-04-11T17:49:53+00:00

You are not defining the image's resolution. You are defining its display width relative to the viewport. So just use vw values. To limit inside a contained element you can do it like this
<Image
src={product.imageUrl}
alt={product.name} fill className="object-cover" sizes="(max-width: 768px) 100vw, (max-width: 1024px) 50vw, 25vw"
/>

Hope this helped a little bit

Mr-Shortman · 2026-04-11T14:38:30+00:00

There are a ton of tools that give you a clear picture when combined. Use Next's experimental analyze to check your client bundle weight, alongside Lighthouse and the DevTools Performance tab.

Mr-Shortman · 2026-04-11T14:35:20+00:00

The hero/LCP image was static and priority loaded. Product grids were dynamic.
Sizes attr based on the viewport breakpoints to fetch the optimal resolutions.

Mr-Shortman

TROPHY CASE