fundamentals

32 posts
career

Free ebook: An engineer’s guide to getting more recognition at work

Know what is effective work. Define your priorities. Deliver on time. Assess yourself honestly. Help your peers. Understand your manager's priorities. Get a mentor. Document what you do. Ask for explicit feedback. Talk to your manager regularly.…

Issue59

Functional lessons learnt

Respect the purity of the functions. Focus on the order of parameters to increase the readability of your code.…

Issue58

Finding the time to refactor

Make refactoring integral to every work schedule. Take a few minutes to clean up code, as soon as tests pass, with better names and extracting private methods and classes, etc.…

Issue58

Why consistency is one of the top indicators of good code

Consistency in code allows you to make accurate assumptions and predictions about its behaviour and implementation.…

Issue56

What makes code bad?

Remove unreachable code, code that doesn’t do anything and code that was put to set up for future features that never materialised.…

Issue55

Five habits that help code quality

Keep coupling to a minimum. Apply the Principle of Least Astonishment. Minimise cyclomatic complexity…

Issue55

Refactoring is about features

Always refactor in the service of a feature. Find code that is frequently being worked on. Try to refactor that code.…

Issue52

Back-end performance, those metrics we should care about

There is a strong correlation between throughput and latency in a performance test. Latency increases with the growth of throughput.…

Issue48

“Don’t deploy on Friday” and 3 other “unwritten rules” of software engineering

Even if you have continuous deployment, Fridays are the worst day to push to master. Wait for complete specs before you begin a build.…

Issue45

Slow down to go faster

Invest time to think about what you want to achieve while things are still simple. This way, you will not be thrown off track by complexity later.…