Thread by @refactorfiend

we love complexity so much that we had to make up a "principle" called #KISS that we use to reign ourselves in when we run into problems. why?

- is it that we wanna look smart so we over-engineer shit?
- is it that we dont know the problem well enough to KISS?
- prolly both 🤔

how to be better at KISS?

1) sit down, be humble (Kendrick voice), otherwise at least remember that simplicity is the best flex

2) ask mad questions about the problem ur tryna solve til you understand it so well u cant explain it to a 5 yr old

#codeNewbie #programming

#NowPlaying

we love attempting to predict and prepare for the distant or unpredictable future so much that we had to make up a "principle" called #YAGNI that we use to reign ourselves in when we run into problems. why?

#YAGNI - cus we cant predict the future well enough to not right code that's just gonna end up getting deleted or confusing the shit out of next developer who inherits your code

#programming #codeNewbie

the last of my top 3 quick coding principle gotos:

we love the convenience of making easy-to-reach duplicates every where we go so much that we had to make up a "principle" called #DRY that we use to reign ourselves in when we run into problems smh

why not stop and think for a sec to find a home, a source of truth for the piece of logic or data?

- we're too lazy
- we're too crunched for time
- c'mon it's friday
- we hate coding
- prolly all o the above 😆

how to cultivate a #DRY mindset:

with every code duplicate you write *realize* that you are only giving yourself more work to do when the time comes,

and it will come,

when you need to change that piece of logic in aaallll the 87 places in the code base you left it 😳

and those are my top 3 quick principles 🥉

er best practices or heuristics or whatever ya wanna call em. theyve served many a dev well and continue to do so

just wanted to share. and rant. as i catch up on code reviews to cap off the week 🤓🙌🏾

#programming #softwareDesign

*write code