mattkenefick

I'd always been amazed over the years by how many people didn't even attempt CSS. They looked at it like an after thought. Reminds me of a favorite Archer quote: "I thought we skipped that step.", "Skipped a step... in bomb defusal...?"

they probably weight documentation higher

Can't ride my horse and buggy in the city anymore.

For real. It's always a headscratcher when I see these weird takes against it.

Amazon has been working with Anthropic which at the very least will create a much more comprehensive Alexa.

expensive talking fidget spinners

Like Alexa, Siri, and Hey Google? Which are used A LOT and will only be used more when they're natural, smarter, and conversational?

Always a strange take.

Hopefully React and Tailwind usage will fall off

much investment and little return, and no obvious large-scale product-market fit, much less a superintelligence.

I'm always blown away when I see comments like this.

It just makes me think the people that say this either work for a competitor or simply haven't used their products.

The things that OpenAI and similar companies have created are literally revolutionary. It's insane. Pretending it's "little return" is a very strange opinion.

we need more mainstream vehicles challenging the boring design "norms"

I'd argue that we need to start treating cars like the utilitarian objects they are and stop associating our personalities with them.

It's unfortunate how many people misunderstand CSS today and how web applications should be structured.

Articles like this make me sad.

I really can't believe anyone bought one of these devices. It looked terrible right out of the gate.

The sheep/ram was my favorite. Purple horns

Woof. Lots of strong opinions and misinformation in this thread.

backs away slowly

An uncached ChatGPT no-less :D

Not surprising since it's just an Android app

in fashion again!

But it shouldn't be :(

Their manifest v3 enforcements on third-party extensions are problematic. I was trying to update one of my extensions recently that used a Google library (ironically) and had trouble finding a way to allow cousin libraries to be loaded.

It still hasn't been updated because of this.

Correct

Especially since it was a refactoring, it's generally better to handle those in stages if you're working with a team.

There are lot of ways/patterns for solving the same problem... but tearing apart an existing interface being used by others isn't a good start.

The best part about abstraction is that you can modify the underpinnings to be more flexible without hurting the rest. A good step would be to create more flexible math functions underneath, like you're saying, and leave the rest alone.

Afterwards, there can be deeper conversations with the team about how they want the interfaces to communicate to provide an obvious facade but an abstract implementation.

I also made one a week or two ago. This one will swap out the video with an embedded player which generally skips ads.

https://chromewebstore.google.com/detail/nhjphlheoepniijfpao...

Job interviews like this are terrible. It's a shame he's put so many people through it.

I think a lot of it is the major influx of people that joined the industry in the mid-2010s that never had to write code before. They started on fancy UIs so that's what they know.

It bummed me out when modern browsers started supporting mistakes in code; like when Chrome would interpret incorrect markup and fix it for you.

It's unbelievable to me that anyone uses or supports Tailwind. I feel like the internet has taken crazy pills.

Get a new machine

Sounds like you've been surrounded with bad code all your life. This isn't true.

React might be the single worst thing to happen to the web. Not because of the library itself, but what it spawned.. the way people write it.. the style of coding that surrounds it. It was a sad time when it rose to popularity. :(

I think you're underestimating that.

Shame that project went the way that it did. A bit ahead of its time if you ask me. There were a lot of controls that phones just didn't support well enough which complicated the project. It was more of a Cordova or Haxe than an Electron though.

Unbelievably, Haxe is still actively maintained. I keep saying I'll get into it, but I never do.

Try to make it not about the job itself. Reward yourself with other things that are non-code related.

"If I get 5-10 of these done today, I'll reward myself with..."

Or use your imagination in someway like kids do with action figures. It can seem strange but there's ways it less mundane indirectly.

Taking it a little personal, eh?

This is like.. a list of things to avoid doing.