- had an interview going well
- existential crisis kicks in
- fear of being found out to be a fraud and phoney kicks in

This is why I can't have nice things! ¯\_(ツ)_/¯

If songs were codes...

When your GitHub repo gets a star

Advertisement boards at german undergound station.
Thank you windows for the bright blue light down there under ground <3

That's really true.... 😂😂😂😜😜😜

"this"

Here is a beautiful picture of everyone who cares about your opinion on which language is better.

GTFO

If Batman was a full time programmer in Dark Knight, "Bugs are not complicated, Alfred. Just need to figure out why they're after" 😂

You only get three wishes.
I wish for more wishes.
I can't do that. Only three are allowed.
Sudo I wish for more wishes.
OK, here's more wishes!

Debugging...

6666666666666

I'm drunk. And I'm going to code. That's going to be epic:P

Nice try!

When the "lost password" feature of a website sends you an email with your original password :/

I just spent 20m debugging.

Basically bootstrap nav wasn't working. Couldn't understand why not.

Figured out its a an issue with the JS interfering so I remove the script reference from my HTML. Problem solved.

Okay,cool. Now let's add that file back in and figure out what caused the issue.

Hm. This line looks like it might be it *comments it out*...odd. Problem still happens.

*proceed to comment out and test every function to see what could be causing this issue*. Still happens. Fuck it. *comments the entire file out*

what the fucking fuck. I remove the script reference the problem is gone. I remove all code from the script - problem persists.

...wait...are you fucking kidding me. I OPENED THE WRONG JS FILE WITH THE SAME NAME BUT IN A DIFFERNT DIRECTORY.

@dfox Can we have the option to include code blocks in rants and comments? So that they're formatted as monospace text? I mean we can get around it with pictures, but it would be a nice option to include code with an appropriate font. =)

Basically like crossing a minefield.

To all new devs:
- Your language of choice is fine.
- There is no superior way to indent, yours is fine.
- Your IDE is fine.
- Your OS is fine.

Unless you work in my team, of course.

0. Plan before you code. Document everything. You won't remember either your idea or those clever implementations next week (or next month, or next year...).

1. Don't hack your way through, unless that's what you intend to do. Name your variables, functions etc. neatly: autocomplete exists!
Protip: Sometimes you want to check a quick language feature or a piece of code from one of your modules. Resist the urge to quickly hack in the test into your actual project. Maintain a separate file where you can quickly type in and check what you're looking for without hacking on your project (For example, in Python, you can open a new terminal or IDLE window for those quick tests).

2. Keep a quiet environment where you can focus. Recommend listening to something while coding (my latest fad is on asoftmurmur.com). Don't let anything distract you and throw your contextual awareness out of whack.

3. Rubber ducks work. Really. Talking out a complex piece of logic, or that regex or SQL query aids your mind greatly in grasping the concept and clearing the idea. Bounce off code and ideas with a friend or colleague to catch errors and oversights faster. Read more here: https://en.wikipedia.org/wiki/...

4. Since everyone else is saying this (and because it merits saying), USE VERSION CONTROL. Singular most important thing to software development aside from planning and documenting.

5. Remember to flout all of the above once in a while and just make a mess of a project where you have fun throwing everything around all over the place. You'll make mistakes that you never thought were possible by someone of your caliber :) That's how you learn.

Have fun, keep learning!

Notepad++: An update package is available, do you want to download it?

Me: Maybe next time

Notepad++: Sure, that's what they all say