How Complex Systems Fail Permalink
Aja Hammerly gives a tour de force on hiring. The video is packed with good practical advices to improve hiring process of your company, even if you are not ...
Nits are rarely useful, but why do we keep picking them?
It is surprisingly easy to shoot yourself in the foot with equality method in java.
Deliberate practice of going fast is positively different than going slow.
“If only you were given time and space to clean up the worst code, all would improve, right?”
“By definition, a problem that remains entrenched is not “totally fixable” (without a change in context, actors, intent, etc.) On paper it may be fixable. In...
…distance between being expert in this system and being an actual expert in your chosen craft.
What are the things you can do today which make it easier to obtain your desired resources and career opportunities tomorrow, in a way that’s defensible and...
“So if you want them to follow a best practice, put it in their starting templates.”
“We prioritize fad-resilience over speed of adoption.”
It looks trivial to set KPIs but getting best out of KPIs depends on small yet important bits of the process.
Glue work is essential for successful teams but “it is complicated”.
We took an idea too far as an industry.
Fallbacks in your system will cause headaches, sooner or later.
Leverage, leverage, leverage…
I don’t think I have read such a valuable article for a long time. Simple, straightforward, and eye-opening.
A succint zine to extract the best out of 1:1s, by no other than Julia Evans.
This is one of the best essays I have ever read. Pure gold.
… and people were complaining because there was no hope of moving up.
Here’s the dirty secret of teams who ship impact and remove tech debt at the same time: they rarely ask for permission to remove tech debt. Instead, they bun...
As software engineers our job is not to produce code per se, but rather to solve problems.
This blogpost aged like a fine wine. It shaped how I approach to pull requests. It contains one of the most memorable statements I have read: Code review...
An amazing resource to learn ways of working for many well-known companies in software industry.
Joel Spolsky tells us an evolutionary history of character sets and Unicode.