My approach towards software development has been pretty similar except that my order of priorities is a little different. I prefer: Correct, simple, fast, in

My approach towards software development has been pretty similar except that my order of priorities is a little different. I prefer: Correct, simple, fast, in that order. In other words: - First get a correct solution working that solves the problem correctly for typical as well as corner cases, hopefully with good test coverage for both typical and corner cases. - Then improve the solution to make it simpler while preserving correctness. - Spend time on making it fast when there is actual evidence of performance problems such as data from performance testing with current workload and expected future workloads. The reason why I like to ensure correctness before simplicity is that many times what might seem like a simple solution initially might turn out to be the wrong idea when all corner cases need to be accounted for. Ensuring correctness first requires me to think through the corner cases well and write test cases early during the development phase. With correctness taken care of and protected reasonably well with test cases, it becomes easier to iterate on the solution and increase its simplicity.