rasiim shabazz Profile picture
Jul 10, 2020 โ€ข 10 tweets โ€ข 4 min read
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
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

โ€ข โ€ข โ€ข

Missing some Tweet in this thread? You can try to force a refresh
ใ€€

Keep Current with rasiim shabazz

rasiim shabazz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @refactorfiend

Oct 18, 2020
Domain Driven Design (DDD) made plain broke down to the bone gristle. cus i need that science to level up my code, but miss me with all the stuffy acronyms and jargon. ๐Ÿงต
domain

- the actual problem
- what we're trying to solve with the code for the user
- the set of problems that the users ask the developers to solve
- the subject matter
domain driven

- problem focused
- to stay focused on the actual problem
Read 122 tweets
Oct 17, 2020
switching from management roles to individual contributor roles and still making the same if not more bread is a slept on power move
moral of the story if/when the toxicity and burnout gets to be to much - make lateral moves
with the quickness #manifesto
Read 6 tweets
Sep 30, 2020
How do y'all like to ramp up on new tech?

๐Ÿงต
For me, when the need for a new language, library, framework, shiny thing, etc pops up - i find that i usually take the same general steps

and the 7-bullet list i jotted down in my notes became this thread:
1. pick a language, any language. or framework, library etc.

no tech is perfect. don't sweat it the choice too much. they all have pros and cons - but do try to pick one that has good community adoption so you can get help when you run into blockers
Read 13 tweets
Sep 30, 2020
re: adding code comments with respect to the single responsibility principle

As a #selfDocumentingCode fanatic, I do appreciate that some kinds of comments go a long way:

1/3
One comment/ blurb (1-3 lines):

- at the top of a class about the single responsibility of the class

- in the project readme/wiki about the single responsibility of the application

2/3
Some benefits:

- helps keep the class/application at the appropriate size

- helps make the class/application be easier to understand/work-with

3/3
Read 4 tweets
Sep 30, 2020
phrases never (before tonight) heard in a #PresidentialDebate

"shut up man"
"do you understand what this clown is doing"
"shush for a minute"
"lemme shut you down for a second"
"he's a fool"
"nobody cares"

I feel some more coming on
"you're the worst president evarr"
Read 4 tweets
Sep 28, 2020
"Always implement things when you actually need them,
never when you just foresee that you need them." - Ron Jeffries

i feel attacked ๐Ÿ™„

(over-abstraction is one of my guilty pleasures) ๐Ÿ˜…
like, sometimes i'll take that advice to "code to the interface" to the extreme, just cus i can, and i'll make everything an interface. what you can do with polymorphism and dependency injection is fun ...
but man is it an over-abstraction time suck when trying to just focus on "keeping it simple" KISS minimum viable product. gotta draw the line somewhere and make concrete classes and move forward ...
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(