** DONE Blog Series: Design Decisions                                     :blog:software:programming:
CLOSED: [2018-07-24 Tue 20:57]
:PROPERTIES:
:ID: 2018-06-05-bad-design-decisions
:CREATED:  [2018-04-01 Sun 02:46]
:END:
:LOGBOOK:
- State "DONE"       from "NEXT"       [2018-07-24 Tue 20:57]
- Not scheduled, was "[2018-06-09 Sat]" on [2018-06-09 Sat 11:18]
:END:

I am going to write a couple of blog articles with a common pattern:
some design decisions that were made years ago whose negative effects
caused harm, additional effort or bad workarounds that introduced
other side-effects.

The reason I write those articles is not writing a show-off or rant.
It should inform and inspire programmers all over the world to *think
twice* before a design decision is done. To be able to do better, you
have to learn from other peoples mistakes.

I am going to link all articles of that series to this article, so
that you have a starting point for all of them.

- [[id:2018-07-24-executable-guessing][Implicit Command Resolving]]
- [[id:2018-08-04-links][File System Links versus LNK Files]]
- More to come in my pipe-line such as:
  - Drive letters
  - Backslash as path component separation character
  - Renaming commonly known tools
  - (I take suggestions or links to similar sources as well)

-------------

Side-Note: In case you wonder why I don't introduce [[https://karl-voit.at/tags/][a new tag]] for
marking articles of a series, please do read [[id:2019-09-25-no-tags-for-series][this article]].