![]() ![]() There are still typos that slip through the net though a famous example is = vs. An extreme example is the Haskell programming language - Haskell programmers often claim, half-jokingly, that once a Haskell program compiles, it is usually correct and bug-free. A language with strict static typing and a compilation step in the build process will catch most typos the stricter the language, the higher the chance of a typo causing invalid syntax. ![]() What's the best way to avoid such a scenario or, in other words, how can I review my own code before someone else does?Įdit: I use Notepad++ for PHP, please don't ask me to change the IDE right-away however, suggestions are welcome if they are persuasive ) ![]() And I agree that many times I am in a hurry to submit the change only to get the work done faster.īut, besides wasting reviewers' time, this actually slows down the development process and reduces my credibility (small errors may even hide praise for good work). I do run unit tests, but sometime they miss these errors (we have incomplete test coverage right now). But many times I make silly typo errors and errors of other kind while making a change in the code.įor example, the last time when I refactored some old code I moved code from one class to another, but forgot to check that $this only worked in the old class and needed to be changed now. I understand reviewing work isn't an easy task, so I don't like to waste reviewers' time and effort. For the first time I have been coding for an open-source software where all my work gets reviewed before being commited. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |