Thinking testing is less important than delivering

After being here for some time already, it astounds me how many organizations still don't use git or any form of versioning tool.

Pffft. How did you manage to guide the intern to cause merge conflicts with his own code? Genius

Every fucking day I'm asked some fucking stupid question that could have been easily figured if this fucker took 2 mins to look.

"Hey why isn't the issue closed with your commit message? Is it because the CI fail?"

No you dipshit. It's because it hasn't been merged into the master branch. And no the CI didn't fail. If you took 20 seconds to actually look into the pull request you'll see it passed.

God why?

First time getting my hands wet with docker. Ended up fully containerizing my company's project. Never been more proud of miself.

Made to write an electron app as a make-shift solution to restart a service running on a raspberry pi that was deployed as a make-shift solution to another problem

Anyone else here typed a really long post about some fuck up, only to delete it because it's not worth it to get so upset?

Got engaged to set up the CI for a project. Worked with the main developer to set up the dev environment only to find out that he deleted 80% of the migration files because he didn't know what they were

WTF your function takes in 12 parameters!!! Then it checks one and pass the rest to another function!!

I need to learn docker. And learn it fast. These deployment/dev-ops issues needs to be tamed

Anyone else here feels like they are working for a pointy haired boss?

Be happy with JavaScript.

There's no provisioning script. Code repo's there, but no configuration files. Missing folders that break the app. No documentation on what to install, what directories to create, NO instructions. Nothing. Just an empty Ubuntu vagrantbox and a git repo. Took the entire morning and then some, just to replicate the dev environment. Fuck

In my first few months of my first dev job, I written this fragile piece of code in, trigger warning, PHP that sent out email reports to my clients. It was a two men team, and we have no clue about TDD or how to do unit testing for such code. We would just run that piece of code manually do send out dummy emails to ensure things were working.

One day the code broke. I was told by my boss to fix it. Spent the entire day trying to fix but couldn't get anything done. Finally at around 7pm my boss came by and asked why is it I couldn't get it fixed. He helped me troubleshoot and fixed it. And subsequently told me "c'mon man you're better than this."

It turns out that he changed a part of a code that was supposed return an array of strings to an array of objects, adding a second attribute that wasn't even in use.

So what that meant is that he changed a piece of working code, to include a property he didn't need, committed and push to production without even manually testing it. AND TALKED SHIT TO ME.

That was the day I learned git blame and began my journey on TDD.

PM: Guys, we have to upgrade Java 8

Me: hey check out all these cool functional programming stuff (lambdas)in Java 8.

PM: Sorry you can't do that. Our automated testing software isn't up to date to test Java 8. So you have to code it "vanilla"

Me: Erm, upgrade it?

PM: we didn't budget it for that.

Me: *thinks to me miself* brilliant

How does a person learn all these Dev ops/backend/frontend/mobile apps technology? I've been using Vagrant + Django mostly and I feel I'm so behind when people talk about AWS EB, Node, React, SASS, Less. Whelp

!rant

Dude, you know nothing about the code that was written. Don't just Google the problem "how to xxx in Python" and send me the first stackoverflow link and tell me "here's the solution."

Left my previous cushy job for a start-up and a paycut. Can't work in a project that still uses CVS and being the only one who knows what git is.