So this guy is supposed to do the frontend.
I do the backend.
I offer an endpoint.
He does his HTML+CSS magic.
Me: Cool but data is hardcoded. Could you get the data from the endpoint I sent you?
Him: "I'd prefer you do that, I can make a git repo so you download the front."

... So you don't do frontend, you just write pretty layouts. And I have to actually write the frontend logic? Go f yourself.

1) Read the wiki on git. I probably have enough shorthands and test methods that you won't need much other shit to debug issues.

2) when debugging, remember that if it is there, there's a good reason why I put it there.

3) commented-out code is probably useful for maintenance. I left it there for a good reason. 😛

4) chances are whatever I wrote, was the state of the art at the time I wrote it. There might be better ways to do it now tho.

5) I always work modular. First, understand the structure. (probably also documented on wiki) DO NOT fuck up the structure. If you change it, you document it.

6) If you feel I wrote shit, it's probably because management annoyed the living shit out of me. Pun intended.

7) Your confusion is normal. I don't do dumb shit.

Boss asks if the project will be finished today, I reply ‘yes’ and then realised I’d not pushed my code after working from home the previous day! Doh!

Poll: how do you manage Git?
A) CLI
B) GUI

My answer: A
Tally: A:1 B:0

has anyone tried versioning your all the files of operating system, ie git init at root directory ? is that possible? I want to see which file is being changed by which action, but i am guessing it would be very tricky to do so with the usual git