You will never exit this fitness club. 😜

Client: the platform isn't sending emails

Dev: I'll look into it

(Finds all emails are being sent without issue)

Client: I just tested and I'm not receiving emails. This is obviously a site wide bug and I'm upping the priority to "Critical". I'm also getting everyone over here involved.

(Looks into clients account)

Dev: you didn't turn the setting on to allow emails to be sent to you.

Client: this is still a site wide bug that is affecting everyone.

(Provides screenshots showing emails are being sent and opened. Client closes ticket and doesn't respond anymore)

You know what really grinds my gears?

Seeing a 5-line comment, that have absolute no value, for a variable declaration.

Example:

/*
*
* String that holds a delivery address.
*
*/
public String deliveryAddress;

Few text editors' learning curves. Emacs won the competition ;)

Running.

When you start inspecting code of the page you are using, and you find something like this...
Not sure if I want to make this reservation anymore...

“java.util.Date”
Salvador Dali
Oil on canvas, 1931

People rant here about how they hate documenting things or writing tests or whatever.

Yes these things are not the most interesting but I have a feeling that we are forgetting about most horrendous of tasks - estimating. Especially in agencies. Especially related to altering legacy features. Especially big projects.

I mean, I'm spending time doing something that is basically dev's Voo Doo, hoping that I will be right... and usually I'm not.

My pm requested me to estimate few tasks on a new project(single page app), the problem was that he was creator of these tasks, so we ended up with

- Create back button
- Create next button
- Create table with contents
... etc

As I prefer to take things literally I estimated each task as they literally should (5 min for adding buttons etc). So all tasks together were estimated for about 5h, while whole project was estimated for 100MD. After few talks and discussions we ended up with:

- Create back button
- Create back button logic
- Create next button
- Create next button logic
etc

Just had a Skype call that explained a Skype chat about the fact that I can't do anything on a task, because we are waiting for another (external) dev do finish his work.

Time wasted for Skype chat: 10 min
Time wasted for Skype call: 20 min
Time wasted for stopping myself from doing any harm to the user: 30 min

Lots of legacy code.

People who send to you an email instead of talking to you despite the fact they sit next to you.

You know that you've just gained few levels when you found out about magic in vim.

:help magic

Also term "very magic" is superb.

When you answer the same question, from the same guy, for the Nth time about why this thing you developed N months ago works as it was designed, based on his requirements.

And at the end you can't really be mad, because he is super friendly and being sorry for that... again...

So apparently I now know someone who knows a bit about hacking

Let's see what he'll teach me

I've talked with my friend about what does that mean to work as QA. It seems all they do is watching yet vids with kittens and slacking off, and basically they are useless.

But then, it clicked. They are people to blame first if shipped product have bugs.

I wonder if one day, one dev just thought(after getting reprimanded by his boss for bugs in the final product): "hey, I don't need to listen to this, we can hire a guy for that!

Ranting about not having anything to rant about. It feels so unnatural...

How upvote whoring will be on devRant : Guys upvote this Rant to reach the upper limit on the votes counter and know what variable type it is !!!1!!1!!