Tomasz Guz

Web Developer | WordPress, design, details.

[Tomasz Guz @kodemdev]

@KinasRemek @stocktavia @hazan Mamy tutaj Panowie realnie pokazany przykład problemu nazewnictwa produktów, które wybrała META 😄. @stocktavia mówi o nowym, personalnym agencie Muse, @KinasRemek o modelu/rodzinie modeli, i pomijając nieporozumienia, obaj Panowie macie rację.

[Tomasz Guz @kodemdev]

Z jednej strony mamy narrację, że AI jest świetne i ludzie nie dotykają już kodu, z drugiej mamy wpisy jak ten, gdzie, jak rozumiem, chciałeś przekazać, że AI nic ci nie dało.

Obie narracje nic nie znaczą bez faktycznego kontekstu, w przypadku narracji pro-AI tym kontekstem jest zobaczenie finalnego produktu, który ktoś stworzył, w Twojej narracji kontekstem jest kod jaki masz, problem do rozwiązania i przede wszystkim prompt jaki napisałeś. Bez tego bardzo łatwo przyjąć, że problemem nie był sam Opus, tylko to w jaki sposób zleciłeś mu robotę.

Jak to mawiają entuzjaści AI - musisz spróbować inny prompt bo różne są. O ile sam się z tego śmieję, bo często to czcze gadanie, o tyle jest w tym trochę racji, bo sposób opisania problemu na prawdę robi różnicę, szczególnie w projektach, w których wrzucasz AI do konkretnego zadania bez przedstawienia mu kontekstu projektu - dokładnie tak jakbyś wrzucił mida w nieznany projekt i oczekiwał super rezultatów po godzinie.

Jeśli nie korzystasz, to warto pokombinować z plikami markdown, np. skillsy na prawdę potrafią zrobić robotę - nie mówię, że to jest złote rozwiązanie, które spowoduje, że nagle dany model będzie pisał wszystko bezbłędnie, ale w moim przypadku mega zmniejszyło to halucynacje, do tego wskazywanie przykładów implementacji w projekcie na których może bazować czasem daje dużo więcej niż opisywanie słowami jakiej konwencji ma się trzymać.

Kombinowanie z różnymi podejściami i faktyczne pochylenie się nad promptem, z opisaniem stepami co chciałbyś osiągnąć mi znacząco poprawiło rezultaty, to nie jest tak, że już nie wysyłam do modelu wiadomości "are you on crack" po kilku iteracjach, ale jest ich znacząco mniej 🙌.

[Tomasz Guz @kodemdev]

Wheel slider with animated circular text.
Built with CSS, SVG, and JavaScript (including GSAP).

[Tomasz Guz @kodemdev]

Just dropped a new version of my personal website - building this “circle slider” was a lot of fun.

As always with personal projects, I still see plenty to improve, but it’s good enough to share.

Would love your feedback!

[Tomasz Guz @kodemdev]

@vponamariov to be precise - we can achieve this in pure CSS for a long time using grid-template-rows, which has much more support 🙌.

[Tomasz Guz @kodemdev]

Full article here:
https://t.co/rltvkNHmCr

[Tomasz Guz @kodemdev]

For years, semantic HTML and accessibility used to be "nice to have".

Thanks to AI these things might be more important than ever, and tokens-usage optimized markup may change the game.

🔽 find a full article in reply

[Tomasz Guz @kodemdev]

I completely agree that this is a great property, but just to notice: we can already make similar thing using grid-template-rows transition from 0fr to 1fr. Of course, this approach requires an additional wrapper, but it's also great to make smooth height transition without JS and without defining a fixed maximum height 🙌.

[Tomasz Guz @kodemdev]

Ready-to-use boilerplate available on GitHub:
https://t.co/3pPf5KWDS2

[Tomasz Guz @kodemdev]

"Why do we remove cascading and sheets from Cascading Style Sheets?"

That question led to backstay.rules - a concept for a single, consistent approach to working with SCSS across various projects and stacks.

More below 👇 (links in comments)

[Tomasz Guz @kodemdev]

The full article, along with a description of the rules, can be found here: https://t.co/grCo2Iy9zO

[Tomasz Guz @kodemdev]

Saying we don’t need GSAP’s ScrollTrigger anymore would be clickbait.
But scroll-triggered animations in pure CSS open up huge possibilities.

[Tomasz Guz @kodemdev]

So, to sum up, you felt offended and I am suggesting that you belong to the group of people for whom working directly in CSS is the least pleasant thing.

It's a fact that Tailwind is a godsend for people who find CSS development a chore. Just like the reason for all inventions like CSS in JS. If you don't see that, you've missed a ton of discussions and articles detailing Tailwind's drawbacks. And more importantly, you probably didn't have to deal with the support and development of projects with Tailwind. I recommend finding a few such articles on Medium or Reddit and reading the comments. If this offends you, I apologize. I don't know how you work. I was referring to "many developers," not all.

