Last part about estimates. Plenty of very good advises again on how to deal not meeting a deadline. Communicating the bad news early is key.
AST tooling is great for porting code and code quality checks. Here are a couple of examples in python.
Very interesting deep dive into conditional HTTP requests. It fully covers ETag and Last-Modified.
Another nice piece about estimates. This time for the tough times when you're asked a quick ballpark number. The best piece of advises in there: know when you shouldn't do it at all, and, if you go for it sound vague.
I'd even add "you can never be to vague". Even if you go for "a few weeks, maybe two or three" very often people here "two weeks". Don't hesitate to hammer down the uncertainty in all this.
More on the test pyramid debate... As usual looking at the history of a concept and carefully evaluating how things are named is very enlightening. This is a must read.
Very sensible and simple advises on how to do logging in your application. Just lacks a bit a discussion on how to use the different log levels.
Lots of good ideas on how to use docker-compose in development vs in production. Very web app oriented as the title imply but contains a few nuggets which make sense for desktop or embedded use as well.
I've been banging the testing drum for so long I'd have a hard time to not violently agree with that article. I have a couple of beefs with it though, like the sacrificing encapsulation point but other than that...
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.
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.
Looks like an interesting engine for offline intent recognition.