Everybody wants less bugs in their code but nobody wants to _______.
use #vscode 😅
declare variables right before they'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're used
"refactor towards deeper insight" #ddDesign 🤓😅
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'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
test first, at least after. but test. be test driven
also bears repeating - be kind to your tech stack:
be domain driven
write the code based on solving the users' problem. not based on messing with teh tech
let the code speak the users' terms and concepts, and speak them loud and proud
keep the number of method params at around 3-ish
@UnrollHelper plz unroll
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.
