Welcome to Code Chatter, your go-to series for conversational coding insights. What makes this series of questions different from all the others? W...
For further actions, you may consider blocking this person and/or reporting abuse
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
ranggakd / 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
I'm a recruiter and I don't believe in those statistics, github stars, leetscore code,
those are all internet points that don't measure anything meaningful,
they have a very weak correlation with the ability to do the work the company needs her to do.
For me the best way to evaluate a developer is to have a look at the work he does.
Just like the best way to evaluate a musician is to open your ears and listen.
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.
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