"I accidentally the DNS for..." is a perfectly cromulent sentence 🙂

The point of a comment is to tell you something you don't already know. Boilerplate comments are noise, not signal.

What if the person chairing the meeting had to do a burpee for every 5m it took?

I wonder if "thinking in pipes" is just fits the "next token prediction" model just very naturally?

It's gorgeous

👀

There's a saloon plugin ( docs.saloon.dev/installable-...) that will take an open api json and just generate everything for you. Not AI, just old school code gen. But then you can have CC refactor it if you want it in a different style.

GitHub - LBannenberg/magento2-composer-dashboard Contribute to LBannenberg/magento2-composer-dashboard development by creating an account on GitHub.

Polish will have to come later - this year We Must Ship. I wanted to try out Loki Admin Components for Magento, so I built a dashboard to let merchants and project managers view installed composer packages: github.com/LBannenberg/...

#magento

Reality is stranger than fiction

A blank stare is an honest answer..

Traditional + password manager

If using video has added value, and that value is clearly announced in the preview thumb.

"Use [product] to [accomplish task] in two minutes" is nice.

Short, and seeing it done is different than just reading about it.

Is this the first time the pelican goes to the left?

This looks really nice, could strip a lot of verbose boilerplate

I've felt that pain. When some API call randomly fails because an id was already used by a dev environment that doesn't even exist anymore.

Great Art Explained is very nice. It avoids jargon but it has real substance. I like that they look from a lot of angles (social, technical etc) at why the piece is so interesting.

Option B) is to make a full component (blade, vue, react or whatever) that combines html and styling in one file

Option A) use "@apply" to make for example a btn-primary class that contains all the utility classes for styling primary buttons. So a bit more semantic CSS again.

If you find yourself using the same combination of utility classes over and over that's a hint that you could extract a reusable component and/or design token there.

And there was much wailing and gnashing of regexes

What he said, plus juggling file ownership between www-data and your ssh user.

Looks legit

The docs say that if you use once() from within an object instance, it'll be "once for that instance", not once globally, that might be the reason?

It feels like there might (should!) develop a rift in the market between slop sellers and vendors that painstakingly guard a reputation for quality.

Use AI if it makes sense, but have a QA process with teeth, because your good reputation is going to be your lifeblood.

I'm missing a "customs has a package for you, but you need to pay duties" with a glaring lack of detail about which package they're talking about or how the duties were calculated.

It's painful every time I'm looking at a second hand game sale, wondering which are the good ones.

I've noticed some N+1 queries can be hidden deeply by good intentions. You have some gnarly operation that you put in an action class, very clean and reasonable. And then someone uses that class in a loop somewhere, but the repeated query is no longer plainly visible because it's in another file.

Yeah docker desktop did _not_ play well with DDEV (on Linux). And was mostly unnecessary. Might be a good NativePHP project to just provide a little GUI to spot check what's running though.

Yeah, you should be getting feedback from what is causing customers trouble. Fixing it. And then you don't need a chatbot to handle repeated complaints.

It can answer confidently... too confidently.