While I worked at my previous employer, I build a proof of concept to improve their ability to search. I will rebuild that proof of concept and I’ll highlight all the patterns and principles I used to build this code. All code related to this proof of concept can be found in a repository on my Github account.
In this fourth instalment, I want to highlight how I divided the solution in different projects.
Continue reading “Patterns and disciplines from a proof of concept – Part 4”
Trust in a codebase can vary from module to module and is very fragile. I’ll go into more detail of what I mean with trust and how to determine the level of trust you can have in a certain piece of code.
Continue reading “Trusting a codebase”
A good name can be the difference between explaining what a particular part of code does and confuse you. Names also tell you a lot about the quality of the codebase.
Continue reading “Good names are immensely important”