Lost a bet and switched from Vim to VS Code for a day. Ten minutes into, I found myself editing gitignore in the embedded terminal. Something went wrong.

ANSI is a dying art; but I want it to live.

Now that's a creative hack

Cobol / Mainframe, create on your computer then ftp to server to compile and run (and hope it doesn't crash the cobol region due to infinite running) then ftp to get the output.

Real life automation scripts be like. 😂

Not getting paid on time AGAIN

Kiss your server goodbye until I'm paid i guess

How to get max value of an integer

Bye OSX....hello Ubuntu

When I see windows rant...

Never stop learning new shit.

Boss: Who knows VB?
Me: I once wrote a calculator
Boss: Good enough! You will edit the companies biggest VB Application.

Lesson learned. When your Boss asks if you know a programming language you do not really know, you are like John Snow: Know nothing

When the Dev gets too real.

It's never too late for vim and regex

It went so fast..

Random Guy: So you wrote all this in Java?
Me: JavaScript
Random Guy: Yea. What i said. It's the same!
Me: *triggered*

What advice would I give a new dev?
"Learn COBOL"

No one specified that it had to be 'good advice'

The rule of pi: When giving estimates, multiply your estimate by 3,14.

If you are copy pasting code from somewhere else, spend some time and effort to understand what that piece of code is actually doing, and how much of your requirement does it satisfy.

Stop reading and JUST start writing code.

I've been stuck in coding limbo because I kept looking for the right answer.

And I've learnt over time that the right answer will come to you only when you know what exactly you're looking for.

So start coding.

Reinventing the wheel can be very valuable. Even if you don't create a better wheel, you'll learn a lot about how it works, which can really help you out in the long term.

1. You will write ugly code. Code that is in dire need of refactoring almost immediately.

2. You will write brilliant code. Functions and algorithms that will impress all that use them.

3. 1 & 2 are not mutually exclusive. Good software can be written poorly, beautifully written code can be useless. At the end of the day, just get the job done.

General advice: If you're the smartest person in the room, you're in the wrong room.

learn how to Google properly!
no seriously, learn how to query well its important asf!

To the new devs:
Never push production on friday

Don't get too comfortable.

If your workplace isn't much of a learning environment, it's either time to learn on your own time or leave that workplace.

Don't be arrogant with those who are less tech savy. If your boss/cowoker doesn't understand, at least give them them a chance ☺.

Be kind to new developers who make mistakes; you were in their shoes once.

Realize there's more to life than just designing and implementing software. Don't let other areas of your life suffer just because you're a godly developer.

Which way did the programmer go?
-He went data way.

*cries in corner*

Well Thats Fabulous ...

https://github.com/xviniette/...

Fix hungry developer typo

(commit: https://github.com/NodeRedis/...)

Call your sysadmin today!

(src: http://commitstrip.com/en/2015/...)

QA engineers...