Interesting talk about management and why it's hard. It touches upon problem solving and why we fail at it. In short we often look at symptoms and not problems. To make things worse we often try to solve them at the wrong place out of sheer ignorance.

It's also a very humble talk which I always appreciate.

Where we're reminded that the stacking contexts with CSS is not tied to the DOM tree... Yay for making complicated rules which means you'll create such stacking contexts unexpectedly. This article comes with a couple of nice tricks to make things easier though like the isolation property. The CSS Stacking Context Inspector browser extension is good too.

I'm on that social media for work reason, still oh boy... how much I hate it. This article pretty much summarizes why.

After the denoiser of raytracing images from Nvidia, here is a neural network approach from Intel to make game output photorealistic. Using the G-buffers as input is particularly clever.

In my question for simpler web frontends, this looks like an interesting library. It's built on Custom Elements (part of the Web Components effort) and is just a tiny bit of Javascript. Sounds neat and tidy.

I think this piece is getting quite a few points right. The SPA for everything trend rubs me the wrong way at least. As usual: use the right tool for the job.

Looks like an interesting alternative to three point estimates. Indeed it feels a bit more complex at first but in practice it might require less discipline than three point estimates. Often three point estimates can devolve into forced distribution for tasks. I have already seen enough time cases where most likely is always say twice the optimistic case, and pessimistic four times the optimistic case for all tasks. By forcing to explicitly treat the uncertainty as a separate metric it's seems less error prone.

Another way to get into "carpe diem" mode I guess. :-)

If you still wonder how ads work on the web and on mobile, this thread summarizes it well. They just farm us.

Interestingly, I'm going through this book right now and indeed I have to agree with most of this article. It didn't age well, it's become a mix of nice advises, things which are kind of obvious nowadays and points which are clearly obsolete. I find that "The Clean Coder" (different topic I know) aged way better. I think I'll give a shot to the proposed alternative book to see...

Interesting article about tracing, especially on the client side and how to correlate it with the server side tracing.

Important advocacy, the right to repair has to become huge in the coming years.

Interesting art form, I didn't know about it. This is fascinating how an activity so humble can be turned into something seeking some sort of perfection.

Looks like an interesting engine for offline intent recognition.

Looks like a very comprehensive course about CSS.

I got a slightly different view on the topic. To me there's value in the process of estimating, the estimation itself less so. The process often helps you refine both your understanding of the technical domain but also of the business domain.

Not that I needed to be convinced, but it's now becoming clear 3D engines are getting out of games to become more pervasive.

This is Rust focused but still, shows a good way to increase binary portability across distributions. I suspect a couple of things would be easier with elf-dissector even.

Very nice tutorial, explores a good set of common biases. Also show that it's not that simple to get rid of them.

OK, now that's a funny consequence of how authorities behave which are taken into account by criminals.