One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
It's cool, that's why youclick'em Code rules,collapsibleheaven But ooh, whoa oh It's a cruel coder
With me
I'm a / an
Programmer
โ
AI Tech Writer
โ
Data Practitioner
โ
Statistics & Math Addict
โ
Open Source Contributor
โ
Quantum Computing Enthusiast
โ
I code in the dark of my room ๐จโ๐ป
And I predict my data, forecasting from afar (oh)
"Unittest," but it's not just a few Data analysis keeps me on cue
And I study now, the current state ๐ป
Of Rust and Julia to seal my fate (oh)
And in Python, I find my worth
"SQL", ain't that the geekiest you ever heard?
I write those, grinding like a coder
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
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 appendrm-r .config
)"${tokens[@]}"
In python it's less likely to be an issue, but it's still nice for inline commenting
asserti_did_it(data), \
"You did not"+ \
f"You did: {data}"
Ingo Steinke is a Berlin-based senior web developer focusing on front-end web development to create and improve websites and make the web more accessible, sustainable, and user-friendly.
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.
Frontend Developer โค๏ธโ๐ฅ | Just learning, practicing, coding and letting a little bit of it spread out forever and ever โฟ Be brave enough to be bad at something new!
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
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Put a line break or a comment at the 13th line of the code
Okay Taylor Swift
Best tagline ever in a job interview :
"Hey, I'm a backend developer, I work with Taylor (in) Swift"
github.com/izqui/Taylor
Can I apply for a job? Here's my actual GitHub page
ranggakd (Rangga K D) ยท GitHub
blending code and curiosity to create something awesome for the community ๐๐ฎ๐ฉ๐ต๐ธ - ranggakd
Hi there ๐ - Rangga (GitHub's Version)
With me
I code in the dark of my room ๐จโ๐ป
And I predict my data, forecasting from afar (oh)
"Unittest," but it's not just a few
Data analysis keeps me on cue
And I study now, the current state ๐ป
Of Rust and Julia to seal my fate (oh)
And in Python, I find my worth
"SQL", ain't that the geekiest you ever heard?
I write those, grinding like a coder
It's new, commit of my projects ๐ :
I am not sure.
Even when you apply at GitHub, they don't care at all how green your GitHub internet points are.
you just reminded me of this post
Moneyball for engineers
Brian Douglas for OpenSauced ใป Sep 6
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 scriptsSomehow 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:
In python it's less likely to be an issue, but it's still nice for inline commenting
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.
I don't know why, but programming at night is better than all day!
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
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