Duplication may be the root of all evil in software. Many principles and practices have been created for the purpose of controlling or eliminating it. --Uncle Bob
Functions should either do something or answer something, but not both. Either your function should change the state of an object, or it should return some information about that object. Doing both often leads to confusion. -- uncle Bob
Uncle Bob's "The Stepdown Rule":
We want the code to read like a top-down narrative, every function to be followed by those at the next level of abstraction so that we can read the program, descending one level of abstraction at a time as we read down the list of functions.
@CodeerDev, From SketchUp to Blender to Unity to publishing, your journey is truly inspiring for beginners like me, thank you so much for sharing this with the world! https://t.co/wdpm4Jmcvj
One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand. -- reading Clean Code
The name of a variable, function, or class, should answer all the big questions. It should tell you why it exists, what it does, and how it is used. If a name requires a comment, then the name does not reveal its intent. -- uncle Bob
Programming languages are not girlfriends. You can use 2 (or more) at once. There's no need to "move on" in order to use other programming languages: just use them. https://t.co/o4AdZfUmhB
I've been brushing up on my JavaScript skills since my boot camp moved on to React really fast; I found myself being pretty fuzzy on some fundamental concepts during a technical assessment and decided "I will learn, EVERYTHING".
The front end engineer technical assessment from IBM is absolutely demoralizing, I have to walk out of the door and stare at the Charles River for roughly an hour to come back to life.