Tech writer with 701K+ views. Sharing my opinion and what I learn. Danish C# backend engineer in FinTech. Ex Big4 senior tech consultant.

BETTER SOFTWARE DESIGN

The art of turning 6 lines into 92 lines by replacing if-then-else and switch with objects — for the better.

Image for post
Image for post
Credit: the author


PROGRAMMING

Talking about If-else vs. Polymorphism is one way.

Image by Nicklas Millard
Image by Nicklas Millard
Image by Nicklas Millard


Opinionated Perspective

And lots of them. So, stop boasting about how self-documenting your code is.

Image by Nicklas Millard
Image by Nicklas Millard
Image by Nicklas Millard


Opinionated Perspective

There’s possibly nothing that has caused more developer-headaches than poor method declarations…

Image by Nicklas Millard
Image by Nicklas Millard
Image by Nicklas Millard


PRACTICAL DESIGN PATTERNS

How to improve from traditional branching and understanding how the strategy pattern brings down cyclomatic complexity.

Illustration by Nicklas Millard
Illustration by Nicklas Millard
Illustration by Nicklas Millard


OPINIONATED PERSPECTIVE

Resulting in pain-inducing constructor bloat and incomprehensive object graphs.

Feature image of an object graph.
Feature image of an object graph.
Image by Nicklas Millard


PRACTICAL PROGRAMMING TIPS

Not all code is created equal. And sometimes, garbage code is sufficient code.

Image by the Author
Image by the Author
Image by the Author


BETTER SOFTWARE DESIGN

How to easily replace if-else statements. And no, a switch is not a suitable substitute.

Image for post
Image for post


Crafting great software is about focusing your attention on what matters at the right time

Image for post
Image for post
Photo by the author.

“Make it work, make it better, make it faster.”


It’s easy to refactor messy code once you follow a few simple guidelines

Image for post
Image for post
Photo by the author.

12 Heuristics for Beginners to Become Refactoring Experts

  1. Is your class’ list of parameters starting to grow too big? Then it’s likely doing too much. Its responsibilities are unclear and perhaps painful to test and debug. It’s a prime candidate for refactoring.
  2. Do you have methods inside classes that only use one of the class dependencies? You better pull that method into a class of its own — even if that class will only consist of a single method. …

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store