Member-only story
Prepare For A Coding Tech Interview Part 5— DRY, KISS, YAGNI, TDD
Do you want to get a job as a coder / software developer or switch to other company? In this series I’ll share information how to solve coding tasks, how to prepare CV and answers to the most popular interview questions for coding positions to land a new coding job!
Hi! My name is Tom Smykowski. I’ve interviewed hundreds of people and also participated in hundreds of interviews to choose companies I worked for. This gives me an insight into how to win a tech interview
In the previous episodes of the series we went through some low level coding test tasks. Today we’ll explore acronyms you need to know. Last week we learned about SOLID, so now we’ll check out other acronyms:
DRY
Don’t repeat yourself. The principle means that you shouldn’t copy code expressing same functionality. Functions, classes, modules, components, services, abstractions, interfaces and types are at your disposal to encapsulate logic and UI parts.
It doesn’t mean you can’t have same code in different places. However it’s rare, you can have two different features that use similar code, and that’s perfectly ok. When you have to choose between DRY and clear and maintainable code, always choose the latter.
