Sade Olutola
Game of Thrones Daily
Peter Solarz
One Nice Bug Per Day
$LAYYYTER
@theartofmadeline
Stranger Things
h
let's talk about Bridgerton tea, my ask is open
祝日 / Permanent Vacation
Monterey Bay Aquarium
Origami Around
TVSTRANGERTHINGS
occasionally subtle
Kaledo Art
pixel skylines
tannertan36
ellievsbear
art blog(derogatory)
wallacepolsom
seen from T1
seen from Indonesia
seen from United Kingdom
seen from United States
seen from Brazil
seen from Malaysia
seen from United States
seen from United States
seen from New Zealand
seen from United States
seen from Singapore
seen from United States
seen from Germany
seen from United States
seen from United States
seen from Malaysia
seen from Finland
seen from Brazil
seen from United States
seen from Brazil
@cleanprogramming-blog
Write down exactly what your function does
Don’t hesitate to write long function names to have a clean code: write “getProductById”, “sendEmailToUsersWhoHaveNotConfirmedYet”, “getSortedListOfKeywordsForProduct”...
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Append types and/or units for your variables
The names of your variables should reflect what they contain and how it can be used; if the name itself isn’t unambiguous, add a suffix to fully explain what’s in there.
You should prefer suffixes because the first letters of your variables should contains the specifics of the variable in order to use your fav IDE autocompletion.
For example, use “keyword” for a string, “keywords” or “keywordsList” for a list of strings (instead of “k”, “listKeywords”...). You can write “quantity” because it’s obviously a positive integer, but you should write “angleInDegrees” instead of “angle”.
Maximum 2 arguments per method
Except some peculiar cases, you should’t have more than 2 defined parameters for each of your functions; this should improve the legibility and usability of your code, as well as simplify tests.
Nested conditional statements - the hard way
switch (false) Â case condition1: manageErrorWithCondition1NotVerified(); break; Â case condition2: manageErrorWithCondition2NotVerified(); break; Â case condition3: manageErrorWithCondition3NotVerified(); break; Â ... Â default: codeWhenAllConditionsAreVerified();
Don’t nest loops and conditional statements more than once
If you have more than 2 levels of indenting, your code starts to become hard to read. You should use refactoring to make smaller portions of code.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Use constants names instead of static values
Replace:
if (time > 3600)
with:
if (time > AN_HOUR_IN_SECONDS)
Replace comments with code
Replace:
// Do something command1 command2 command3
with:
doSomething()
Nested if
if (!condition1) Â Â manageError() Â Â break_or_return
block1
if (!condition2) Â Â manageError() Â Â break_or_return
block2
if (!condition3)...