Got Coding Superstitions?🤞

Put a line break or a comment at the 13th line of the code

clean + restart visual studio + rebuild solution

and if it doesn't work you restart your laptop/pc before rebuilding

🙈

Don't use backslashes \ to split lines - especially in shell scripts

# actually remove old settings before redeploying, else it will append
ssh user@host \
    rm -r .config

Somehow I got bitten by that once where the character after backslash became inline whitespace and caused a hard to find bug with the second part becoming a new statement on a new line.

Using parentheses usually gets us out of r trouble, and allows more granular commenting:

tokens=(
    ssh user@host
    # actually remove old settings before redeploying, else it will append
    rm -r .config
)
"${tokens[@]}"

In python it's less likely to be an issue, but it's still nice for inline commenting

assert i_did_it(data), \
    "You did not" + \
    f"You did: {data}"

assert i_did_it(data), (
    # Admonish programmer
    "You did not"
    # Highlight irregularity
    f"You did: {data}"
)

Only slightly related to coding, but similar to some people striving for a green GitHub activity graph, I used to believe that it's important or helpful to have a high reputation on StackOverflow.

Certainly! It's always fun to hear about coding superstitions and rituals. Personally, I have a "lucky" rubber duck on my desk. Whenever I'm stuck on a coding problem, I explain it to the duck, and more often than not, I end up finding raposo frp apk the solution while talking it out. 🦆😄 #CodingSuperstitions

I don't know why, but programming at night is better than all day!

I’m not superstitious, but I am a little bit stitious.

ALWAYS DO THE MOST FUNCTIONAL PARTS AT THE END. DESIGN FIRST, MECHANICS LATER

I always kind of want finish the simple task first and then proceeding to the complex ones.

Backups : My superstition is that I still assume that they will work when I need them, despite history having proven otherwise