Read on Twitter
Everybody wants less bugs in their code but nobody wants to _______.
use #vscode 
https://abs.twimg.com/emoji/v2/... draggable="false" alt="😅" title="Lächelndes Gesicht mit offenem Mund und Angstschweiß" aria-label="Emoji: Lächelndes Gesicht mit offenem Mund und Angstschweiß">
declare variables right before they& #39;re used
keep methods short and sweet
read the docs first. well, at least some of it
name your classes well. cmon now with meaning!
name your methods even better
make a class do just one thing. no multitasking ish
declare variables right before they& #39;re used
"refactor towards deeper insight" #ddDesign https://abs.twimg.com/emoji/v2/... draggable="false" alt="🤓" title="Nerd-Gesicht" aria-label="Emoji: Nerd-Gesicht">https://abs.twimg.com/emoji/v2/... draggable="false" alt="😅" title="Lächelndes Gesicht mit offenem Mund und Angstschweiß" aria-label="Emoji: Lächelndes Gesicht mit offenem Mund und Angstschweiß">
add behavior (methods other that getters and setters) to objects, not just fields
rebuke anemic domain models. unless you have to use em
think twice about deeply nested loops and ifs. use em if u need to. just think twice is all
refactor methods that take too many params (if you gotta ask if it& #39;s too many, it is)
read that book "domain driven design", aka the blue book
think before you code. measure twice cut once.
ask ask ask mad questions to clarify the requirements
