$ ls

dogmas that govern our code, database as implementation detail

using markdown for presentations

dogmas that govern our code, zero comments in code

who killed my application?

why architects should code

osv.dev

migrating to jekyll

exceptions, results, and whatnots

code generation and .net

value objects beyond the constraints of your code

i see your primitive and raise you a value object

writing a sorm

implementation vs. project thinking

language enjoyer, go

opinion on code readability, part 2

opinion on code readability, part 1

opinion on nullable collections

dogmas that govern our code, test everything

nullable data

architecture, design patterns, why and why not?

dogmas that govern our code, yagni

dogmas that govern our code, dry

dogmas that govern our code, introduction

abstractions, and why interfaces

monoliths, services (of all sizes), serverless, low code, etc.

investing in yourself

dependencies that you own

code, before writing any

how not to meet

are you still the same person you were x years ago?

balancing innovation, technical debt, and features

thing explainer: complicated stuff in simple words

tell me, how can i improve?

knowledge sharing

craftsmanship, seniority, and paygrades

rules for a new job

developers and ai sidekicks

beyond pi-hole

challenging status quo

my "white" noise

coming soon

$ cat ../contact_information.md

Email: [email protected] and GitHub: D34NM

$ _