Honestly, it sounds like the usual clichéd advice.
I was expecting something more practical, like doing an interview every six months or something along those lines.
Supervisors and HR just smile and nod.
Maybe if he had a better relationship with his manager, he would’ve realised sooner that he was just wasting his time.
Documentation is like an untested disaster recovery plan.
When a major issue happens, you’ll be the one called.
You should delegate or automate the task and remove it from your workload, especially if it carries high risk.
I’d actually love to read the dark arts equivalent of this article.
I got frustrated with existing screenshot services choking on cookie banners, rendering half-loaded pages, and serving bloated images. So my co-founder and I built one that auto-dismisses cookie consent dialogs using Playwright heuristics, serves AVIF-first from Cloudflare R2, and supports geo-distributed rendering so you can capture pages as they'd appear from different regions.
Spring Boot + React + PostgreSQL. Bootstrapped after selling a previous ecommerce SaaS.
Currently documenting the whole build in a 30-day series on the blog if anyone's into that sort of thing.
You have link to the blog series?