Technical debt is the implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. That leads to the safe assumption that every software project has already incurred some technical debt, which will subsequently increase the risk and cost of change for an …
The real reflection of intelligence is to create order in the chaos despite of catastrophic environment!
Today I was reading a news about “Spade Hacker”. At that moment I realized that every software company has at least one “spade hacker”. How many “spade hackers” do you have in your company ? 😉
More than three years I was trying to transfer the jidoka approach from Toyota Production System into the software practices. Finally I find my translation, it’s very simple lean principle “Never Fix Later!”. Under the word “fix” I mean wide definition like fix the bug, make the code clean, refactor the code, redesign the code …
Guerilla Tactics in Software Development, Bob Colwell and Taichii Ohno ideas,
Recently I thought on ‘How can I reduce the bugs to minimum ?’
My decision was to execute these steps :
1. Stop and fix the bug if it is serious or log it for a later inspection .
Note : See TPS (Toyota Production System) and why they stop the production line when there is defect.
2. …
Recently I worked on a server side project. And I noticed this snipet below :
public class DBConnection implements Connection {
private DBCConnectionPool pool;
private Connection conn;
public DBCConnection(Connection conn, DBCConnectionPool pool) {
}
}
I was very curious to see the reason for pool reference …
Let’s say “Hi” to all guys , sorry girls we are talking about software you are excluded from this conversation, which will read my first post. I think that every developer will find something from his experience in this post. Many developers face a problem with their managers. I will try to share my observations …