my ordinary day

few things that people should know 1. Writing procedural code in an object oriented langauge does not make it an object oriented program magically. 2. coding progress is not measured by the number of lines written, nor is it inversely related to the number of lines written. With more lines code is bloated and specific purpose of routines/methods is blurred or multitudineous. With less lines but still no division of responsibilities the code is difficult to read and maintain. 3. fixing a bug with no investigation into the cause is the same as applying a plaster to something, yes it stops the bleeding for now but whatever was causing it may lead to death in the mean time. 4. when using an api I should not need to know the inner workings of its implementation, it should be as a simple box that answers my questions. 5. there is good laziness and bad laziness. Good laziness leads to automation and tools being created to make work easier. Bad laziness leads to no units tests, sloppy code and having to repeatedly perform the same operation time after time when it could be automated. 6. situations don't just improve, without someone willing to fix problems they will exist forever. 7. knowing a language syntax does not mean you are a good developer. You can be a good developer, able to see what conditions should exist, what things should be checked for and how something should work without even knowing a programming language UML is often enough. 8. experience teaches a developer, regardless of academic qualifications, experience is what truly matters.