How Complex Systems Fail Permalink
Posts by Tag
- link 26
- ways of working 16
- management 7
- career 5
- tech debt 3
- engineering 3
- unicode 1
- documentation 1
- meetings 1
- distributed systems 1
- java 1
- software engineering 1
- hiring 1
- video 1
- software 1
link
Stop nitpicking in code reviews Permalink
Nits are rarely useful, but why do we keep picking them?
How to write an equality method in java Permalink
It is surprisingly easy to shoot yourself in the foot with equality method in java.
Fulfilling the promise of CI/CD Permalink
Deliberate practice of going fast is positively different than going slow.
Building realistic roadmaps for tech debt cleanup Permalink
“If only you were given time and space to clean up the worst code, all would improve, right?”
The patient change agent Permalink
“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...
Questionable advice: The trap of the premature senior Permalink
…distance between being expert in this system and being an actual expert in your chosen craft.
See your career as a product Permalink
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...
Driving cultural change through software choices Permalink
“So if you want them to follow a best practice, put it in their starting templates.”
How big technical changes happen at Slack Permalink
“We prioritize fad-resilience over speed of adoption.”
How to measure and improve success in your engineering team Permalink
It looks trivial to set KPIs but getting best out of KPIs depends on small yet important bits of the process.
Technical leadership and glue work Permalink
Glue work is essential for successful teams but “it is complicated”.
Independence, autonomy and too many small teams Permalink
We took an idea too far as an industry.
Avoiding fallback in distributed systems Permalink
Fallbacks in your system will cause headaches, sooner or later.
What SV gets right on software engineers Permalink
Leverage, leverage, leverage…
A primer on engineering delivery metrics Permalink
I don’t think I have read such a valuable article for a long time. Simple, straightforward, and eye-opening.
What to talk about in 1:1s Permalink
A succint zine to extract the best out of 1:1s, by no other than Julia Evans.
Salary negotiation Permalink
This is one of the best essays I have ever read. Pure gold.
Command and conquer and the herd of coconuts Permalink
… and people were complaining because there was no hope of moving up.
Tech debt and the pragmatic middle ground Permalink
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...
Design docs at Google Permalink
As software engineers our job is not to produce code per se, but rather to solve problems.
How about code reviews? Permalink
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...
What it’s like to be a developer at… Permalink
An amazing resource to learn ways of working for many well-known companies in software industry.
Unicode and character sets Permalink
Joel Spolsky tells us an evolutionary history of character sets and Unicode.
ways of working
Stop nitpicking in code reviews Permalink
Nits are rarely useful, but why do we keep picking them?
Fulfilling the promise of CI/CD Permalink
Deliberate practice of going fast is positively different than going slow.
Building realistic roadmaps for tech debt cleanup Permalink
“If only you were given time and space to clean up the worst code, all would improve, right?”
Driving cultural change through software choices Permalink
“So if you want them to follow a best practice, put it in their starting templates.”
How big technical changes happen at Slack Permalink
“We prioritize fad-resilience over speed of adoption.”
How to measure and improve success in your engineering team Permalink
It looks trivial to set KPIs but getting best out of KPIs depends on small yet important bits of the process.
Independence, autonomy and too many small teams Permalink
We took an idea too far as an industry.
What SV gets right on software engineers Permalink
Leverage, leverage, leverage…
A primer on engineering delivery metrics Permalink
I don’t think I have read such a valuable article for a long time. Simple, straightforward, and eye-opening.
What to talk about in 1:1s Permalink
A succint zine to extract the best out of 1:1s, by no other than Julia Evans.
Command and conquer and the herd of coconuts Permalink
… and people were complaining because there was no hope of moving up.
Tech debt and the pragmatic middle ground Permalink
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...
Design docs at Google Permalink
As software engineers our job is not to produce code per se, but rather to solve problems.
How about code reviews? Permalink
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...
What it’s like to be a developer at… Permalink
An amazing resource to learn ways of working for many well-known companies in software industry.
management
Driving cultural change through software choices Permalink
“So if you want them to follow a best practice, put it in their starting templates.”
How to measure and improve success in your engineering team Permalink
It looks trivial to set KPIs but getting best out of KPIs depends on small yet important bits of the process.
Technical leadership and glue work Permalink
Glue work is essential for successful teams but “it is complicated”.
Independence, autonomy and too many small teams Permalink
We took an idea too far as an industry.
What SV gets right on software engineers Permalink
Leverage, leverage, leverage…
A primer on engineering delivery metrics Permalink
I don’t think I have read such a valuable article for a long time. Simple, straightforward, and eye-opening.
Command and conquer and the herd of coconuts Permalink
… and people were complaining because there was no hope of moving up.
career
The patient change agent Permalink
“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...
Questionable advice: The trap of the premature senior Permalink
…distance between being expert in this system and being an actual expert in your chosen craft.
See your career as a product Permalink
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...
Salary negotiation Permalink
This is one of the best essays I have ever read. Pure gold.
tech debt
Building realistic roadmaps for tech debt cleanup Permalink
“If only you were given time and space to clean up the worst code, all would improve, right?”
Tech debt and the pragmatic middle ground Permalink
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...
engineering
Fulfilling the promise of CI/CD Permalink
Deliberate practice of going fast is positively different than going slow.
Building realistic roadmaps for tech debt cleanup Permalink
“If only you were given time and space to clean up the worst code, all would improve, right?”
unicode
Unicode and character sets Permalink
Joel Spolsky tells us an evolutionary history of character sets and Unicode.
documentation
Design docs at Google Permalink
As software engineers our job is not to produce code per se, but rather to solve problems.
meetings
What to talk about in 1:1s Permalink
A succint zine to extract the best out of 1:1s, by no other than Julia Evans.
distributed systems
Avoiding fallback in distributed systems Permalink
Fallbacks in your system will cause headaches, sooner or later.
java
How to write an equality method in java Permalink
It is surprisingly easy to shoot yourself in the foot with equality method in java.
software engineering
Stop nitpicking in code reviews Permalink
Nits are rarely useful, but why do we keep picking them?
hiring
Hiring is Not Hazing by Aja Hammerly
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 ...
video
Hiring is Not Hazing by Aja Hammerly
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 ...