I still maintain that "the only advantage it offers is the ability to avoid touching CSS files by writing inline styles." I also maintain that I'd love to hear what other, significant reasons you think people choose Tailwind are. And furthermore, for me "built-in design system" sounds like a marketing phrase, which is why I also asked what exactly it means in your opinion and how you use it.

However, I know you won't, and for me, further discussion is pointless.

[Tomasz Guz @kodemdev]

Oh man, I think the problem is more serious judging by the way you speak, so one last time.

I wrote about a problem Bootstrap solved, a problem it no longer has to solve because the world of CSS has moved on. I wrote that Tailwind doesn't solve any such problem, and that's true - it's simply a CSS wrapper with a defined behavior.

After that, you decided that I didn't know Tailwind, and then you wrote that you proved it. How did you prove it? You made an assumption and didn't address what I wrote at all.

I've asked several times what benefits Tailwind offers you, how you understand this design system, and what advantages it gives YOU. What do the docs have to do with this?

This won't change anything in this discussion, but I've used Tailwind, I've used Bootstrap, and I've used many other solutions over the years. I believe I can't have a clear opinion about something and express it publicly if I haven't used it, or have used it incorrectly - as exemplified by, in my opinion, unfair opinions about WordPress (you can read about it here - https://t.co/zGnA9h6BZj).

You talk to much about docs, co this is a quote from Tailwind docs:

"A common reaction to this approach is wondering, “isn’t this just inline styles?” and in some ways it is — you’re applying styles directly to elements instead of assigning them a class name and then styling that class."

So, even in the Tailwind docs you can read that it's inline styling with additional options where you can use breakpoints and refer to variables from within classes, where some variables and layers are already defined for user and ready to adjustment.

Finally, with this attitude you would be a terrible teacher of anything, take a breath and count to ten, because instead of a normal discussion in which you present your opinion, which I may not agree with, but you provide any arguments, you keep playing someone who is better than others, even though you can't prove it in any way.

[Tomasz Guz @kodemdev]

You still didn't answer my questions what exactly it means to you. You write in previous comment "show me your design system" that you can compare with Tailwind. You still think that you are a teacher, and I show lack of knowledge, And I'm demonstrating a lack of knowledge, while comparing Bootstrap to Tailwind, I'm the only one in this discussion who has provided concrete reasons, and I am the only one herewho tries to justify why I think something. You use big words but can't explain what that means to you.

Maybe for you, "built-in design system" means that Tailwind shows you where to define CSS values, has specific class names corresponding to specific CSS values or that it's easiest to operate with multiples of 4.

Maybe, but I don't know, because you don't respond, so it's hard to have a substantive discussion with you, in which you pretend to be smarter than me without even knowing me. I don't expect you to change your mind and answer my questions, so I wish you a nice day.

[Tomasz Guz @kodemdev]

This argument is general, not directed at me personally. I see that if you cannot explain what this design system means to you and what benefits it offers for you, so you stick to one thought and try to play mentor, recognizing that my knowledge is less than yours.

My question was normal, what specific advantages do you get from using Tailwind and what you call its design system, if it is too difficult then the problem is not with me.

btw. the fact that you call tailwind design a system is already bizarre, but maybe you're confusing it with Tailwind Plus, which firstly shows who actually doesn't know Tailwind, and secondly, even Tailwind Plus is not a design system.

[Tomasz Guz @kodemdev]

@diegohaz Agree, it’s solid choice for prototyping or for people who hate writing styles. It’s like jQuery for CSS.

[Tomasz Guz @kodemdev]

I've been waiting for this argument, always the same: if you're criticizing Tailwind, you're either unfamiliar with it or have seen it used incorrectly. So I'd love to hear what the real benefits of this Tailwind design system are, what you think it is, and what its advantages are when used in a custom-designed website or app.

Btw. You can remove unused style also without using Tailwind, but it's always an argument from people who use it, which only shows that it generates a lot of unused styles by default.

[Tomasz Guz @kodemdev]

I think quite the opposite, Bootstrap, unlike Tailwind, was a real problem solver at the time of its greatest popularity, a time before flex, before grid, when you had to use float and reset. Bootstrap provided a simple way to build a layout without worrying about breaking anything. And what advantage does Tailwind offer? The only advantage it offers is the ability to avoid touching CSS files writing inline style, which is the most important feature for many developers, as writing styles is the least enjoyable part of their job.

[Tomasz Guz @kodemdev]

Honestly, I don't think we need to use any "CSS framework" at this time. I prefer a component-oriented approach, clear naming conventions, globally defined values. I personally use SCSS with a few base files (reset, global stuff definition, keyframes), and all other styles are written for a specific component/section/view.