sh03
@sh03.dev
🇮🇹 Software Dev. Primarily: Typescript, React, 🐘 PostgreSQL.
🤌
🤌
Still can't believe the UI/UX community allowed floating action buttons to be popular. There should be Nuremberg trials when the reign of terror, this anti pattern has brought upon us, ends.
I bet they are the same people that are now trolling us with the liquid glass design.
I bet they are the same people that are now trolling us with the liquid glass design.
December 2, 2025 at 12:18 PM
Still can't believe the UI/UX community allowed floating action buttons to be popular. There should be Nuremberg trials when the reign of terror, this anti pattern has brought upon us, ends.
I bet they are the same people that are now trolling us with the liquid glass design.
I bet they are the same people that are now trolling us with the liquid glass design.
We have officially gone too far.
Yet another directive.
Nobody writes code like this, come on. This is a solved problem: you create a task queue and then have a scheduler execute these tasks.
Why is the ecosystem moving more and more towards pure magic?
Yet another directive.
Nobody writes code like this, come on. This is a solved problem: you create a task queue and then have a scheduler execute these tasks.
Why is the ecosystem moving more and more towards pure magic?
November 1, 2025 at 4:34 PM
We have officially gone too far.
Yet another directive.
Nobody writes code like this, come on. This is a solved problem: you create a task queue and then have a scheduler execute these tasks.
Why is the ecosystem moving more and more towards pure magic?
Yet another directive.
Nobody writes code like this, come on. This is a solved problem: you create a task queue and then have a scheduler execute these tasks.
Why is the ecosystem moving more and more towards pure magic?
@infrequently.org Corporate needs you to find the difference between these two pictures
October 8, 2025 at 9:22 PM
@infrequently.org Corporate needs you to find the difference between these two pictures
I absolutely despise this way of presenting filters. It's so chaotic and difficult to implement correctly. It's a prime example of a lose-lose UI component. You, the company, the users... Everybody loses.
September 17, 2025 at 4:42 PM
I absolutely despise this way of presenting filters. It's so chaotic and difficult to implement correctly. It's a prime example of a lose-lose UI component. You, the company, the users... Everybody loses.
This is prototype-level code. Less than 330 lines of code. 1 single objective. Using a library that is battle tested to solve that objective. With extensive documentation and examples.
Somehow it managed to create a non trivial bug.
This is the latest (released 56 days ago) "Pro" model.
Somehow it managed to create a non trivial bug.
This is the latest (released 56 days ago) "Pro" model.
August 12, 2025 at 10:04 PM
This is prototype-level code. Less than 330 lines of code. 1 single objective. Using a library that is battle tested to solve that objective. With extensive documentation and examples.
Somehow it managed to create a non trivial bug.
This is the latest (released 56 days ago) "Pro" model.
Somehow it managed to create a non trivial bug.
This is the latest (released 56 days ago) "Pro" model.
... surprise, surprise! The bug was not fixed.
At least it fixed the height issue while dragging items.
Now it's the width that shrinks instead.
At least it fixed the height issue while dragging items.
Now it's the width that shrinks instead.
August 12, 2025 at 10:04 PM
... surprise, surprise! The bug was not fixed.
At least it fixed the height issue while dragging items.
Now it's the width that shrinks instead.
At least it fixed the height issue while dragging items.
Now it's the width that shrinks instead.
I kept prompting it the errors to try and fix them but there was just no way and I was getting irritated so I slapped some `!` to make it all compile (not modifying the resulting JS).
I got this:
I got this:
August 12, 2025 at 10:04 PM
I kept prompting it the errors to try and fix them but there was just no way and I was getting irritated so I slapped some `!` to make it all compile (not modifying the resulting JS).
I got this:
I got this:
