u/TheBanq

I am really fascinated, how fast we as humans can adapt even to very small specific nuances in written text.

Even with models getting better and adapting in their writing style, it doesn't take long, until my AI Slop radar gets up to date.

Really interesting to see first hand, how good our algo, aka intuition is.

https://preview.redd.it/b6owx6346rah1.png?width=956&format=png&auto=webp&s=09d133bdf87c4a1f281417158a21da9c4144bde4

How can Fable be released again and GPT 5.6 is still only available for a selected group?

I thought Dario is the bad guy, according to US Gov/Trump...

Any frontend developers where already tried using Sonnet 5?
How does it perform in UI? How well does it compare in Claude design, compared to Opus 4.8?

Don't have any UI to build atm. so It's hard to check, curious for experiences

For many people, especially newer devs, vibecoding is kind of a trap.

The reason being is, that everything is so damn fast now - you can basically, with a good workflow go from idea to MVP within a day. But with every dev now having this power, standards and expectations increased dramatically!

A few years back even, the motto was "Ship fast, MVP asap!".
But for most projects, "Ship fast" didn't mean 1 day. It still ment many months.

Developing a fully working MVP as a solo dev, depending on the project would still take a long time, compared to now. Now comes the important point I want to make:

important note here; I am fully aware, that there are still projects, that are built within a week and are highly successful - but it's most of the time more experienced people and these projects aren't the norm!

This timeline has NOT changed!
A proper dev, will still take let's say 3 months to build the MVP.
And now, the standard for MVPs is a 3 month project WITH AI! Not a 3 month hand coded MVP!

What does that mean?
If you now deliver an MVP from the old days, especially if you work mostly with AI, it shows. Just because you now are able to build an MVP, that would previously take 3 month, doesn't mean, that it's good enough now. Because the bar has risen insanely high now.

How my philosophy changed.
I actually stopped thinking of what my next big app could be. Instead, I actually started a web-design business with my partner, which is built with full AI automations in mind (for the future).

So Instead of now building something, I think people need, I am building tools for myself.
I'm now doing something, that many others will also be doing. So building a SaaS basically just for myself now, gives me two very important leverages:

- No time pressure
I don't care how long I take to fully finish/polish my SaaS, because I mainly build it for myself to use. Even If I would never monetize it at all, it already is giving me value

- I am the user
By actually building something for myself, I am actually using my product and the amount of iterations I have already done, I know for a fact, I would have never spotted those, If i wasn't a heavy user first.

I am now building a Software Service, that makes my operation highly efficient, I am trying to optimize it for every client in a way, that it's universally useful for any web-dev.
By having all that time now, I will probably use my tool for many month, before even thinking about making it public.

The bar has risen and I think in most cases, releasing a half-assed MVP just doesn't work anymore. You have to actually prove, that it works first. Because people are very careful now with buying the next "this app will run your whole business"-SaaS.

Curious to hear what you think!

As far as I know, Sonnet always followed as a cheaper and more efficient model for Opus.

Since we only have Opus 4.8, is Sonnet actually secretly Fable, but "sonneted"?

Seems weird, that we are skipping 4.9 and going straight to Sonnet 5, since I thought Sonnet is based on Opus.

But having Sonnet 5, would indicate there is an Opus 5 - which I would guess is just called Fable?

Hello UX people,

I am currently building my own CMS for my web-design agency.
We currently only work with a calendar and tasks. We have a rough pipeline, from lead akquisition to the final sale and converting the lead to a customer.

My goal is to standardise the process and have a fixed flow with stations inbetween.
The CMS is only for me and my partner, so I'm able to build it however we like.

My idea is, to have this whole pipeline visualised, with every macro step also having a detailed view, since the bigger point have internal steps aswell.

https://preview.redd.it/9dgrdcficu8h1.png?width=1635&format=png&auto=webp&s=9bef24f7de1f95edcf7246ae53a4641b90e300e2

I brainstormed this rough idea, but I'm curious to hear your opinions.

I'm not sure if there are some proven designs for this kind of stuff and that I maybe trying to reinvent something, where there is already a well established design, that works.

What do you guys think, does this layout make sense for you? Could I maybe build it differently? I know, since the design is made for myself and my partner, I should be the judge.

But I am still curious to hear opinions on it and if there are known designs for this kind of stuff

I recently came across a website on mobile, that had a mobile navigation, where a 100vh was one sticky screen - once you swiped downwards, you landed on the next 100vh.

The very first moment I was a bit confused, but then I found it to actually be more user friendly.

All the information I was supposed to get, was perfectly layed out for obvious reasons.
And since nowadays you do so much scrolling on Instagram or some on tiktok, this kind of navigation felt very natural.

What are your opinions on that?
I'm building landing pages for local shops and am thinking of offering this format to my customers (if they want to), because I actually like it myself.
Makes doing mobile layouts so much easier, since you know exactly what will be on screen.

I just described a bug regarding a syncing error in a web-app I built for myself and my partner.

There was some issue, where the UI would jump back to previous IDs etc., so there is def. some problem in the architecture.

I gave Codex xhigh and Opus 4.8 Ultracode the exact same explanation and told them to do a deep audit, to really identify the current problem.

Codex took 4 Minutes and gave me a short audit.

Claude worked for 20, activated over 20 sub-agents on it's own.

Codex review was half-assed at best and overlooked so many things.
Opus gave me an insanely good review (which Codex agreed btw), which pretty much found the issue perfectly and is right now fixing it.

I'm a Codex user btw. and i'm just using the account of a friend right now, so I'm rather team Codex most of the time. But this comparison really makes me think of switching again - especially with the fact, that front-end in Claude Code is much much better.

I really hope 5.6 comes soon, otherwise I'll probably switch to Claude in my next 200$ cycle.

I recently came across a website on mobile, that basically had no native scroll.

After "scrolling" for a certain amount (so basically a swipe), the 100vh screen instantly moved to the next 100vh below. It kind of gives the feeling of swiping through reels on Insta.

First I thought "weird", but then again - with more people probably using reels and tiktok instead of real websites, this type of site navigation might even be more intuitive now for the newer generation.

Apart from that, It's actually much easier to design beautiful layouts like this, because you always have a fixed viewed section and can "perfect" this section for exactly 100vh.

Would love to get some more opinions on this.