A dev, a pianist, a teacher, a lifelong learner. Can debug code and piano scales ✨
Joined August 2013
- Tweets251
- Following57
- Followers44
- Likes169
Jun retweeted
You need both taste and judgement. You need taste to know what is good, and you need judgement to understand the price of quality.
If you ask a model for a component or migration plan, it will create a lot of options, very quickly. Most of those drafts seem OK. So once you have a collection of work that meets the basic criteria, you can no longer use taste to select between them. You must choose.
I like to think of this as two filters. There is the taste, and there is the judgement. And I think a lot of people mix those up.
The first filter is taste. Taste is the feeling for what makes a thing good.
Taste is that feeling you get first, before you're able to put into words what is good or bad about something. You've had that experience where something is bad but you're not sure why, until you've worked it through and can describe it. "This user experience was really clumsy" or "that error message was really aggravating." Taste is built up by experience and practice.
It comes from looking at a lot of things, and making a lot of things, and remembering the good bits. Kant's great insight into aesthetic taste was that you could appreciate the form, without having a stake in the outcome. Engineers care about the outcomes much more than the forms, but the feeling is the same.
Taste can disqualify a lot. It can disqualify 90% of drafts very quickly. But it's not enough to make a decision between the few remaining options.
The second filter is judgement. Judgement is understanding the price of quality. The most perfect solution may not be finished by the time that you need it. The sanest architecture may require the users to migrate while you're in the middle of the final upgrade.
Judgement is the understanding of what you give up in time and risk to get good things, for the sake of the users, for the sake of the team. Judgement is made from domain knowledge and experience from previous decisions.
People with great taste but poor judgement make beautiful work too late. They make the right thing at the wrong time, or the wrong thing at the right time. People with judgement but no taste make on time but don't make things people love.
Both taste and judgement are essential. Filter to a few options with taste, and filter to one option for delivery with judgement.
Jun retweeted
This is insane 🤯
Grok 3 just wrote out an extremely detailed 6-mo SEO plan for a brand pressure washing business in Tokyo starting from scratch (did this as a test for a friend)
The amount of detail is crazy 🤩
Check it out 👇🏻
xitter.gq/i/grok/share/tLmgMyOhZ…
Jun retweeted
Windsurf just announced Wave 3.
It takes AI coding to a whole new level with so many incredible features.
8 wild examples:
Jun retweeted
Really great article on React Query by @uidotdev ui.dev/why-react-query
Jun retweeted
Tech people!
I'd like to you to turn your attention to this interview with @unclebobmartin by @ThePrimeagen
This is a good interview.
I really like how UnclueBob adds more colour to the whys behind his guidance when it comes to clean code.
I like especially that part when Prime says that abstractions make a flow hard to comprehend because too many things you have to keep in your mind.
UncleBob says, how the abstraction is done is wrong in this case. From this it is clear that the meaning for another human is important. It also opens another thousand can of worms as human communication is everything but not stable meaning.
All in all. The interview is good and the insights we get is great.
Thanks for both of them for this interview.
youtu.be/UBXXw2JSloo
Jun retweeted
Whether you like this or not, we can all agree that JSON files are a terrible format for configs, right?
Jun retweeted
AI is not going to take your job any time soon
AI is going to likely make your job harder for a while (that mf devin is going to wreck codebases)
Jun retweeted
CSS Trick ✨
You can create this glitch hover effect by animating pseudoelement content 🎬
button:hover span:after {
animation: flip 0.2s calc(var(--i) * 0.05s);
}
@keyframes flip {
20% { content: '_'; }
40% { content: var(--c1); }
60% { content: var(--c2); }
}
It's a funky little track that allows you to animate text flipping with CSS 🤙
Leaning into custom properties, you can make each flip animation random with inline styles 🎨
<button>
<span
style="--i: 0; --c1: 'x'; --c2: '$'; --c3: '≈';"
>C</span>
<span
style="--i: 1; --c1: 'ç'; --c2: '&'; --c3: 'π';"
>l</span>
<!-- Other characters -->
<span class="sr-only">Click Me</span>
</button>
You make use of each character within the keyframes above. And "--i" communicates the index that you can use for the animation-delay 🙌
That's all there is to it!
As always, any requests or suggestions, hit me up! 🙏
@CodePen link below! 👇
Jun retweeted
try it out on musicfy.lol
