I was finally able to fix this other persons code when I accepted the fact that they don’t know what the fuck they’re doing

When I tried to start a company and failed miserably. MVP was shit. Much harder to build a decent web app than I anticipated.

Hope I die in my sleep tonight. I hate my career!

Me finding bugs in someone else’s undocumented code before the author does:

Coworker was adversarial from the get. He would always bully me by saying “You better do [BLANK]!” whenever we’d discuss tasks to be done. He eventually pushed my buttons too many times. I responded to his bullying tactic by yelling back, “IF I DON’T, WHAT ARE YOU GOING TO DO ABOUT IT!? Stop bullying me and let’s work TOGETHER on this!” I realize now he was fucking with my head.

Engineers realize paying it forward is just as important to career progression than glamorous features completed

Key to long term career survival as a developer: learn to ABI (Always Be Interviewing).

You should be able to sue a company for having to work for their sociopathic managers just like you can sue them for forcing you to work in hazardous conditions. Both are harmful!

What do VPs say to justify a shitty product: “The competition is _just_ good at marketing.” 😆😆😆

Data Science: that thing you call yourself to make more money when being a good SWE isn’t doing it.

Wish I would have tried harder at becoming a sports star. Society more readily accepts African American jocks than they do their African American geeks.

Some days you’re excelling and thriving. But some days you take pleasure in eating shit, because you have no other choice.

Deciding to work in technology was one of the worst decisions I made in life. But I won’t kill myself.

I’m a career failure and I think it’s better if I died.

Working at FB sucks. Managers talk make-believe . Gratuitous use of made up acronyms. Chaos chaos fucking chaos. I’m there only to pay my over priced rent.

Old school SUSE Linux sticker

My set up in March, 2003.

On the desk: Titanium PowerBook G4 1Gz
On the floor: custom-built PC running my email and web server on SUSE Linux

When you find that boneheaded bug in your boss’ code who’s always talking like he know everything

My 18-year-old Logitech USB mouse (back when they were making mouses in Mexico) must’ve known that I was going to e-waste it today. I set it down on my table and then went back to grab it and the little fucker scurried away.

p4 add <new file>
cp <old file> <new file>
p4 delete <old file>
p4 submit

That how you tell someone “GO TO HELL!” in perforce commands.

What’s an adequate amount of lead time for a code freeze notice. I was asked to update some code I was not responsible for. The updates will take about 2 weeks. A few days after being assigned I get a notice of the code freeze :/

Note to self: never use gdb commands as variables in my program.

When they use up 2TB of disk space with useless information that kills your jobs for the 10th time!

Management fixes our slow running buggy code problem by exactly copying every file into separate version control depots so that Dept A does have to deal with Dept B bugs and Dept B does have to deal with Dept A bugs to the same files.

Worst documentation experience: reading an 500+ page ISA document where the author (a so-called computer architect) kept confusing the term 'op-code,' and 'instruction.' When I asked for a consistent definition he flamed the shit out of me. My boss sided with him.

On day one was told "don't check in anything that will break the build." Been debugging and had to revert back a few days only to find my clean area is broken by some else's commit.

When the Verilog95 RTL coder tells you your debugger for object oriented SystemVerilog is primitive #stickuphisass

20 yrs programming experience and still fucks with xls.

Oxymoron #123: perforce wrapper scripts which are meant to make perforce run faster.

In merge hell (again).