e2e tests continue to be underrated. Yes, they are slower to run than unit tests, and usually take longer to write, but a good e2e test lasts forever, no matter how often you change the implementation. It's the only kind of test I want to write anymore. It's worth the extra work.

Many programmers underuse control flow because they associate it with the repetitive "spaghetti code" they wrote as a beginner. So they make things excessively DRY by passing around state (booleans, enums). But state is *the* thing that makes code hard to understand.

The `user-select: all` for making it easier to copy text is such a great idea I only learned recently about. Check it out here -> developer.mozilla.org/en-US/docs/Web…

Yay! 🙂🥱🤯🎉🥳 credly.com/badges/d12fc0f…

My unpopular (?) opinion is that buying in-flight wifi is a mistake. 5-10h flight is a perfect opportunity for an Internet break, actually read that book you always carry in your backpack, to think about the meaning of life, web components etc.

A very good video on the usage of React.useMemo and React.useCallback. Many times, I've seen those abused and used, in my humble opinion, incorrectly. youtube.com/watch?v=huBxer…

A wealth of knowledge about JS event loop -> blog.frontend-almanac.com/event-loop-myt…

Give yourself a favor and read through this excellent resource by Ahmad Shadeed a read. defensivecss.dev

First day at Runway today, onward 🚀

If you use Playwright for tests, do yourself a favor and wrap your expects / actions with `test.step`. This way, you will make the test output more readable, especially while reading the steps in the "UI mode". playwright.dev/docs/api/class…

🌶️ *every* JS/TS function that takes more than one argument should take an object instead Better IDE support, code completion and you’ll never screw up the order of arguments

*eye twitch*

This tip is pure gold epicweb.dev/inverse-assert… Seemingly so "simple", yet something I could not find a good way of doing until now. Thank you, Artem Zakharchenko, for sharing.

Isn't it funny, how day by day nothing changes but, when we look back, everything is different.

vibe coding, where 2 engineers can now create the tech debt of at least 50 engineers

I spent 45 minutes today to learn Go. I know Go now. I can see the appeal.

Rare picture of two founders vibe coding their product

At this point, what am I supposed to do? No matter how hard I try, AI won't listen to me sometimes.

Can’t wait to see these “memories”: - since 12/7 user created 57 commits named “CI fix” and 23 “lint fix” - user likes to refer to me as “moron” or “idiot” (the feeling is mutual) - based on commit messages, user thinks he’s a “Sisyphus”, should I call authorities?