This post was originally posted on medium. Here I paste it and give it a fresh look in a few places.
Was anyone else ever under impression that principles of software development are a mess?
Continue readingTag: clean code
When it comes to adding complexity to the code, I generally see two schools of programming:
- Top-down: start with abstractions, then write implementations for it.
- Bottom-up: write down the whole implementation, then make abstractions out of it.
This post advicates the second school.
Continue readingA note on the importance of not anticipating future.
As you could read in my initial “Don’t Test…” post, I’m against too many test cases. Here’s another thing you shouldn’t be testing.
Contrary to popular belief, I don’t think you should test as much as possible. I stand by smarter, not more numerous tests. But what makes tests smarter?
In his “Clean code” Uncle Bob univocally condemns boolean arguments.
Recently I’ve come across my Ruby code from 13 months ago. The code regarded my very first task in a project, while I was about to leave the project. Those 13 months were enough to spot right away that the code was, well, bad.
Comments are always failures.
What a perfect example of a wise sentence (by Uncle Bob) that feels wrong when taken out of context.
Recent Comments