Was even thinking to use one declarative structure to additionally also generate the forms.
However I felt it would get too complex and settled with separate definitions that all depend on each other and so are type safe.

Prototype prototypejs.org

It was wild and doing monkey patching the DOM 😱 However it was a huge step ahead at the time, showing that more serious things are possible with JS.

The next hot shit was MooTools and jQuery.

Mui when you need functional components, Tailwind for totally free styling.

I don't think so.

Wouldn't then the interface act exactly like a normal class?

Does it work for you?
I am still struggling. Fixing a specific declaration, all fine. However, using it for designing? … that is another story.

Bonus tip: Avoid ad-hoc guesses — come back later with an informed estimate.

I just remember that display: contents was cool – but not what it actually does 😅

Depends a lot. Is it a proof of concept? Is it internal or external? Is this an attractive target? What can happen in the worst case? How likely is it that suddenly it gets a lot of traffic or would I have time to react?
And I avoid doing anything security by my own, better libs or services.

Why not an already existing idea but in better?

Was thinking lately about a tool that helps with responsive design, breakpoints, etc. but hard to solve 🤔

Don't know your LinkedIn page, but have something to show beside of bootcamp projects. A hobby project, OSS contributions, some freelance or voluntary work.
However more effective is to reach out to people directly.

Uhhhhh, then the waters are getting shallow … maybe with some hidden checkbox with a label wrapper and some
```
#container:has(input[type="checkbox"]:checked) div {
display: block;
}
```
?? However, this is getting experimental 😬

Yes, I expect AI will influence code style. More verbose, non lib, code can even be a plus. Not sure if we are, but at least we feel like we can handle this more of custom code.
It has the benefit that this custom code fits exactly our needs, but carries a higher risk of hidden bugs with edge cases.

Is it the

tag? developer.mozilla.org/en-US/docs/W...

E2-E4 – Early electronic music album, a classic.
Was ear opening to me, to better understand the roots of this genre.
www.youtube.com/watch?v=Vq-k...

I check new technologies only really high level, to get a grip on what is new and when to use it.
Then I wait until I really need it, to then dive in by reading the TOC and pick some interesting parts. Rest is learning on the go, on demand.

uhh, know that game … 😬
what helps me sometimes: going as vanilla as possible 🍦

seems pretty clear by now that scaling & iterating the core large models has hit strongly diminishing returns & the viable paths to true improvement are

a) make the surrounding tools use their context better
b) make smaller models almost as good
c) another transformers-level breakthrough