Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "wk29"
*Now that's what I call a Hacker*
MOTHER OF ALL AUTOMATIONS
This seems a long post. but you will definitely +1 the post after reading this.
xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that.
xxx: So we're sitting here, looking through his, uhm, "legacy"
xxx: You're gonna love this
xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login.
xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time".
xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am.
xxx: (and the oscar goes to) fuckingcoffee.sh - this one waits exactly 17 seconds (!), then opens an SSH session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has SSHD up and running) and sends some weird gibberish to it. Looks binary. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk.
xxx: holy sh*t I'm keeping those
The bash scripts weren't bogus, you can find his scripts on the this github URL:
When a customer said that I shouldn't be working with web development since I couldn't put 3D animations in her PDF document.6
A 15 minute meeting to discuss what shade of yellow our product should use for warning. I had to attend because I was writing the product.
This was one of about 5 separate discussions on the colour, a few of which involved me showing them a colour wheel and telling them to pick.
I'm a back end developer, the colour is just 3 rgb floats to me, I don't goddam care!3
When you are into Dota2 trying to forget everything after stressful day and your manager messages you if you have spare 10 minutes to discuss next weeks' upcoming tasks.
Hell NO!! Let me play and chill.5
During my internship.
Got wonderful opportunity to present a project to a senior Director of a different team.
And just moments before meeting, my project stopped working.
Was a disaster.
Later came to know there were internal issues in the service I was using in my project.
Though not my fault, but during the meeting, I managed to show a video of the project.
Let me know if folks wants to know what happened later..3
The one they called to announce I was being dismissed after promising a promotion witch led me to refuse a better job opportunity the week before...2
The whole point of having a daily scrum is to let your team know about the progress you've made from last day and what you'd be needing to stick to the sprint plan.
So ideally everyone has 30-60 seconds to give a gist of their activities. And a small scrum team would be productive because everybody is on the same page.
Our scrum meetings usually wait for all of us to assemble with our coffees and donuts, sit down, joke, and then agonizingly go over everybody's existential crisis as a developer because of the task they've been assigned to has too many dependencies. And this happens every single fucking day! These "scrum" meetings tend to go for 1 hour. FML!6
Instead of watching our (software) product demo, the client asked why not build something like Amazon Go? The whole meeting was debating with him.1
On Friday. Client and Project Managers arranged a meeting and wanted me to be there. Client said the meeting will be max 15 Minutes but it was around 2 hours. This client project was due the following week. I was happy because everything was done and excited that the client might be coming down to say how awesome the work was.
The table turned around. They came changed the designed and functionalities. The client said, it won't take long to do it, right? and my Project Manager said No! No! No! don't worry its very easy thing. It will take him around 1 day to do it, it's just all cosmetic changes.
It took me more than a week to get it done, test again, check on browsers. The client was pissed and they fired us. Guess who was blamed for it?1
I don't know what to chose.
The fact that for three months, I had to design a 16-page catalog, when I have no experience and my job is web development;
The fact that I have to do SEO for the site, but that means for my boss that for a one-page long text, we have to find at least 60 (sixty! ) times the occurrences of the keywords;
The fact that when I finally have something interesting to do, the boss finds that it doesn't go fast enough and decide to drop the project even if making a whole new dynamic stock system with the db we have is something hard and long to do;
The fact that when I come to work five minutes late, my boss is at the verge on screaming on me, even if I come ten minutes early every other day;
The fact that when I'm coding, I need concentration, I don't need the boss to give me the phone to answer customers, stop everything I am doing and explain them what products we are selling;
The fact that I am paid the minimum wage for a trainee, and when there's no coffee anymore, we have to buy some ourselves because "you drink way too much coffee, you understand" (three a day, sorry for wanting to stay awake);
The fact that I have asked for one year how many days of vacation I still had, and the only answer they gave to me yet was: "Oh, we have to ask the accountant". I still don't know how many days I have left;
The fact that the site is made only by trainees since the beginning, so circa 2008, and the code is horrible but "it works, so don't touch it". The admin part is in CodeIgniter, the front in laravel 4.2, there are a lot of useless code but we can't touch it because the boss doesn't think it is worth the time.
I almost made a burn-out last year, my doc saw my state right before and made me stop for a week. I still have to work there 'till end of august, then I will have my diploma and find another company to work with. Now, I check everyday on my calendar.6
When a client told you how easy the feature is and he could've gotten a cheaper price from other developers but prefer to let you do it.1
Once I had a meeting with a employee. He asked for some bonus money and I wanted to fire him. Was weird.1
Today. Where the senior developer got into a schoolyard yelling match with one of our owners. And then the only thing we accomplished in an hour was that we decided we needed another meeting next week.
When the client you did a huge project for goes bankrupt and you have to fire up your (questionable) legal skills to get the latest 35% of the money -.-