Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "meetings about meetings"
-
The programmer and the interns part 2.
We will discuss numerous events that happened over the past week or so.
Case 0:
We had our weekly engineering meeting. The interns were invited as well.
We hold meetings in the generic, big, corporate meeting rooms with a huge table in the middle.
There were more than enough chairs for everyone yet the most motivated and awkward intern (let's call him Simon) chose to stand, cause "it's cool man, I always stand". At this point we all know that he probably read about Agile stand up meetings and is confusing it with this one. Otherwise he's simply trying to stand out from the rest. (See what I did there?)
Anyway the meeting has started way later than planned (what a surprise) and took much longer than Simon expected. Everybody is sitting and listening to the CTO while occasionally glancing at the weird looking intern standing awkwardly and refusing to sit because it would make his original intentions pointless. He even tried to nod whith a serious face and his hands crossed when the CTO said something and looked at his general direction. The meeting was about a hour and a half long but with the delay it was at least 2.5 hours.
At the end Simon was so exhausted that he fell asleep on the office puff, was forgotten and locked inside. 3 hours later when I was home I received a call from him with his sleepy-trying-to-sound-awake voice telling the news. Lucky there's a 24/7 Noc team that could rescue him.
Case 1:
An intern who was late on his Linux test connected to every test VM (should I remind you that each one has a personal VM but they share passwords for their roots?) and tried to reset it with "sleep 10s; shutdown -h now".
He took down all 13 of those so I had to turn them on and switch passwords again.
Case 2:
One of the interns didn't do any of his training chores. Apparently he forgot what he was told to use, ignored all online documentation and used Windows CMD with Linux commands for almost a week already.
Case 3:
Simon uses Vim to write all text possible. Even mails, he then selects all and copies into the mail body. He spent half a day on a homework task I gave them. He wrote everything inside one text file using Vim. When he was done he saved the file and quit the editor. He then said "Oh shit! I've forgot to sign my name!". I explicitly told him that theres absolutely no need for that because I see which mail the file was sent from. He said "I don't even need a program for that!" and gave a couple of strokes on the keyboard.
Later I received an email from him with a .txt attachment. When I opened it the only text that was inside was "by Simon ;)".
I logged to his machine and checked the last command ran on the file:
echo "by Simon ;)" > linuxtasks.txt
Case 4:
The girl here uses a MacBook. She keeps getting confused with the terminal windows and rebooting her own machine instead of the remote VM.
Case 5:
Haven't checked yet how this happened but one of the interns deleted the gui from his local Centos.35 -
Welcome back to practiseSafeHex's most incompetent co-worker!
*sitcom audience cheers*
Thank you, thank you. Ok so far we've had a developer from hell and a CEO who shot to fame for being the first rectum to receive a passport and be given a job.
2 pretty strong entrants if you ask me. But its time to slow it down and make sure everyone gets a fair chance. Its not all just about the psychopaths and assholes, what about the general weirdo's and the stoners who just made life awkward?
So here we go, Most incompetent co-worker, candidate 3, "A".
"A" was a bit of an unusual developer, despite having a few years experience in his home country, he applied for an unpaid internship to come work with us ... probably should have rang alarm bells but hey we were all young and dumb back then.
I had to say I felt very bad for A, as he suffered from 2 very serious, and job crippling personal conditions / problems
- Email induced panic attacks
- Extreme multifaceted attachment disorder (also known in layman terms as "get the fuck away from me, and do your job" syndrome)
While he never openly discussed these conditions, it was clear from working with him, that he had gone undiagnosed for years. Every time an email would come in no matter how simple ... even the services team asking to confirm his staff ID, would send him into a panic causing him to drop everything he was doing and like a homing missile find me anywhere in the building and ask me what to do.
Actually "A" also suffered from a debilitating literacy issue too, leaving him completely unable to read our internal wiki's himself. Every week we had to follow a set of steps to upgrade something and every week to mask his issue, he'd ask me what to do instead ... no matter how many times I sat with him previously ... must have been truly embarrassing for him.
But "A"'s finest moment in the company, by far, was the day where out of the blue, at the top of his voice (as if wearing headphones ... without wearing headphones) he asked
"DO YOU KNOW ANYONE WHO SELLS POT?"
... why no, manager of the entire department standing behind you, I do not
... why no, tech lead talking to manager, I do not
... why hello 50% of my team staring at me ... no "A", I do not!
Needless to say all our team meetings were a little awkward for the next few weeks after that but hey who doesn't like being thought of as a stoner / drug dealer by their team mates huh?
Will A make it to the top of the list of most incompetent? Well he has some truly logic defining competition yet to be announced.
Tune in later for more practiceSafeHex's most incompetent co-worker!!!16 -
Meeting with smooth suit guy:
"So, our company has pivoted"
I hate everything about this guy, not having slept well at all, I fucking snapped:
"Pivoted? Oh wow, what a wonderfully refined word to describe that your asinine business model smacked flat into the mud, that your obtuse bubble of vague ideas popped and your childish dreams of piles of undeserved gold got caught up by the hard reality that your product does not add any tangible value -- yet you tricked your sheepish retarded investors once again to fall for a new hype-filled pitch deck? Congratulations. At least you probably snort enough coke to keep believing in yourself..."
The guy nervously wiped his nose, stuttered, and walked off looking angry and a little confused.
So it turns out, my boss is apparently the major "sheepish retarded investor" in this company.
Today I got a mail from him. I expected fire and fury, nuclear ICBMs crashing into my desk.
"Thanks for your feedback, this is why I invite you to meetings. Could you take a look at their new pitch slides and preliminary API docs for me?"16 -
One of my worst meetings, as the sheer rage was unbelievable.
Backstory:
Architect: "Stop duplicating code", "stop copy pasting code", "We need to reuse code more", "We need to look at a new pattern for unit tests" etc.
Meeting:
Architect: What did you want to talk about?
Me: I built a really simple lightweight library to solve a lot of our problems. Its built to make unit testing our code much easier, devs only need to change a small bit of how they work.
Architect: I like the pattern a lot, looks great ... but why a library? can we not just copy the code from project to project?
... do you have a twin or something?2 -
"Let's go for the low hanging fruit first" 🤢
"I think we should do some market research" 🤢
"Yeah that is also on my radar" 🤢
OKAY YOU FUCKING CUNT, STOP WITH YOUR PATRONIZING SHIT.
FIRST OF ALL, ARE YOU REALLY SO SMALL MINDED THAT YOU CAN'T REACH ANY HIGHER? THIS TREE IS FUCKING RAW AMD BARE ON THE BOTTOM, WITH YOUR FILTHY CLAWS GRASPING FOR ALL THOSE EASY NARROW FIXES.
SECONDLY, A FUCKING EMAIL SURVEY WITH BIASED QUESTIONS ANSWERED BY 3 HOBOS IS NOT BLOODY MARKET RESEARCH.
THIRDLY, IF THIS NUCLEAR ICBM OF AN INFRASTRUCTURE PROBLEM IS ON YOUR RADAR, MAYBE STOP FONDLING YOUR SWEATY BALLS FOR A MINUTE AND TAKE ACTION.
"Okay lets peel this onion, so we hit the ground running" 😩🤢😞
NO, LET'S NOT "HIT THE GROUND RUNNING", YOU'RE GOING TO FUCKING TRIP AND MESS UP YOUR FACE EVEN MORE. HOW ABOUT GET YOUR PILE OF SHIT IN ORDER FOR ONCE, PREPARE FOR A MEETING? HOW ABOUT THOUGHTFUL ACTION, SOME FEATURE DESIGN?
"No, just implement it quick and dirty" 🤢😡👿
OH YOU WANT IT QUICK AND DIRTY? IS THAT HOW YOU FUCK YOUR DAD AS WELL?
"Let's evaluate the fix in a few weeks. We really had good synergy here team" 🤢😫
YEAH SURE, LET'S EVALUATE THIS.... BUT LET'S EVALUATE IT RIGHT NOW: 😡
"Ahem....
1. You're always late for meetings.
2. After 6 months, you still barely know what we do as a company, you still don't know the teams, and you still don't know the product.
3. You do not listen to engineers flooding you with red flags, requiring time for a redesign to fix serious scaling issues.
4. Everything must be a quickfix, nothing is allowed to require thought, because you CAN ABSOLUTELY NOT think ahead for more than 30 seconds.
OH AND IF YOU EVER AGAIN COVER UP ONE OF YOUR MANY SHORTCOMINGS WITH THAT FUCKING SLIMEY DOUCHEBAG MANAGER VOCABULARY OF YOURS, LET'S SEE HOW MUCH SYNERGY YOU FEEL WHEN YOU'RE DEEPTHROATHING A CACTUS."19 -
Replace the teachers with no real world experience with part-time workers that are still active in IT.
I had this last year in my final year of vocational education and it was amazing, I had two teachers running their business two days a week and teaching us everything on the three remaining days.
I learnt about oop without dogs and cats, I learnt to extract information from invoices to be able to create an invoicing system without being misled by customers, and much more.
Second thing would also be something we did in my previous education. It was called "learning productively".
Basically, companies would give a project to the school and students could pick one to do for a few months. You had to have meetings with the customer, you had to give presentations and it wasn't another fucking calculator.
I've had the pleasure of working with a big corporation like this and learnt a ton in my first year.
These were extremely valuable, I think I'd still be a piece of shit developer without any knowledge on how to actually develop a full system and how to manage a project as a dev.
Peace6 -
My boss isn't really a developer. He isn't part of the development team and doesn't know any technical details about the product. He doesn't want to code, "too much effort", he just wants to boss. But he wrote some php in the early 2000's and is really, really proud of his codecademy html/css badge...
And that makes him dangerous.
Today I hear him talk from behind his laptop: "Right, we have this page for creating management groups, but we can't edit them yet. I can fix that!"
This task is literally on the current sprint, but he doesn't know that because he doesn't attend scrum meetings and ignores everything people say to him.
Me: This smells like probable cause, let's look with suspicion over his shoulder.
Boss:
"OK, right-click create.blade.php -> copy.
then right-click directory -> paste.
now just rename file to edit.blade.php!"
I start walking to the office kitchen.
Boss mumbling in the background:
"Now all I need to do is just copy the whole method in the controller, change the post url in the form, and modify the <h4> at the top, so it says edit instead of create."
Boss, looking at me now:
"This is so easy... creating and editing is almost the same thing, you can just copy paste all the code from one template to the other! I don't understand what you developers are always complaining about!"
Me: *Hands him a roll of paper towels*
Boss: "What is that for?"
Me: *points at code*6 -
Summing up many ridiculous meetings I've been in.
Many years ago we hired someone for HR that came from a large fortune 500 company, really big deal at the time.
Over the next 6 months, she scheduled weekly to bi-weekly, 1 to 2 hour meetings with *everyone* throughout the day. Meeting topics included 'How to better yourself', 'Trust the winner inside you'...you get the idea.
One 2-hour meeting involved taking a personality test. Her big plan was to force everyone to take the test, and weed out anyone who didn't fit the 'company culture'. Whatever that meant.
Knowing the game being played, several of us answered in the most introverted, border-line sociopath, 'leave me the frack alone!' way we could.
When she got the test results back, she called an 'emergency' meeting with all the devs and the VP of IS, deeply concerned about our fit in the company.
HR: "These tests results were very disturbing, but don't worry, none of you are being fired today. Together, we can work as team to bring you up to our standards. Any questions before we begin?"
Me: "Not a question, just a comment about the ABC personality test you used."
<she was a bit shocked I knew the name of the test because it was anonymized on the site and written portion>
Me: "That test was discredited 5 years ago and a few company's sued because the test could be used to discriminate against a certain demographic. It is still used in psychology, but along with other personality tests. The test is not a one-size-fits-all."
VP, in the front row, looked back at me, then at her.
HR: "Well....um...uh...um...We're not using the test that way. No one is getting fired."
DevA: "Then why are we here?"
DevB:"What was the point of the test? I don't understand?"
HR: "No, no...you don't understand...that wasn't the point at all, I'm sorry, this is getting blown out of proportion."
VP: "What is getting blown out of proportion? Now I'm confused. I think we all need some cooling off. Guys, head back to the office and let me figure out the next course of action."
She was fired about two weeks later. Any/all documentation relating to the tests were deleted from the server.16 -
A year ago I would have said:
"Because I love solving logic puzzles, there's no greater joy than finding a very simple, elegant translation of a user's requirements into code"
Then 2020 came. I'm SO FUCKING FED UP with coworkers and managers who miss all the required competence to organize and communicate about projects as they are fundamentally incompatible with the concept of working from home.
I'm quite sure I'm the last one to give up at my work.
The company chat has completely died down. I've tried setting up meetings, but even my bosses show up irregularly, confused about why I'm calling them in the middle of their Netflix marathon.
So if you can't beat 'em, join 'em. My answer is now:
"I'm a developer because I get nearly 6 figures, for going through my Steam Library while completely shitfaced at 11AM. When I sober up in the afternoon, I work on some hobby projects. I get to spend 500/m on ordering sandwiches"9 -
Worst thing you've seen another dev do? Long one, but has a happy ending.
Classic 'Dev deploys to production at 5:00PM on a Friday, and goes home.' story.
The web department was managed under the the Marketing department, so they were not required to adhere to any type of coding standards and for months we fought with them on logging. Pre-Splunk, we rolled our own logging/alerting solution and they hated being the #1 reason for phone calls/texts/emails every night.
Wanting to "get it done", 'Tony' decided to bypass the default logging and send himself an email if an exception occurred in his code.
At 5:00PM on a Friday, deploys, goes home.
Around 11:00AM on Sunday (a lot folks are still in church at this time), the VP of IS gets a call from the CEO (who does not go to church) about unable to log into his email. VP has to leave church..drive home and find out he cannot remote access the exchange server. He starts making other phone calls..forcing the entire networking department to drive in and get email back up (you can imagine not a group of happy people)
After some network-admin voodoo, by 12:00, they discover/fix the issue (know it was Tony's email that was the problem)
We find out Monday that not only did Tony deploy at 5:00 on a Friday, the deployment wasn't approved, had features no one asked for, wasn't checked into version control, and the exception during checkout cost the company over $50,000 in lost sales.
Was Tony fired? Noooo. The web is our cash cow and Tony was considered a top web developer (and he knew that), Tony decided to blame logging. While in the discovery meeting, Tony told the bosses that it wasn't his fault logging was so buggy and caused so many phone calls/texts/emails every night, if he had been trained properly, this problem could have been avoided.
Well, since I was responsible for logging, I was next in the hot seat.
For almost 30 minutes I listened to every terrible thing I had done to Tony ever since he started. I was a terrible mentor, I was mean, I was degrading, etc..etc.
Me: "Where is this coming from? I barely know Tony. We're not even in the same building. I met him once when he started, maybe saw him a couple of times in meetings."
Andrew: "Aren't you responsible for this logging fiasco?"
Me: "Good Lord no, why am I here?"
Andrew: "I'll rephrase so you'll understand, aren't you are responsible for the proper training of how developers log errors in their code? This disaster is clearly a consequence of your failure. What do you have to say for yourself?"
Me: "Nothing. Developers are responsible for their own choices. Tony made the choice to bypass our logging and send errors to himself, causing Exchange to lockup and losing sales."
Andrew: "A choice he made because he was not properly informed of the consequences? Again, that is a failure in the proper use of logging, and why you are here."
Me: "I'm done with this. Does John know I'm in here? How about you get John and you talk to him like that."
'John' was the department head at the time.
Andrew:"John, have you spoken to Tony?"
John: "Yes, and I'm very sorry and very disappointed. This won't happen again."
Me: "Um...What?"
John: "You know what. Did you even fucking talk to Tony? You just sit in your ivory tower and think your actions don't matter?"
Me: "Whoa!! What are you talking about!? My responsibility for logging stops with the work instructions. After that if Tony decides to do something else, that is on him."
John: "That is not how Tony tells it. He said he's been struggling with your logging system everyday since he's started and you've done nothing to help. This behavior ends today. We're a fucking team. Get off your damn high horse and help the little guy every once in a while."
Me: "I don't know what Tony has been telling you, but I barely know the guy. If he has been having trouble with the one line of code to log, this is the first I've heard of it."
John: "Like I said, this ends today. You are going to come up with a proper training class and learn to get out and talk to other people."
Over the next couple of weeks I become a powerpoint wizard and 'train' anyone/everyone on the proper use of logging. The one line of code to log. One line of code.
A friend 'Scott' sits close to Tony (I mean I do get out and know people) told me that Tony poured out the crocodile tears. Like cried and cried, apologizing, calling me everything but a kitchen sink,...etc. It was so bad, his manager 'Sally' was crying, her boss 'Andrew', was red in the face, when 'John' heard 'Sally' was crying, you can imagine the high levels of alpha-male 'gotta look like I'm protecting the females' hormones flowing.
Took almost another year, Tony released a change on a Friday, went home, web site crashed (losses were in the thousands of $ per minute this time), and Tony was not let back into the building on Monday (one of the best days of my life).10 -
So the remote manager who won't reply to my emails or slacks, won't invite me to meetings with product / design, won't ask for my opinion on deadline dates and won't tell me whats being said in meetings (despite repeated effort on my part to change this);
Has decided to send an angry email, cc'ing a bunch of people, about "constant deadline slippage" and poor planning on our part focusing on features that should have been de-prioritised.
ahem
*clears throat for maximum yelling rant-ability*
<rant>
I HAVE BEEN EMAILING YOU FOR FUCKING WEEKS ASKING TO TALK ABOUT THE DEADLINES YOU FUCKING COLOSSAL ASS CLOWN.
I'VE BEEN REPEATEDLY TOLD THAT THESE FEATURES ARE A MUST HAVE AFTER ASKING TO DE-PRIORITISE THEM, AND HAVE TOLD YOU THE DATES ARE NOT FEASIBLE.
ONE MORE, ONE MORE EMAIL OR BAD COMMENT AND I'M EXPENSING A TRIP OVER THERE, TO KICK YOU SQUARE IN THE NUTS AS HARD AS HUMANLY POSSIBLE. I'LL HAPPILY BREAK MY FOOT OFF IF NECESSARY, YOU USELESS PIECE OF SHIT.
</rant>
... the above is work appropriate to email back to him and all the higher ups right?12 -
So a guy wants to start a company with me. He wants to be CEO 👨💼 I'm fine with it but now he also wants me to obey every one of his orders such as attend long unplanned meetings, go do market research, code the app and for what, a mere 5%. He gets a bigger cut of the income because he came up with the idea 💡, he also gets to sit and order me around because he's read a few books on business and economics. People don't seem to understand the difference between having an idea and implementation. I just left and said no to every offer he had the highest of which was 10%, don't be worried about the money he says this is a real opportunity for you. I mean wtf is wrong with some people.14
-
Story of my most useless meeting?
Too many to mention. Here's one. Years ago a new HR associate was specifically hired to better engage the workforce. About once a week, she conducted about an hour to two hour meetings which consisted of every 'touchy-feely' idea you could think of. I swear any day I was going to walk into a meeting and do the "fall back into your partner" trust exercises.
One particular meeting, 'Betty' engaged us with the topic of what keeps us motivated, and I was a little more annoyed than usual because I was behind on a system critical project and these meetings were mandatory.
User1: "Knowing I make customer satisfaction my number one priority."
User2: "The strong sense of accomplishment I feel by doing my best"
Me: "Money"
<you could almost hear Betty's gasp>
Betty: "Oh, no, money shouldn't be the motivator. Money is like icing on the cake. Tell us what keeps you happy and engaged."
<other users nod their heads in engagement>
Me: "Again, money."
User3: "I can't...ugh..I don't believe..oh..why would you say that? I think being part of such a great team is payment enough."
<more nodding of heads>
Me: "Do you work for free? I don't. None of us do. Would any of you keep doing your jobs here if you weren't getting paid?"
Betty: "That is really not the point of this meeting."
Me: "Sure it is. I'll bet if Order Taking starting providing bonuses for positive after-call surveys, employee satisfaction would go through the roof. Anyone else like that idea?"
Betty: "Your attitude isn't helping this discussion. Lets move on."
Me: "Lets not. In 20?? the Gartner group performed a study where they 'discovered' the primary motivator for employees was money. You want employees to perform better, you pay them. It is really that simple."
<I could see the looks of "Its OK to speak my mind?" and others wanting to speak up>
Betty: "Moving on. Lets go over the company core values again and discuss how they enrich our lives at work and at home."
I kept quiet for the rest of the meeting.
The poop hit the fan, and my boss pulls me into a conference room
Boss: "Betty is really pissed at you. She went directly to the VP of HR"
Me: "Good. Does this mean I don't have to attend the enrichment meetings?"
Boss: "Yea, that was her idea of punishment. Lucky bastard."8 -
So many interruptions!
So many distractions!
I just want to fucking finish this refactor. I dont' care about meetings, texts, bloody office game tournaments, lunchtime, gossip, or people trying to be friendly. Just let me fucking work!
If you see me rocking out with my headphones on and working furiously, seriously, just don't fucking interrupt. I'll bite.17 -
This is a long rant. Sorry in advance. I just want to let it all out.
I don't really know what John (not his real name) did to my boss, who I shall name as Steve. Does he have a personal grudge? Like wtf?
John wasn't even incompetent. He even helped us mobile developers in our designs using photoshop. He's flexible. Ok sure, he isn't a top performer, but he isn't a low performer either. But why the fucking hate? really.
We currently have a new project, and are assigned to our posts. Then Steve goes, "Ok John, you will remain in the old project." He already said it once, which is fine. But did he really have to bring it up EVERY TIME? "John doesn't have to go overtime because he's in the old project, so it'll only be us." Like really? Of course we know that. why do you have to keep repeating that John isn't included? He even pointed at John during this. John shouldn't have been in the meeting then. Dipshit.
There was a meeting with the Web team in regards to what the progress was. When it came to John, Steve had to say, "The design is so ugly." Ok.. first off, you are not the QA to say that. And everyone else says it's fine. Even the QA says it's fine. So wtf? Why do you hate him so much?
We have these friday meetings in where we present our topics to the team, like Object Oriented Programming, SDLCs, and the like. We presented our stuff, and Steve listened attentively to everyone. But when it came to John, guess what? he ain't listening. He's on his phone, on his EARPHONES even. fucking rude. When John finished, he said, "You didn't present everything." He talked for an hour and a half. His topic has many things. Of course he can't present everything. And that is all you have to say? What about the others then? The others didn't present everything but you didn't complain. Why do you have to humiliate him to everyone else?
Way to demoralize your employee. What a lead. Fucking piece of shit. I am treating John pizza since I can't do anything else for him. It's frustrating. I wouldn't be surprised is John left the company.9 -
My whole team was a circus:
- Dev 1, the senior: he will be spent his days coding his personal projects and will convince management that everyone else needed to prove themselves so he will have nothing to do and we will do all the work.
- Dev 2, the junior: he was convinced that his mission in life was to be friends with his team. He's desk was far from the rest of the team so he will show just right after lunch EVERY FREAKING DAY with a list on his phone of random things he wanted to talk about like music, artists, art, news, etc., he really thought I didn't notice the list.
- Dev 3: the vegan: you will hear on every chance how she was so awesome for being vegan.
- Dev 4, the expert: if you ask him anything he will stare at you in silence to make you feel like you are a stupid for not knowing the answer and then turn around like nothing.
- Dev 5, the ghost: he will show early every day, code without mouthing a word and leave at 5pm, I think I heard him saying "hmmm" once but I might be wrong.
- Dev 6, the coder by accident: he was a graphic designer and ended up doing front end so he hated his job.
- Dev 7, me: the one who didn't care about anything but doing his job and leave.
- The project manager: she didn't knew anything about technology but will attend meetings with clients on her own, commit to deadlines and then inform us that the project that we estimated for 8 weeks will have to be done in 2 with new additions to the features.
You know the drill, here's your potato :/7 -
There are a lot of things that could rank up as the worst about being a dev, such as recurring meetings, documentation, shitty requirements, pm gnats, Monday, etc...but something that truly ruins it all is NO INTERNET CONNECTION.5
-
Sometimes I envy the blind because nobody invites them to "let's talk about what colour to make this" meetings1
-
Today the CEO called a meeting with our team just to get to know us personally and have some friendly chat. These meetings are to become a regular thing. Seems like he really cares about his employees.11
-
Last week we had a short seminar at work about 'listening skill.'
In that speaker gave an example how 'natural' leaders speak last in the meetings.
From that day we are having entirely silent meetings.
Now management is planning seminar on 'Speaking Up'3 -
Another episode in the search of a job and it involves recruiters again
Last week tuesday:
> d69: 'Hi this is derpina69 from someFancyShmancyCompany, we got a position for you that might be interesting for you, here is the job description, would you be willing to meet us?'
> Me: 'Well it seems interesting enough, how about we set up a videocall meeting since this is a informative meeting, once ypur end customer is interested in my profile, i am willing to come over'
> d69: 'sure, i'll get back to you to alert attendees for this meeting, i'll get right on it'
Days go by without any word nor even an ical...
Two days ago:
> me: ' hello, pinging you again for a sitrep on the meeting, would like to hear from you and your attendees, wkr: neatnerdprime'
Nothing, until today.
> d69: 'hi sorry for the late reply, we really would like you to come ovzr because we don't like videocalls, are you available on these dates?'
MOTHERFUCKING SHITFACED CALF, YOU REALLY NEEDED TO HAVE MORE THEN A WEEK TO FIGURE THAT OUT, GODDAMN EVEN A TODDLER CAN BE QUICKER IN A RESPONSE ON WHAT HE OR SHE WOULD LIKE!
> me: ' sure, lets pick this date, hope you hace coffee ready'
> d69: 'we don't serve coffee for first meetings'
Mfw.webm
What the actual fuck!?!?
You're going to be classified down to my shit tier opportunities, and you better buy some goddamn coffee. All-dieties-be-damned!15 -
Our manager is not a developer and he has no idea of what we are doing most of the time, but he thinks that stand-up meetings are the coolest way to control us.
Sometimes coworkers joke about his lack of knowledge and today I think we reached the highest jerk level: «Yesterday I opened a new branch on the git repository and today I'll continue on this task».
I struggled to stay serious on my turn.8 -
Here's a true story about a "fight" between me and my project manager...
I've been working as a Frontend developer for nearly two years, managed to acquire a decent amount of knowledge, in some cases well above the rest of my coworkers, and one day I got into a bit of a disagreement with my project manager.
Basically he wanted me to copy/paste some feature from another project (needless to say, that... "thing" has more bugs than an ant farm), and against his orders I started doing that feature from scratch, to build a solid foundation from the very start.
I had a lengthy deadline to deliver that feature, they were expecting me to take some time to fix some of the bugs as well, but my idea was to make it bug-free from the moment the feature was released. Both my method and the one I should be copying worked the exact same, but mine was superior in every way, had no bugs, was scalable and upgradeable with little effort, there was no reason not to accept it.
We use scrum as our work methodology, so we have daily meetings. In one of those, the project manager asked me how was the progress on that new feature, and I told him I was just polishing up the code and integrating it with the rest of the project, to make sure everything was working properly. I still had a full day left before the deadline set for that feature, and I was expecting to take about half an hour to finish up a couple lines of code and test everything, no issues so far...
But then he exploded, and demanded to know why wasn't I copying the code from the other project, to which I answered "because this way things will work better".
Right after he said that the feature was working on the other project, copying and pasting it should take a few minutes to do and maybe a couple of extra hours to fix any issues that might have appeared...
The problem here is, the other project was made by trainees, I honestly can't navigate through 3 pages without bumping into an average of 2 errors per page, I was placed into this new project because they know I do quality code, and they wanted this project to be properly made, unlike the previous one, so I was baffled when he said that he preferred me to copy code instead of doing "good" code...
My next reply was "just because something has been made and is working that doesn't mean that it has been properly made nor will work as it should, I could save a few hours copying code (except I wouldn't save any, it would take me more time to adapt the code than to do it from scratch) but then I'll be wasting weeks of work because of new bugs that will be reported over time, because trust me, they will appear... "
I told him this in a very calm manner, but everybody in the meeting room paused and started staring at me, not many dare challenge that specific project manager, and I had just done that...
After a few seconds of silence the PM finally said... "look, if you manage to finish your task inside the set deadline I'll forget we ever had this conversation, but I'll leave a note on my book, just in case..."
I finished that task in about 30 mins, as expected, still had 7 hours till deadline, and I completely forgot about that feature until now because it has never given any issues whatsoever, and is now being used for other projects as well.
It was one of my proudest/rage inducing moments in this project, and honestly, I think I have hit my PM with a very big white glove because some weeks after this event the CEO himself came to the whole team to congratulate us on the outstanding work being made so far, in a project that acted against the PM's orders 90% of the time.11 -
Was in a meeting with my boss. I complained about there being too many meetings and thus not enough time at the keyboard. He told me that I should turn down meetings I feel I dont need or feel are unnecessary (no point in me being there if I dont feel i contribute). Point taken . I stood up and left. He later told me he appreciated my honesty and would try to keep are meetings to the point in the future :D
-
Okay so this is going to be a rant.
My exams started last wednesday. I'm doing a study called Application Development and I'm in my 5th year now (out of 4, long story).
This is the stuff that's going wrong at the moment and it's getting FUCKING annoying.
- The windows computers were not installed that well so everyone had to downgrade from the last update which took way too long.
- We have to have at least 1-3 conversations with the 'client' and 'manager' for each document but the waiting lists are so long that we have to wait for about 2-4 hours in general (we had a total of 18 hours for the first task) so a lot of people couldn't even have a meeting about around half of the documentation. Having meetings about everything is a REQUIREMENT for a good grade.
- Some of the teachers are so slow that the meetings take way too long.
- Although documentation is important, we calculated that about 80% of the WHOLE FUCKING EXAMS will be documentation which is way too fucking much.
- Some of the grading points (like chapters you have to write in the documentation) ARE NOT EVEN IN THE TEMPLATES MY STUDY PROVIDES. Already had a moment where a teacher was like 'I'm missing this chapter?' me: 'It's not in the official templates?!?' teacher: 'stop right there. I have to grade you for this so is that your or my problem'? unbe-fucking-lievable.
- Some students get so many 'musts' that we are seriously doubting if we can get this to work within about 2 days (12 hours).
Sorry for this rant but I had to get this the FUCK out.8 -
So, when there is shit hitting the fan at work I tend to stay during lunch to take care of it and make sure I can take as much of a hit for it before it reaches my employees.
the lead developer walked to my office to let me know that he was about to take lunch and asked if i had plans for lunch. I told him that there were some reports to be done and some meetings that i had to attend and would be staying back, he asked if i was going to get something to eat and I said that I would try to get something as soon as possible. My man knows that I am on a strict regimen due to my workouts, and he normally takes concern over it.
I did not get something to eat, but the hour mark when he came back I was fucking starving and still stuck on a call T___T my man walks into my office as I was on a call (meeting) and he leaves a bag with my favorite burgers in my desk as I was waving hello T___T I thanked him afterwards.
Y'all, if youse a manager, take care of your people, fight for your people, my boys know i go the extra mile for them and we used to chill out having bbqs every other week playing pathfinder(i suck but make a fun party member) before the pandemic. Your coworkers might very well be your extended family. Even if you are the manager them peeps will look out for you if they know you are not a power hungry egomaniac that is more focused on keeping higher ups happy.
These dudes are my friends, my family, they were the board of members tasked with knowing if I was to get hired when i first joined in, and even tho I am now their manager I am still their friend, shit like this is possible and what I would implore everyone to strive for, because even if your organization is a faceless entity full of people that don't care for you, the dude at arms reach from your office is there, people are there, fellow human beings are there.
Fuck, just be nice to everyone else and I severely hope y'alls work life is a chill as this one.3 -
Once had a classmate schedule a meeting with me to "go over something" for a project we had together. (Not a CS class, but it was a general education class.)
I agree, make time on my schedule for this meeting.
I get there and they say "Yo I just wanted to let you use my flash drive so you could make some changes to the PowerPoint I started last night. Just get it back to me a few days before the project is due and we'll look over it together."
You asshole. Go fuck yourself.
This lesson taught me to ask what meetings are about in order to prevent this bullshit2 -
All,
Let's have a quick meeting about today's meeting so we can plan our meeting for tomorrows meeting. Thanks!
Thanks,
Kill myself5 -
Working really hard, finishing tasks, upgrading servers. Cancel some useless meetings to finish up features, working till 2am to get a database migration working. Half of the platform is transformed, both customers and team are very happy about their accomplishments.
Boss: "OK, I think we're on the right path with these changes, but productivity and morale is honestly disappointing. Are you guys sleeping enough? You all look very tired and unmotivated!"
Attend all meetings, call boss at 7am to discuss random purchases like a whiteboard, run around the office holding a (broken, lol) MacBook, looking very busy & slightly worried. I shout random things at people across the office like "Nice work Gary!" and "Damn, you are on a roll Angela!". I initiate smalltalk with department heads, only to immediately disrupt the conversation by checking my phone saying "Oh I really have to take this one" (empty battery, lol). No one writes a single line of code for four weeks, and nothing new has been deployed by the whole team.
Boss: "I think it's commendable how productive the team has become this month. You guys are all so active and involved. A real improvement!"6 -
My dad used to be a Marketing Manager. He used to make a lot of presentations et al for his meetings. We got our first computer in our house when I was around 7 years old. It was first Windows 95, but I wasn't fortunate enough to even touch the machine. My dad was very protective about the machine. He himself would not use it unless he had to complete some work overnight. For me, it was an absolute wonder as to how and what that thing in the bedroom sitting on the desk next to my parents bedside was. I used to hide and peek around the door sill when my dad was working on it. He became a bit more lenient with the Windows 98 and let me and my sibling play DOS games under his supervision for a limited time.
Over time, I managed to look over his shoulder for the passwords - both BIOS and OS user passwords and started logging in myself. By now, my dad would let me sit on the bed near him when I looked curiously as he worked. Then I had to figure how to connect to the internet and surf the web. And there folks is how my journey with computers began.4 -
Let's build a house with no blueprint, no idea how it should look but have daily meetings about the bathroom... #Scrum3
-
Following on from: https://devrant.com/rants/1345037/...
I sent a polite but very frank email to the manager telling him I don't agree and think its extremely unfair to overlook the breath and scale of work we have done in the past few months. Instead to criticise us for this.
He didn't reply, or really speak to us for a week. Then suddenly one day the developers were all in a meeting room and he butted in to talk.
He first of all said he wanted to let things settle before talking to us, which gave me high hopes as I expected him to then say something like we miss understood, or he didn't realise etc.
... but no ... the next words out of his mouth were "I'm not apologising for anything, and I don't want to be told to piss off in an email".
A) Piss off = completely untrue and a massive exaggeration.
B) Go fuck yourself with a cactus.
C) See point B.
In that meeting we discussed the massive amount of meetings and work we have to do which was described as "just the job".
We were told we all have to be in until 5pm, but that we also don't. We need to be in the office more, but its fine if we can't be. And we need to cut down on WFH, but its ok to WFH ... so yeah everything is crystal clear.
I haven't written any code in 3 - 4 weeks. I'm now dealing with GDPR shit, and our internal processes to handle it (despite having no legal background). Have to fill out 140+ question surveys about each of our projects, which are the most vaguest things i've ever seen.
"Are you processing large scale data" - The fuck is large scale, oh wait heres a definition. "Large scale is determine by volume or percentage of population size" - How in the name of christ is that a definition? Fucking lawyers and their bullshit.
The next round of applications for research funding is coming around soon and were being told to work on proposals (which are huge and a lot of effort). While being told we need to define and improve on our KPI's for the year. While trying to find time to ... you know ... do ... work?
I'm just so fucking bored and pissed off with this place. I have to do the work of 6 people, nothing is ever good enough, devs have to do very non-dev tasks with little to no support. Bosses are just annoyed about everything, everyones in a bad mood and everything sucks.
A friend put me forward for another senior role in another company. Thought this would be my saving grace. They have a strict interview process with white-boarding (which I hate) and will likely ask about algorithms etc which I suck at. I'm so burnt out from this place I just can't find the motivation to go study up or prepare properly.
I just wanna write code, why is there so much bullshit in life11 -
!rant
I complained during a dev team review about the too many dev calls/meetings we have that are supposed to improve our productivity but instead feel like interrupting our work and line of thoughts when focusing on something.
I expected the team lead to bash me or say "Nooo, these meetings are important bla bla bla" but he received it quite positively and already changed how we do things.3 -
How I picture w3 meetings about the CSS color spec.
The result, we have both color: gray and color: grey in all their variations (light, dark, slate...)16 -
Man I really need to get this off my chest. So here goes.
I just finished 1 year in corporate after college. When I joined, the team I got was brilliant, more than what I thought I would get. About 6 months in, the project manager and lead dev left the company. Two replacements took their place, and life's been hell ever since.
The new PM decided it was his responsibility to be our spokesperson and started talking to our overseas manager (call her GM) on our behalf, even in the meetings where we were present, putting words in our mouth so that he's excellent and we get a bad rep.
1 month in, GM came to visit our location for a week. She was initially very friendly towards all of us. About halfway through the week, I realized that she had basically antagonized the entire old team members. Our responsibilities got redistributed and the work I was set to do was assigned to the new dev (call her NR).
Since then, I noticed GM started giving me the most difficult tasks and then criticizing my work extra hard, and the work NR was doing was praised no matter what. I didn't pay much attention to it at first, but lately the truth hit me hard. I found out a fault in NR's code and both PM and GM started saying that because I found it, it was my responsibility to fix it. I went through the buggy code for hours and fixed it. (NR didn't know how it worked, because she had it written by the lead dev and told everyone she wrote it).
I found out lately that NR and PM got the most hike, because they apparently "learnt" new tech (both of them got their work done by others and hogged the credit).They are the first in line to go onsite because they've been doing 'management work'. They'd complained to GM during her visit that we were not friendly towards them. And from that point on if anything went wrong, it would be my fault, because my component found it out (I should mention that my component mostly deals with the backend logic, so its pretty adept at finding code leaks).
What broke my patience is the fact that lately I worked my ass off to deliver some of the best code I'd written, but my GM said in front of the entire team that at this point "I'm just wasting money". She's been making a bad example out of me for some time, but this one took the cake. I had just delivered a promising result in a task in 1 week that couldn't be done by my PM in 4 weeks, and guess what? "It's not good enough". No thank you, no appreciation, nothing. Finally, I decided I'd had enough of it and started just doing tasks as I could. I'd do what they ask, but won't go above and beyond my way to make it perfect.
My PM realized this and then started pushing me harder. Two days back, I sent a mail to the team with GM in cc exposing a flaw in the code he had written, and no one bothered to reply (the issue was critical). When I asked him about it, he said "How can you expect me to reply so soon when it's already been told that when anything happens we should first resolve within the team and then add GM in the loop?" I realized it was indeed discussed, but the issue was extremely urgent, so I had asked everyone involved, and it portrayed him in a bad light. I could've fixed it, but I didn't because on the off chance if it broke something, they'd start telling me that I broke the tool, how its my fault and how its a critical issue I have to fix ASAP, etc. etc., you get the idea.
Can anyone give me some advice of how to deal with this kind of situation? I would have left but with this pandemic going on, market being scarce and the fact that I'm only experienced by 1 year, I don't think I qualify for a job switch just now.17 -
WHY THE FUCK DO YOU KEEP WASTING MY FUCKING TIME WITH POINTLESS MEETINGS ABOUT WHAT METHODOLOGIES YOU GONNA USE TO GET THE FUCKING DATA????
JUST GIVE ME THE FUCKING DATA AFTER YOU DISCUSS THIS SHIT AND TELL WHAT THE FUCK I HAVE TO DO WITH IT!!!
FUCKING WASTING MY FUCKING TIME AND WANTING SHIT TO BE DONE! WHAT THE FUCK!5 -
One of the dev in my team literally asked us (other student devs, professor, and a guy from the company we were working with) this question during a weekly scrum meeting:
"Who is this Jason you guys keep talking about? He never showed up to any of our meetings!".
A bit of context: we were 6 weeks (halfway) into our FINAL YEAR PROJECT for a bachelor in software engineering...
I thought at first he was joking...9 -
One of my top 10 worst meetings, was for an interview for a job I really wanted. The guy started off the technical interview by asking me about language features that had been replaced since before I started learning the language. Told him when I started learning and his reply was:
"Yeah I see that on your CV, but come on, you MUST know this stuff".
eh no asshole, because its been removed for 4 years, you MUST know its not relevant11 -
I've been working exclusively from home for over 2 years now. I've been seeing several posts from people talking about adjusting to working from home, so I figured I would compile a list of tips I've learned over the years to help make the adjustment easier for some people.
1) Limit as many distractions as possible. WFH makes it much easier to get distracted. If you have roommates/family members at home, ask them politely to leave you alone while you're working. Make sure the TV is turned off, put your phone on silent, etc.
2) Take regular breaks. I find it easier to accidentally go hours without taking a real break from work. Try working in half hour intervals, and then taking 5-10 minute breaks. Read an article, watch a youtube video, grab some coffee/tea, etc.
3) When you eat lunch, eat it away from your computer. I often find myself eating lunch trying to wrap up fixing a bug, which makes it feel like I never really "took a lunch." Lately I've been trying to step away and do something else completely unrelated to work.
4) Get ready for work like you normally would. It's very easy to wake up, throw on your favorite pair of sweats and sit at the computer with messy hair half awake "ready" to start the day. Instead try doing your normal morning routine before sitting at your computer. It will help your mind and body go into "it's time to work" mode.
5) Keep your work area clean. I find it very difficult to work when my workspace is cluttered. Studies have shown working in a messy place tend to make us less efficient.
6) Keep your work area work related. Try to only have the things you need for work in your workspace. If you're working from your personal computer this can be difficult. I always end up with camera/music equipment left over from the previous night's photo editing/jam sessions. So try to clean off your desk when you're done for the night so it's ready for work in the morning.
7) Prepare for meetings. I have alarms set 10 minutes in advance so I can go from programming mode to meeting mode. During this time I'll go to the bathroom, grab a snack, water, mute all my email notifications, close any non essential programs, get my code ready if I need to present it.
Stuff is hard & stressful right now, but hopefully these tips will make it a bit easier. If anyone else has any good tips please share them.5 -
I don't have _a_ most worthless meeting. I have a template. We have meetings like this frequently:
"Customer wants x, y and z done"
"Ok, do we have a data spec for x?"
"Not yet"
"Do we know what the output for y will be?"
"No, still in development"
"We can't really do z yet until we know more about x and y"
"True"
"Deadline?"
"Next week. Or sooner. Maybe later. We don't know yet"
At this point I usually think: And we're meeting now...why? -
The solution for this one isn't nearly as amusing as the journey.
I was working for one of the largest retailers in NA as an architect. Said retailer had over a thousand big box stores, IT maintenance budget of $200M/year. The kind of place that just reeks of waste and mismanagement at every level.
They had installed a system to distribute training and instructional videos to every store, as well as recorded daily broadcasts to all store employees as a way of reducing management time spend with employees in the morning. This system had cost a cool 400M USD, not including labor and upgrades for round 1. Round 2 was another 100M to add a storage buffer to each store because they'd failed to account for the fact that their internet connections at the store and the outbound pipe from the DC wasn't capable of running the public facing e-commerce and streaming all the video data to every store in realtime. Typical massive enterprise clusterfuck.
Then security gets involved. Each device at stores had a different address on a private megawan. The stores didn't generally phone home, home phoned them as an access control measure; stores calling the DC was verboten. This presented an obvious problem for the video system because it needed to pull updates.
The brilliant Infosys resources had a bright idea to solve this problem:
- Treat each device IP as an access key for that device (avg 15 per store per store).
- Verify the request ip, then issue a redirect with ANOTHER ip unique to that device that the firewall would ingress only to the video subnet
- Do it all with the F5
A few months later, the networking team comes back and announces that after months of work and 10s of people years they can't implement the solution because iRules have a size limit and they would need more than 60,000 lines or 15,000 rules to implement it. Sad trombones all around.
Then, a wild DBA appears, steps up to the plate and says he can solve the problem with the power of ORACLE! Few months later he comes back with some absolutely batshit solution that stored the individual octets of an IPV4, multiple nested queries to the same table to emulate subnet masking through some temp table spanning voodoo. Time to complete: 2-4 minutes per request. He too eventually gives up the fight, sort of, in that backhanded way DBAs tend to do everything. I wish I would have paid more attention to that abortion because the rationale and its mechanics were just staggeringly rube goldberg and should have been documented for posterity.
So I catch wind of this sitting in a CAB meeting. I hear them talking about how there's "no way to solve this problem, it's too complex, we're going to need a lot more databases to handle this." I tune in and gather all it really needs to do, since the ingress firewall is handling the origin IP checks, is convert the request IP to video ingress IP, 302 and call it a day.
While they're all grandstanding and pontificating, I fire up visual studio and:
- write a method that encodes the incoming request IP into a single uint32
- write an http module that keeps an in-memory dictionary of uint32,string for the request, response, converts the request ip and 302s the call with blackhole support
- convert all the mappings in the spreadsheet attached to the meetings into a csv, dump to disk
- write a wpf application to allow for easily managing the IP database in the short term
- deploy the solution one of our stage boxes
- add a TODO to eventually move this to a database
All this took about 5 minutes. I interrupt their conversation to ask them to retarget their test to the port I exposed on the stage box. Then watch them stare in stunned silence as the crow grows cold.
According to a friend who still works there, that code is still running in production on a single node to this day. And still running on the same static file database.
#TheValueOfEngineers6 -
SCRUMS ARE SUPPOSED TO BE 15 MINUTES, NOT FUCKING 1.5 HOURS
People who like hearing themselves talk shouldn't be in charge of meetings. We can't get the work done if you keep having meetings to talk about us getting the work done.6 -
I have seen it. They say it doesn't exist; just a story we tell our children so that their innocence does not lead them down into a nightmarish adulthood from which there is no salvation. But the evil lives. So vile that were you to look inside its soul, all you would find is a terrible desperation for suffering. To cause it. To revel in it. To bathe in the tears of those it considers less than human and feed off the emotional detritus.
It was 2009. The financial crisis. I was one of the lucky, having found refuge in a large company right before the jobs dried up. General IT: system administration, documentation, project management, telephony, software training, second level help desk. No software development, but with a two-year-old at home and Ph.D.s lining up outside the local Olive Garden whenever a help wanted sign was posted, I grabbed the health insurance and entered into darkness.
The Thing did not need to hunt it's prey. A manager title with 21 reports brought it new opportunities for fresh meat by the hour. But I was special. I resisted. I needed to know my place.
My first mistake was incomprehension. I did not understand the Thing's lust to be right at all costs. I was reviewing some documentation it had brought forth from its bowels. I mentioned that two spaces were being used between sentences. That proportional type made that unnecessary. It insisted, I was wrong. It insisted that Microsoft itself, the purveyor of all good technical writing, required two spaces. I opened the Microsoft Manual of Style for Technical Publications that it demanded its staff use and showed it that the spec was one space. It was livid. I was a problem.
From that point on my work life became exponentially more wretched. I was given three Outlook calendars to maintain: one with my schedule, one with the team's schedule and one with the Thing's schedule. Every time I had an appointment, I was to triple schedule it. If I was going to be away from my desk for more than 15 minutes triple schedule. Triple schedule my lunch, vacations, phone conferences.
Whenever it held a meeting, I and a colleague would be taken off mission critical IT projects to set tables with name tents and to serve as greeters as attendees arrived.
I was called into its crypt to be told never to say anything in a meeting unless I told the Thing beforehand what I was going to say. Naive, I mentioned that I often don't know what I will say as it is often in reply to someone else. Of course the response was that I should not say anything.
I would get emails 10-20 times a day asking about a single project. I would regularly complete work that was needed to be completed ASAP, only to have the Thing rake me over the coals for not completing it a week later. And upon resending the emails proving I notified it of the work being competed, disparaged at length a second time for not sending repeated notifications of the competed work.
I would have to sit in two-hour meetings to watch it type. Literally watch it try to create cogent thoughts. In silence.
I received horrendous annual reviews. At one, it created a development plan that stated a colleague would begin giving me lessons on the proper ways to socially interact with personnel. I pointed out to HR that this violated privacy concerns and would make the business liable in many areas, not least of which would be placing a help desk person in the role of defining proper business practice. HR made the Thing remove this from my review. She started planning to remove me.
I had given a short technical training to a group of personnel months earlier. Called into its tomb I was informed that feedback surveys on my talk were disturbing. One person stated that they did not think I was funny. Another wrote that I made an offensive statement. That person did not say what the offensive statement was. Just that I had said something he or she didn't like.
The Thing interviewed the training attendees. Gathered facts. Held three inquest-like meetings where multiple directors peppered me with questions trying to get me to confess to my offensiveness. In the end the request to fire me was brought to the man who ran the business at the time. The statement on high: "Humor is a subjective thing. Please tell This to be sensitive to that."
The Thing had failed, but would no doubt redouble its efforts. I had to find a new job. I sent hundreds of resumes. Talked to dozens of recruiters. But there were no jobs. And I had a family. And the wolf was at the door.
So I didn't say a word to the creature. For six months. Silence. At one group meeting it shrieked at me "what are you smirking at? If you've got something to say then say it!" I just shrugged. For my salvation was revealed. The Thing could not stand to be ignored. And at the end of my penance I was transferred to another group: Software Development.
I am one with the Force. The Force is with me. I am one with the Force. The Force is with me.4 -
My team has 1-on-1 check-up meetings with our boss about once a month.
My 1-on-1 today consisted solely of him saying "So I bought a new Porsche, want to see a picture?"
It was a pretty productive meeting, if I do say so myself!3 -
TL;DR :
"when i die i want my group project members to lower me into my grave so they can let me down one last time"
STORY TIME
Last year in College, I had two simultaneous projects. Both were semester long projects. One was for a database class an another was for a software engineering class.
As you can guess, the focus of the projects was very different. Databases we made some desktop networked chat application with a user login system and what not in Java. SE we made an app store with an approval system and admin panels and ratings and reviews and all that jazz in Meteor.js.
The DB project we had 4 total people and one of them was someone we'll call Frank. Frank was also in my SE project group. Frank disappeared for several weeks. Not in class, didn't contact us, and at one point the professors didn't know much either. As soon as we noticed it would be an issue, we talked to the professors. Just keeping them in the loop will save you a lot of trouble down the road. I'm assuming there was some medical or family emergency because the professors were very understanding with him once he started coming back to class and they had a chance to talk.
Lesson 1: If you have that guy that doesn't show up or communicate, don't be a jerk to them and communicate with your professor. Also, don't stop trying to contact the rogue partner. Maybe they'll come around sometime.
It sucked to lose 25% of our team for a project, but Frank appreciated that we didn't totally ignore him and throw him under the bus to the point that the last day of class he came up to me and said, "hey, open your book bag and bring it next to mine." He then threw a LARGE bottle of booze in there as a thank you.
Lesson 2: Treat humans as humans. Things go wrong and understanding that will get you a lot farther with people than trying to make them feel terrible about something that may have been out of their control.
Our DB project went really well. We got an A, we demoed, it worked, it was cool. The biggest problem is I was the only person that had taken a networking class so I ended up doing a large portion of the work. I wish I had taken other people's skills into account when we were deciding on a project. Especially because the only requirement was that it needed to have a minimum of 5 tables and we had to use some SQL language (aka, we couldn't use no-SQL).
The SE project had Frank and a music major who wanted to minor in CS (and then 3 other regular CS students aside from me). This assignment was make an app store using any technology you want. But, you had to use agile sprints. So we had weekly meetings with the "customer" (the TA), who would change requirements on us to keep us on our toes and tell us what they wanted done as a priority for the next meeting. Seriously, just like real life. It was so much fun trying to stay ahead of that.
So we met up and tried to decided what to use. One kid said Java because we all had it for school. The big issue is trying to make a Java web app is a pain in the ass. Seriously, there are so many better things to use. Other teams decided to use Django because they all wanted to learn Python. I suggested why not use something with a nice package system to minimize duplicating work that had already been done and tested by someone. Kid 1 didn't like that because he said in the real world you have to make your own software and not use packages. Little did he know that I had worked in SE for a few years already and knew damn well that every good project has code from somewhere else that has already solved a problem you're facing. We went with Java the first week. It failed miserably. Nobody could get the server set up on their computers. Using VCS with it required you to keep the repo outside of the where you wrote code and copy and paste changes in there. It was just a huge flop so everyone else voted to change.
Lesson 3: Be flexible. Be open to learning new things. Don't be afraid to try something new. It'll make you a better developer in the long run.
So we ended up using Meteor. Why? We all figured we could pick up javascript super easy.Two of us already knew it. And the real time thing would make for some cool effects when an app got a approved or a comment was made. We got to work and the one kid was still pissed. I just checked the repo and the only thing he committed was fixing the spelling of on word in the readme.
We sat down one day and worked for 4 straight hours. We finished the whole project in that time. While other teams were figuring out how to layout their homepage, we had a working user system and admin page and everything. Our TA was trying to throw us for loops by asking for crazy things and we still came through. We had tests that ran along side the application as you used it. It was friggin cool.
Lesson 4: If possible, pick the right tool for the job. Not the tool you know. Everything in CS has a purpose. If you use it for its purpose, you will save days off of a project.1 -
Some time ago I quit my job at a big corporation. Getting treated like a resource, a production line robot, just isn't for me.
My current job is way better. Small company, lots of freedom, getting to work on multiple projects, the result counts. But, as a small company, we also collaborate with big corporations. So I joined a team at one.
Watching my coworkers there, I'm reminded of robots again. Lunch break? 15 minutes tops. Just shovel some edibles into your face hole and back to work. Five minutes break between meetings? Open laptop, work work work. The concept of "needing rest" seems entirely foreign to them.
Yesterday our product owner "relayed some criticism" from other team members to me. Apparently, me going to the toilet in breaks is "suddenly disappearing". Or me not replying within 15 minutes in the chat is outrageous. And then he tried to berate me how I'm "his developer" and his team's tasks have top priority. So, according to the PO the problem is me and I should "get used to their mode of operation".
How about "no". I quit a fucking job because that "mode" is simply inhuman. After that feedback, you bet I'm taking my legally protected 30 minutes lunch break and any other break I can. Because fuck yourself, you're not going to burn me out. The best part, that team has smokers who "suddenly disappear" twice as much as I do, but apparently that's somehow a-ok.
I had to remind him that his project is just one of several I'm working on, so no, not "his dev". While that wasn't exactly a powerful comeback, it did shut him up. Still going to talk to my boss on Monday, at least to ensure that the PO can't talk shit about me behind my back.4 -
I posted a while back about a manager I had who vaped excessively indoors, during meetings, one on ones, etc. He was a total asshole. He was still a total asshole if you overlooked the strawberry scented Cape Canaveral act. This guy was good at CSS, I will give him that, but that's all he was good at. Couldn't comprehend basic JS, scared of jQuery, and would promptly shoot down ANY approach that didn't involve using WordPress. He was also one of the biggest power tripping egotistical know it all mother fucking pieces of shit and worst human beings in general that I've ever met. At least he had paint-by-numbers going for him.
We had a meeting with a client one day that wanted some kind of IRC thing with SMS support. I can't remember exactly what it was now, and it doesn't matter. I had been working on a slack-like clone for months at that point, and it was ok. It was a for-fun kinda thing. Not great by any stretch, but it worked. Mostly. I thought it might be a possible head start for the client's app, so I showed it to my manager.
I didn't get five words out before he's screaming and yelling in front of God and everyone. Customers, colleagues, the owner. "Don't work on anything without my permission ever again". I stood there, shocked. Actually couldn't speak for a couple of minutes. It was the same thing around the now very quiet and awkward open floorplan office. When words found me again, I turned to this sack of shit and said "I need to have a word with you in private". Long story short, I ended up walking out that day.5 -
Show up on time.
Be prepared.
Have a list of things that need to be covered if you're leading the meeting.
Stay on track, don't let people start talking out of one tangent, I tend to suggest people discuss it afterwards or email about it.
Take the meeting seriously, otherwise other people will not.
Know how to talk a language everyone understands. Sometimes people with key info just aren't very technical.
Following Ely's golden rules for meetings, my meetings are rarely longer than 20 minutes.5 -
Got this from boss (a few colleagues got it as well):
Sites have been down over the weekend and seems the only person cares is PM! There is a condition about working when required (i.e. unpaid OT) on your contract! It is essential that sites are properly managed even at weekends - we run a online business! If anyone has problems we'll discuss next week
*Note: site was partially down and there was no major impact on the business
When I explained why we need to rebuild the sites, you said not now - almost 2 years now, still nothing happens.
When I asked if we can get managed hosting or load balancer, fecking NO again
After asking for my opinion on the sites, you & the puppet think my honesty is me being negative and incorporate, and exclude me from meetings and major part of my work
Go fuck yourself! I've warned you about the status of the sites and you did not want to listen SO DON'T TELL ME I'M NOT DOING MY JOB WHEN YOU'RE THE ONE STOPPING ME FROM DOING IT PROPERLY!
I'm sure we'll have our meeting very soon, cheapskate.10 -
Another fucking rant about my fucking goldfish brain.
At meetings, I usually note down things I need to fix, to do on the sticky note pad that comes with the OS, currently Mint.
I sat at my desk.
Looked at my notes.
Decided to properly put them as tasks on trello.
I copied all notes, planning to paste it on a trello card quickly.
Then I can just work on trello and separate into different tasks.
Connection issue.
Ethernet said connected but websites are not showing up.
Maybe restart will fix since I haven't opened any app and started working anyway.
Reboot.
Internet works.
Yayyy.
Trello showed up.
Yayyy.
oooh
f
u
c
k.
fuck.
fuck.14 -
I'm fucking tired of this so called lead developer, lead developer my ass:
- He takes two days to complete a simple task and he dares to ask me why I extended the deadline of this freaking complex feature I need to build.
- He does a half-assed job when completes a task, no validation of data, no well informative message when exceptions are th thrown ...
- He assigns me his tasks although I already have tons and we need to release soon.
- I take care of developing and maintaining 60% of the APIs and I implemented the most complex of features and he dares to always say that my code can be optimized in a vague way, never mentioning what exactly is he talking about, and never telling me beforehand, he always does it during team meetings where another thing is being discussed.
- He presents the app to the whole company and at the end doesn't give credit where it's due, no " thank you for being part of this or helping build this" even if I built most of that shit, instead he says he's disappointed in me ... WTF! What did you fucking do to build this to be disappointed in me? I'm the fucking disappointed one here !!
- He fucking keeps preaching practices that he doesn't follow or he finds workarounds to skip them while the rest of the team follows them.
- He's like "I'm only taking care of this task to help you out?!" .... wtf! I have nothing to do with that fucking task, how are you helping me! You just keep fucking lazing around when we need to be finishing features asap.
Thank God I don't expect anything from you, I get enough credit from my boss who expresses how impressed he's with my job.8 -
Past 3 years I've been working 1pm-9pm instead of usual 8am-4pm at our company, no issues, I'm the only developer on the projects I work on, tasks delivered always on time, meetings with PM always afternoon, etc.
Few months ago company hierarchy changed and the new operative manager started to harass me about this with made up reasons (not working 8 hour or not working at all) and he doesn't care about the fact that my projects might be the only ones at the company that never missed a deadline. He even turned some of my colleagues against me.
So now I'm thinking about to quit this job and go freelance or find a remote job. Am I doing it right?7 -
I've just come back from a business networking event. There was a speaker who gave a talk about not wasting time.
On of her points was catching up on emails, from your smart whilst waiting to go into meetings, as that's apparently wasted time.
All I do whilst waiting to go into meetings is read devrant :)
It puts me in s good mood :)3 -
Productivity hacks:
1. Make sure the client understands that you wont be taking there BS.
2. Remind the client that the fact they know HTML means fuckall and that you wont be taking advice from them about all the javascript libraries you are supposed to use.
3. Tell PMs to be decisive and think before making decisions.
4. Fuck windows updates. Use linux/mac.
5. Keep a loaded gun on your desk to deter any person from disturbing you when you are in your zone.
6. Use the gun to end pointless meetings to decide the background color of some div on the website.
Use at your own caution though.6 -
This is something that happened 2 years ago.
1st year at uni, comp sci.
Already got project to make some app for the univ that runs in android, along with the server
I thought, omg, this is awesome! First year and already got something to offer for the university 😅
(it's a new university, at the time I was the 2nd batch)
Team of 12, we know our stuffs, from the programming POV, at least, but we know nothing about dealing with client.
We got a decent pay, we got our computers upgraded for free, and we even got phones of different screen sizes to test out our apps on.
No user requirement, just 2-3 meetings. We were very naive back then.
2 weeks into development, Project manager issues requirement changes
we have a meeting again, discussing the important detail regarding the business model. Apparently even the univ side hadn't figure it out.
1 month in the development, the project manager left to middle east to pursue doctoral degree
we were left with "just do what you want, as long as it works"
Our projects are due to be done in 3 months. We had issues with the payment, we don't get paid until after everything's done. Yet the worse thing is, we complied.
Month 3, turns out we need to present our app to some other guy in the management who apparently owns all the money. He's pleased, but yet, issued some more changes. We didn't even know that we needed to make dashboard at that time.
The project was extended by one month. We did all the things required, but only got the payment for 3 months.
Couldn't really ask for the payment of the fourth month since apparently now the univ is having some 'financial issues'.
And above all: Our program weren't even tested, let alone being used, since they haven't even 'upgraded' the university such that people would need to use our program as previously planned.
Well, there's nothing to be done right now, but at least I've learned some REALLY valuable lesson:
1. User Requirement is a MUST! Have them sign it afterwards, and never do any work until then. This way, change of requirements could be rejected, or at least postponed
2. Code convention is a MUST! We have our code, in the end, written in English and Indonesian, which causes confusion. Furthermore, some settle to underscore when naming things, while other chooses camel case.
3. Don't give everyone write access to repository. Have them pull their own, and make PR later on. At least this way, they are forced to fix their changes when it doesn't meet the code convention.
4. Yell at EVERYONE who use cryptic git commit message. Some of my team uses JUST EMOTICONS for the commit message. At this point, even "fixes stuffs" sound better.
Well, that's for my rant. Thanks for reading through it. I wish some of you could actually benefit from it, especially if you're about to take on your first project.3 -
Fucking teammate who did not know how to read/write a simple class diagram.
We warned him that he have to study or we just kick his fucking ass out of the team.
He just did nothing. When we had meetings he just stayed at home pretending to have an heart issue needing surgery.
After just 2-3 days he was tagged on FB in a photo shooted a few days earlier where he was riding a bike for a competition.
He skipped another scheduled-a-fucking-week-before meeting saying that he was on a surprise trip, when I called him 5 minutes before meeting start.
In the end we just kick him out because he did nothing. He went to professor talking about some relationship problem in the team and asked him if he could continue the project by himself just forking the ours.
Professor said HELL NO SON OF A BITCH.
But our team learned a precious lesson : choose your team carefully.5 -
I was engaged as a contractor to help a major bank convert its servers from physical to virtual. It was 2010, when virtual was starting to eclipse physical. The consulting firm the bank hired to oversee the project had already decided that the conversions would be performed by a piece of software made by another company with whom the consulting firm was in bed.
I was brought in as a Linux expert, and told to, "make it work." The selected software, I found out without a lot of effort or exposure, eats shit. With whip cream. Part of the plan was to, "right-size" filesystems down to new desired sizes, and we found out that was one of the many things it could not do. Also, it required root SSH access to the server being converted. Just garbage.
I was very frustrated by the imposition of this terrible software, and started to butt heads with the consulting firm's project manager assigned to our team. Finally, during project planning meetings, I put together a P2V solution made with a customized Linux Rescue CD, perl, rsync, and LVM.
The selected software took about 45 minutes to do an initial conversion to the VM, and about 25 minutes to do a subsequent sync, which was part of the plan, for the final sync before cutover.
The tool I built took about 5 minutes to do the initial conversion, and about 30-45 seconds to do the final sync, and was able to satisfy every business requirement the selected software was unable to meet, and about which the consultants just shrugged.
The project manager got wind of this, and tried to get them to release my contract. He told management what I had built, against his instructions. They did not release my contract. They hired more people and assigned them to me to help build this tool.
They traveled to me and we refined it down to a simple portable ISO that remained in use as the default method for Linux for years after I left.
Fast forward to 2015. I'm interviewing for the position I have now, and one of the guys on the tech screen call says he worked for the same bank later and used that tool I wrote, and loved it. I think it was his endorsement that pushed me over and got me an offer for $15K more than I asked for.4 -
Recap: https://www.devrant.io/rants/878300
I was out Thursday at the Hospital. I'm what the doctors would call "Ill as fuck"
So, Friday I’m back in the office to the usual: "How was that appointment?"
I know people mean well when they ask this. So, I do the polite thing and tell them it went as well as it could.
Realistically it does't matter how well it went... They haven't cured Crohn's because I showed up to the appointment. They know I'm fucked already.
But, push it down, add it to the future aneurism.
I had to go through the usual resignation meetings with managers:
"We"re fucked now you're going"
"yep"
"we need to get a handle on how fucked"
"already done that for you, here"s a trello board, very fucked."
"we need to put a plan together to drop all the junior devs in the shit with the work you’ve been doing"
"You need about 4 devs, please refer to the previous trello board for your plan"
Meanwhile, me and Morpheus are in constant communication because all of this is like a Shakespearean comedy.
So, I overhear a conversation between a Junior Dev and the Solution Architect.
[SA] took over the project because he knows better than two tried and tested senior devs -_- (fuckwit).
JD: "It took me one and a half days to build it out"
SA: "Yeah, it must have taken me twice as long... It must be a problem with the project, you should just be able to check it out and run it."
JD: "I know, it has to be wrong"
All of this is about Morpheus' work of art, of an Ionic 3 hybrid app.
I fumed quietly at my desk because I've been ordered by the Stazi to be hands off.
Since Morpheus and me were pulled from the project [JD] and [JD2] were dropped into it to get it over the line.
It"s unfortunate and I was clear and honest with my advice to them: I personally would not take over the project because I"d be way out of my depth... Oh, and the App works, so uh, there's no work to do.
They have been constantly at our desks. Asking fuckdiculous questions about how to perform basic tasks. So they can get Morpheus" frigging masterpiece to the user.
It"s like watching that touch up of jesus that got borked by an amateur. Shit I have google, it's like watching this happen: http://ti.me/NnNSAb
[JD] came to me Friday evening.
"I can’t get this to build to iOS or install on [Test Analyst]'s phone."
Me: "No worries brother, where are you stuck right now?"
[JD] describes the first steps with clear indication he hasn't googled his problem.
Life lesson: http://lmgtfy.com/?q=lmgtfy
Que an hour of me showing [JD] how to build an Ion3 project for iOS. Fuck it, your man's in a bind and he"s asked politely for help. I can show him quicker than he can read 3 sets of docos.
I took him through 'ionic cordova build ios', the archive and release processes in XCode 9, then the apk bundling process for droid. Finally we have an MAM so the upload process for that too.
All the while cleaning up his AppIDs, Profiles, deployment attempts.
Damn they were a mess.
I did this with a smile on my face, not because I could say "I told you so"... But. because when any developer asks you how to do something. If you know how to do it, you should always be happy to learn them some new tricks!
Dude's alright, he's been dropped in the shit. Now I know how badly so I'll help him learn things that are useful to his role, but aren't project specific.
As a plausi-senior dev (I'll tell you about that later); it's my job to make sure my team have what they need to go home smiling!
I’m not a hateful fucker, the guy asked me an honest question so I am happy to give him the honest answer.
I took him through it a few times and explained a few best practices. Most were how to do his AppID and ProvProfile set up. Good lad, took it all on board.
However! In his frustration, he pointed the finger at Morpheus' "David" (ref: Michelangelo).
He miraculously morphed into a shiny colourful parrot and fed me SA's line:
"you should just be able to build from a clean clone"
My response was calm and clear:
"You can, it took me 20 minutes on Thursday evening. I was bored and curios, so I wanted to validate Morpheus' work. Here it is on my iOS device and my Android device. It would have taken me 5 if my laptop wasn’t so horrifically out of date."
I validated Morpheus' work so I have evidence, I trust that brilliant bastard.
I just need to be able to prove it's good.
[JD] took this on board.
Maybe listening to two tried and trusted senior devs is better than listening to a headstrong Solution Architect.
When JD left for the weekend I was working a late one (https://www.devrant.io/rants/874765).
His sign off was beautiful.
"I think I can happily admit defeat on this one, it can wait until Monday."
To which I replied: "no worries brother, if you need a hand give me a shout."
Rule 1: Don't be a cunt.
Rule 2: If someone needs help and you can give it: Give it!
Rule 3: Don't interrupt James' cigarette time.
Rule 4: goto Rule 3.rant day 3 jct resigns crohns resignation solution architect wk71 invisible illness fuckwit illness junior developer4 -
Be good at job, have lazy coworkers who can't be bothered getting into the project. End up developing most of it. End up having to do client meetings as well because you've come to be the only one who knows how it works. Start to get tired after being relied on for everything. Be pressured to work late because now you're the only one who can fix it... Other devs just tinkering around the edges. Get refused leave requests because deadline after deadline. Work morning till night feeling increasingly burned out, Covid curfew means you can't even leave the house during the week, start to go insane. Leave request refused again. Ok I haven't had any time off in a while year now. Fuck this. Quit. Company sorry, try to keep you. How about no.9
-
Overheating The Javascript Ecosystem
Paranoid thought: You know, in the course of every day, being the corrupt piece of shit that I am, whenever I see a scandal or what looks like shenanigans-in-the-making, I ask myself
"Wisecrack, is this a fucking scam or con of some sort?"
I was recently asking myself this about javascript.
Not the language per se, but the ecosystem.
I noticed how there are a thousand CLIs for simple shit. Another four thousand for page long libraries, for simpleton level shit (because prototypes are designed after satans own aborted love-child of object models). I noticed another eight thousand guys imitating steve jobs, talking at conferences and 'change the world' high-on-huffing-my-own-shit TEDX talks like rubyists that don't realize the world has moved on, all to hawk books and inflate CVs for cushy positions at major tech firms and the herd of dicksuckers following the next fad off a cliff like lemmings. And another eight thousand 'tech journalists' pushing them off the cliff while begging for outrage and hype dollars and slowly circling like vultures above the drain that is the ad-based economy.
And I thought to myself.
"Wisecrack, who benefits from all this noisy self-indulgent horseshit? Where is all the money coming from for all these books, conferences, meetings, publications, media, bread, and circuses?"
"I don't know wisecrack. But if I were the CEO of a big company, threatened by the prospect of a universal language, or universal platform, like flash, but one I couldn't kill like flash, I would try to do the most corrupt thing I could think of."
"Whats that wisecrack?"
"I would try to 'overheat' the ecosystem by selectively hiring people from that ecosystem, pumping money into a boatload of similar products, all in the hopes of provoking the equivalent of an immune overreaction, imitators all flooding the ecosystem with the same shit in different packages, self promoting sycophants, aggrenadizing social media idiots, tools sold as tools, hyped as 'the next coming of steve jobs', overcooked shit that focuses on ceremony over functionality, ritual over productivity, documentation over innovation like some sort of amazonion infinite nesting doll hellscape of documents linking to documents linking to documents, each one a new circle of dantes inferno, where the definition of anything links to another document that says "see also xyz", and I would convince them that they had done it to themselves."
And then I would push typescript as their lord, savior, and master. "
"How do you know all this wisecrack?"
"Because I am a piece of shit, and, this is what I would do in any executive's shoes."11 -
There are three things in my workflow that I don't like:
1. Feature requests appearing out of thin air.
It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!
2. Not being asked about estimates.
Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).
3. Being the last part of the product development process.
Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.
This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?
I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.6 -
Meetings about meetings that we're going to have to discuss the need for the next meeting wherein a potential followup meeting will be scheduled to meet for the meeting.3
-
(Best read while listening to AEnima by Tool, loudly)
Dear Current Workplace,
Fuck you, for the reasons enumerated below.
Fuck your enterprise grey blue offices, the stifling warm air of a hundreds of bodies and sub par "development laptops".
Fuck your shitty carbonated water machines which were a cost saving measure over decent drinkable water.
Fuck your fake "flexi time", "you can do home office whenever you want" bullshit. You're still inviting me to mandatory meetings at 09:00 regularly.
Fuck your shitty, in house, third part IT provider sister company. They're the worst of all worlds. If it was in company, we'd get to give out to them, if it was an external company we'd fire them. And yes, when I quit I will quote the dumpster fire that is our corporate VPN as a major factor.
Fuck your cheery, bland, enterprise communication. Words coming under the corporate letterhead seem to lose all association with meaning. Agile, communication, open are things you write and profess to respect, but it seems your totally lack understanding of their meaning.
Fuck your client driven development. Sometime you actually have to fix the foundations before you can actually add new features. And fuck you management who keep on asking "why are there so many bugs and why is it always taking longer to deliver new releases". Because of you, you fucknuts, Because you can't say "NO" to the customer. Because you never listen to your own experienced developers.
Fuck your bullshit "code quality is important to us" line. If it's so important, then let us fix the heap of shit you're selling so that it works like a quasi functional program.
Fuck you development environment which has 250 projects in a single VS solution. Which takes 5mins plus to compile on a quad core i7 with 32 gb of ram.
Fuck this bullshit ball of mud "architecture". I spend most of my time trying to figure out where the logic should go and the rest of the time writing converters between different components. All because 7 years ago some idiot "architect" made a decision that they didn't have to live with.
Actually, fuck that guy in particular. Yeah, that guy who was the responsible architect for the project for 4 years and not once opened the solution to look a the code.
Fuck the manual testing of every business process. Manual setup of the entities takes 10mins plus and then when you run, boom either no message or some bullshit error code.
Fuck the antiquated technology choices which cause loads of bugs and slow down development. Fuck you for forcing me to do manual tests of another developers code at 20:00 on a Friday night because we can't get our act together to do this automatically.
Fuck you for making sure it's very clear I'm never going to be anything but a code monkey in this structure. Managers are brought in from outside.
Fuck you for being surprised that it's hard to hire competent developers in this second rate, overpriced town. It's hard to hire anywhere but this bland shithole would have anyone with half a clue running away at top speed.
Fuck you for valuing long hours and loyalty over actual performance. That one guy who everyone hated and was totally incompetent couldn't even get himself fired. He had to quit.
Fuck you for your mediocrity.
Fuck you for being the only employer for my skill-set in the region; paying just well enough that changing jobs locally doesn't make sense, but badly enough that it's difficult to move.
Fuck you for being the stable "safe" option so that any move is "risky".
Fuck your mediocrity.
Fuck you for being something I think about when I'm not at work. Not only is it shit from 9 to 5 you manage to suck the joy out of everything else in my life as well?
Fuck you for making me feel like a worse developer every day I work here. Fuck you for making every day feel like a personal and professional failure. Fuck you for making me seriously leave a career I love for something, anything else.
Fuck you for making the most I can hope for when I get up in the morning is to just make it until the night.6 -
I don't know why the fuck the manager from the other team keeps trying to involve me in his project. He has his own developers, it's their codebase and they know it better, and yet if he finds something so little that he can associate to our team, he drops my name. Why? My life has been so peaceful for a month. The stress from reliving this traumatic assignment will lower down my immune system and I'm gonna die from corona. The virus would just be like, "Yeeaaah, this bitch wanna die right now. Let's fuck this up real good."
I spent the entire February bitching about this team who borrowed me. Even after my assignment with them, their codebase (see recent rants) followed me to my original team. At least it was fine because we forked it and we'll be handling it in the future, meaning:
- I can clean it up.
- I don't have to subject myself to their stupid fucking stand-ups that last more than an hour because no one knows how to update their Jira tickets.
- I don't have to be talked down to or endure sudden power-trips from one of their asshole developers who revel on the fact that he knows the maze more than I do.
- I don't have to perform their hacks to make shit work.
- I don't have to work on unsupported bundled libraries for Python 2. I do not know why the fuck you keep using that shit or starting new projects with that shit when it's long expired.
- I don't have to turn on my webcam during meetings.
- I don't have to be accused of being a snob for not responding to messages in group chats that I'm not even a member of.
- Many more.
But this guy, fuck this guy. I'm already done with that module and it was transitioned to his developer before I went on vacation. I did not hear any more questions for a month. Even if he asks me questions now, I wouldn't mind answering them, just please don't involve me in this type of hell anymore. I still remember the time your team forgot to develop the user interface and I had to take shit, as a back-end developer, that it's somehow my fault (see old rants).
Oh god, no. You have to let me go. If you just want that module disabled for other users, your team can do it. It would be really quick. It's like the easiest part. I don't want to do the hacks you did to make the libraries work EVER AGAIN. I don't want to spend another week of my life setting up that shit and guessing where things are.
It makes no fucking sense. You have your own developers. One of them even told me they can do it. Even way before that assignment, we agreed (and I don't take offense from this) that it would be a lot easier if someone from your team did it instead of me.
I have a bad feeling about this. If you have plans of adopting me, I will hang myself.
I'm just so fucking tired. Arrrrrrrrrrrrrggggggghh.rant let me go freedom this is attempted murder let me go! let me fucking go please stop it give me freedom5 -
So I studied for a long time about scrum, convinced my boss, his boss and our team to consider it, everyone liked it but seems to don't understand it very well.
I organized meetings about it and everything...
This week the majority of our team will attend a Google event about scrum in another city.
Guess who is not going?11 -
In the last project i worked in, the product owner wouldn't treat people as people but as resources.
The problem with that is you just look at people and their work in terms of a checklist and remain blind about real humans face.
She wouldn't understand the challenges of building something with an absolutely new stack which people needed to learn from scratch and put pieces together. She wouldn't be supportive of people trying out things and fail.
One fine day I told her that I was spending too much time on meetings and i should be excluding that time from available sprint timings.. she made me open my calendar in a screenshare session with all team members. Made me go through go through every meeting invite i had on calender and ordered which ones should i be attending from then and which ones i wont. That was insulting. It broke the trust.
I decided to not work with the project. Stopped putting my heart and soul into it and eventually got out of it in a month time.
Don't put your team into a position like this ever. You have to trust them with the problems they face and try to find a solution. Scrutinizing and micro management will always kill the team.1 -
Finally after one year I understood how to carry out my job. I should do exactly NOTHING. I stopped completely organizing the team, solving bugs, helping the team developing and solving problems, explore and try stupid things said by CEO, PM and consultants.
I stopped for 2 months now and nothing happened.
I work remotely, nobody knows if I'm working or not, because nobody cares really about priorities, bugs, customers or products development.
I gain 10K$ (ten thousand) per month.
I attend skype meeting once per week or less. I say yes to everything, nobody gives a shit to what I say, even if they consider me the technical director. Actually in the meetings I only take care of being considered the technical director.
I achieved the mythical 4 hours working week.
I keep skype open in all my devices in order to answer promptly in case of problem, wherever I'm am, that's the most important thing right now.
I attended some meeting from the toilet or from the bedroom.
It was hard. To understand that the board is only after the next funding and not looking to develop a real product. It's hard to pretend helping people while thinking inside you "fuck you".
You have to let go the "guilt": if you can't login, I KNOW that is my fault, that there is a bug, that is possible to solve it, that resources and planning are needed etc. That's guilt. Just let go and say "next release" and never include it in the next release.
In this way I discovered that some users are paying the application even if they can't login.
The company is not going to disappear in the next 5 years. On the contrary, it's going to receive more money.
So the only "bad" thing is, what will I write in my CV in 5 years?20 -
I rewrote my resume. It is getting shorter and shorter. Scary.
But I was thinking, that during interviews, I never get to ask the important questions. Like, I do need to ask a few things that are important for me. Those that are not written in their websites, and they will do their best to hide.
So I came up with a list of questions:
1. Do you pay for overtime work? what is the basis of pay? hours or work-module? how realistic are the work-modules?
2. Have you ever had issues with employees from minority groups?
3. How do you address employee's professional concerns? for example, about technological debt.
4. what's the policy for meeting and daily interruptions during brain-work? Are people ever forced to participate in meetings that could be summed up in emails? what's the company policy for initiating a meeting?
5. Who designs the software? Are the requirements always non-negotiable? do the direct developers have a say in design matters?
6. How close are job requirements (as advertised) to actual tasks I need to perform?
7. What's the company policy for motivating the employees?
8. How does the company deal with mental health issues? is it acceptable for people to take leaves due to mental health issues? Has anyone ever done it?
9. How does the company deal with individual needs for working methods and space? Specifically, how does that apply to meetings? Do you have company-wide meetings? How often are they? What's the impact on productivity? Can employees not participate? Do they have to have an excuse to not participate?
10. Do developers get to develop their skills during worktime often? Or is it a "do it in your own free time" kind of thing? Are there any resources available to those who want to develop their skills further? Is it included in the career planning and employee performance review?
11. Assume I work for your company for a year. What are the benefits I can potentially gain in a year from working here, aside from adding a line of work experience to my resume?
12. Does the company provide any form of free feminine hygiene products in the bathroom?
Any questions I should add?94 -
As a Java developer I didn't write a line of code at work for about 2 months. Been so busy with meetings, doc, governance, architecture decisions, running after people for approvals,... I really miss coding.2
-
rant.GetType() == typeof(long)
I have voiced my unhappiness to the powers that be regarding having to sit in traffic for over an hour to get to work and an hour to get back home, in the hopes that some sort of resolution and compromise can be reached.
The response basically was, "We've never had anyone work from home before and this is very new to us, so we wouldn't know where to start and how to manage this."
Firstly, from what I've heard along the grapevine, someone has worked from home before. In fact, it was a developer... wouldn't you fucking know!
Secondly, you're the manager... FUCKING MANAGE! Yes this is perhaps "new" territory for the company, but it's certainly nothing new to the world. Or maybe I'm wrong?
How's about, rather than fucking "ummm-ing" and "ahhh-ing" about the working from home being a good idea or not, perhaps try saying, "You know what, let's try something for the next 3 months and see how it goes. We sit down and hash out when and how we are going to communicate regarding the work that needs to be done, and when you will need to come in for meetings and the like." If it doesn't work after 2 weeks, oh well... we tried. And if we're still going strong after month 4, I think we have a winner!
Perhaps it's a generational thing, seeing as management are Baby Boomers and I'm a Millennial? Then again, I could be wrong.
The point is that I see a potential solution to my problem that may actually work and benefit both parties, but they're either to fucking set in their old ass ways and stubborn to allow this. Or perhaps it's a thing of "if we do this for you, we have to do it for everyone", which they don't want to do.
But more importantly, they don't seem to get the whole notion of "a happy employee is a productive employee".6 -
Never had one due to this trick I borrowed from an old friend.
So we all know about those meetings where its all crap flying around right?.
First go in there with your alarm clock set on vibration every 7 minutes(trust me on this-makes you look important and you ought to be somewhere else)
Actually the alarm is a reminder that you need to bring yourself back online.
At this point just listen to the speaker for a couple of seconds(especially if its marketing dept) and being the engineer your are; rephrase parts of their presentation in a question-comment hybrid( at this point you're the wisest looking person in the room)
Now go back to thinking about that pizza slice you left in the fridge as they discuss the "lean production" methods that they can use based on "your opinion"..
To more happy meetings..cheers3 -
20+ years ago we got a contract to replace an old home grown system for managing rented equipment for a company with offices in two countries with a new standard system.
I was tasked with building a few addon modules to handle import and reporting that the standard system lacked.
Over the course of 8 months and multiple trips to their head office for on premises development along side their people that knew how it should work (there was a lot of waiting for info so it was not 8 months of actual work) we finally was ready to present the finished solution.
After about one hour of demonstration their boss questioned why we did not demonstrate the connection to their corporate group accounting system ...
“Corporate group accounting?”
After some confused discussion it turns out that in one of the first meetings the sales person had they had mentioned this accounting system and that all accounting info was to be exported there.
This requirement was never listed in the specifications we got and looking into it it turned out that the standard system did not support such exports at all.
In the end we had to throw it all away as it proved impossible to get that info out of the system (which was not of our design).
We barely avoided having to repay all fees as their people had approved the specification but standing there without a clue to what he was asking for was a very scary experience, thinking “how could we miss this?”2 -
A couple of months back we were discussing sh with a third party vendor for a very large ass fuck system that another department uses. I had been called into the meeting because the entire I.T department counts on me to at least act as an assessor to the many issues that other departments might have.
the department for which i was working with manages the databases that our institution uses, and in this particular question the DBA (my best friend mind you) was part of the meeting.
Mind you, issues that the third party vendor were having were all fixed by our DBA, and he had documented and mentioned these items to me as I provided assistance to him through the 3 weeks prior to this meetings. Once such case was that we needed a transitioning as well as intermediary system for some processes to happen from one DB to the other and a lot of other technical babble. Well, the DBA used to be an excellent (fuck you) VB developer who recently re-learned the language into .net. He had shown me many of his old programs and even by the limitations of the language they were elegant and fascinating. They really are and ya'll devrant fam know that I ain't one to hate on tech at all.
When the DBA explained how he went around some of the issues by generating programs that could assist him, he mentioned the tech stack, I had coached him into knowing that being descriptive about the tools he used would be beneficial to everyone else. While he mentioned VB.NET the vendor snickered and my boy got quiet.
Then I broke the silence, fuck you. "what was that?" and the dude said "nothing, sorry"
So I said "no no, I want to know, I am not going past this point until you, the dude getting paid over $100 an hour for something YOU couldn't fix explain to me the little hehe moment you had"
The mfker went silent. then explained how he was aware that people were moving past vb.net and shit like that, me "imagine that, someone used a tech stack that your ignorance thought obsolete to fix something you could not solve, even though we are paying you for it, were it me or in my hands, and mind you i have direct access to the VP so this foolishness might change, I would have cut you and your little sect loose months ago, I have no patience, or appreciation from leeches like you or the rest of the "professionals" that work for your company or other similar entities, much less, as you can see, my patience runs even less when you people snicker at the solutions that our staff has to take when you all slack"
The entire meeting was uncomfortable as high heaven.
Fuck you, if someone I know manages to run shit on fucking liberty basic then so fucking be it. I will slap you 10 fucking times over, and then fuck your girl, if you try to put someone else down for the tech stacks you use.
I hate neck beards, BUT I hate fake ass neckbeards ever more
*Colin Farrell in true detective mode: FUCK....YOU13 -
Disclaimer: Long tale of a tech support job. Also the wk29 story is at the bottom.
One time I was working tech support for a website and email hosting firm that was in town. I was hired and worked as the only tech support person there, so all calls came in through me. This also meant that if I was on a call, and another one came through, they would go straight to voice mail. But I couldn't hang up calls either, so, sometimes someone would take up tons of time and I'd have to help them. I was also the "SEO" and "Social Media Marketing" person, as well; managed peoples' social media campaigns. I have tons of stories from this place but a few in particular stick out to me. No particular order to these, I'm just reminiscing as I write this.
I once had to help a man who couldn't find the start button on his computer. When I eventually guided him to allowing me to remote into his computer via Team Viewer, I found he was using Windows XP. I'm not kidding.
I once had to sit on the phone with a man selling Plexus Easy Weight Loss (snake oil, pyramid scheme, but he was a client) and have him yell at me about not getting him more business, simply because we'd built his website. No, I'D not built his website, but his website was fine and it wasn't our job to get him more business. Oh yeah, this is the same guy who said that he didn't want the social media marketing package because he "had people to hide from." Christ.
We had another client who was a conspiracy theorist and wanted the social media marketing package for his blog, all about United States conspiracies. Real nut case. But the best client I've ever had because sometimes he'd come into the office and take up my time talking at me about how Fukushima was the next 911 and that soon it'll spill into the US water supply and everybody was going to die. Hell, better than being on the phone! Doing his social media was great because he wanted me to post clearly fake news stories to his twitter and facebook for him, and I got to look at and manage all the comments calling him out on his bullshit. It was kinda fun. After all, it wasn't _me_ that believed all this. It felt like I was trolling.
[wk29] I was the social media and support techie, not a salesperson. But sometimes I was put in charge _alone_ in front of clients for status meetings about their social media. This one time we had a client who was a custom fashion-type person. I don't really remember. But I was told directly to make them a _new_ facebook page and post to it every day with their hot new deals and stuff. MONTHS pass since I do that and they come in for a face-to-face meeting. Boss is out doing... boss things and that means I have to sit in with her, and for some fucking reason she brought her boyfriend AND HER DAD. Who were both clearly very very angry with me, the company, and probably life. They didn't ever say anything at first, they didn't greet me, they were both just there like British royal guards. It was weird as fuck. I start showing them the page, the progress on their likes goals, etc etc. Marketing shit. They say, "huh, we didn't see any of these posts at home." Turns out they already had a Facebook page, I was working on a completely seperate one, and then the boyfriend finally chimes in with the biggest fucking scowl, "what are you going to do about this?" He was sort of justified, considering this was a payed and semi-expensive service we offered, but holy shit the amount of fire in all three of them. Anyway, it came down to me figuring out how to merge facebook pages, but they eventually left as clients. Is this my fuck up? Is it my company's? Is it theirs? I don't know but that was probably the most awkward meeting ever. Don't know if it comes across through text but the anxiety was pretty real. Fuck.
tl;dr Tech support jobs are a really fun and exciting entry level position I recommend everybody apply for if they're starting out in the tech world! You'll meet tons of cool people and every day is like a new adventure.2 -
The exit interview with an ex boss.
While working there, we had regular meetings every other week. Discussing current work, equipment requests, technology, sometimes office politics. At some point we discussed that our team was moved to an open-plan office and how I regarded this as detrimental to our productivity and satisfaction. Of course we sometimes had different opinions, but it was an amicable atmosphere. My boss also always carried a personal organizer and sometimes wrote notes during these meetings.
Later I resigned. Him becoming more and more abusive was a major reason, and I think he knew he had crossed a line. So the day of the exit interview came...
In a professional setting, you'd thank each other for the good collaboration. Maybe laugh about one or two points from the past. And then wish each other success for the future and say farewell.
Not there. Not with him in the exit interview.
Instead, he apparently went through a list in his personal organizer. A list of every single thing we ever disagreed at. And roasted me for each. single. item. "Back when you said x... you can't really say it like that". Or "remember that time when you were against open-plan offices? Let me tell you, that's just your opinion. There are no actual arguments against them, it's just a matter of taste". And that went on and on and on. Like a final reckoning. Like he needed to get revenge. I hope that carnage made him happy, because it made *me* happy to have had resigned.
And it was fucking unprofessinal, because this is the management equivalent of stomping your foot in rage and anger, shouting "no no nooo I'm right! I! am! Riiiiiiight! *stomp*".6 -
When I was at university in my last semester of my bachelor's, I was doing a game programming paper and our last assignment was to group up and make a game. So I go with one of the guys I know and this other dude since his previous game was really neat. Then two randoms joined that from my first impressions of their games wasn't much at all (one guy made four buttons click and called it a game in Java when we had to make games in c++ and the other guy used an example game and semi modded it.
Anyways we get to brain storming, totally waste too much time getting organised because the guy that volunteered (4 buttons guy) was slow to getting things sorted. Eventually we get to making the game and 4 buttons guy hasn't learnt how to use git, I then end up spending 3 hours over Skype explaining to him how to do this. He eventually learns how to do things and then volunteers to do the AI for the game, after about a week (this assignment is only 5 weeks long) he hasn't shown any progress, we eventually get to our 3rd week milestone no progress from him and the modder, with only three classes left we ask them both to get stuff done before a set deadline (modder wanted to do monsters and help 4 buttons with AI) both agreed and deadline rolls up and no work is shown at all, modest shows up extremely late and shows little work.
4 buttons guy leaves us a Skype message the day of our 2nd to last class,, saying he dropped the paper...
Modder did do some work but he failed to read all the documentation I left him (the game was a 2d multiplayer crafting game, I worked so hard to make a 2d map system with a world camera) he failed to read everything and his monsters used local coordinates and were stuck on screen!
With about a week left and not too many group meetings left we meet up to try and get stuff done, modder does nothing to help, the multiplayer is working my friend has done the crafting and weapon system and the map stuff is working out well. We're missing AI and combat, with our last few hours left we push to get as much stuff done, I somehow get stuck doing monster art, AI is done by the other two and I try to getting some of the combat and building done.
In the end we completely commented all of modders work because well it made us look bad lol. He later went to complain to my free claiming I did it and was a douchebag for doing so. We had to submit our developer logs and the three of us wrote about how shitty it was to deal with these two.
We tried out best not to isolate ourselves from them and definitely tried to help but we were swamped with our other assignments and what we had to work on.
In the end leaving and not helping right when the deadline is close was what I call the most shittiest thing team mates can do, I think sticking together even if we were to fail was at least a lot better.3 -
I really hate to have a non-technical Scrum Master...
He makes these long meetings to explain EVERYTHING to him and ask us help to be on meetings with clients in case "he over commit us" with more work.
I've had cool Scrum Masters but not like this dude that is a pain in the ass...
PS. he's good friend of the boss... so I'm sending him videos about what his role should do 😕
PS2. Fourtunately, he's about to be switched to another project soon.5 -
First day back. I am a junior Dev a year and a half of work.
I get in after Christmas break and find people standing around my desk turns out all senior staff (except CEO and PM who are both non-technical ) are away and an email. Basically saying it's up to me for the next week to manage people.
FU&£&# what the heck I don't have a clue what I am doing and I can't mange if I could I would be a manager pays better. So I designate to people took me an hour to figure out what people can actually get on with. Then PM wants a break down of the plan. Then meeting with CEO over the importance of these projects and told 'politely' shortest deadline to date most work, get it done the company depends on these projects if you don't well it would be the end of you.
Get back to my desk people need work I should be getting on with to do theirs but I have been busy in silly meetings and litrually every 5 mins get nagged 'have I done it yet'. But as I am about done they discover what they should have been working on is doable without my work. I don't shake but at one point today I was shaking so much with nerves I couldn't type. Had a very short lunch and stayed on late sorting people problems out. (Thankfully the even more junior people are nice and 1 did help me at one point today I'm so great full for the help)
I'm a junior no training in the technologies I work with not even before starting the job. £3 million+ worth of projects and possible future client resting on my shoulders... (Thankfully the real project lead and senior members are back next week although won't be long left till deadline) Wtf ...
Anyone got a job going I want out!5 -
Story time!
I worked at a company that was the HQ for a sizable organization for a while, until it was eventually bought out by another company, and then yet another company who was located in the valley.
We were kinda a forgotten office not being the HQ, like most places like that are.
No customers EVER visited our building, few if any people knew we existed even, even our own company. I visited HQ in the valley on a number of occasions and was stalked by the video monitoring system for hours before I was stopped by security and the cops called because nobody believed there as an office outside the valley when I explained why my badge looked different .... (San Jose cops were very nice about it and really pissed at the security team.) But that's another story...
One day people who were never at our office decided (after many meetings without talking to anyone at the office) ... they decided the beige walls at our office didn't match the company colors.
So they took all the generic wall coverings down and painted all the walls an almost imperceptible different color.
So now we had an office with all white(ish) walls and nothing on them. Due to the configuration of the building there were these huge monolithic white walls that looked pretty dumb.
This lasted quite a while so as a joke I printed up and framed (found an old frame, as a former HQ we had lots of stuff lying around) a sign that said:
"This space intentionally left blank."
When the "mediocre hotel room quality art" and posters were scheduled to go up the folks putting the art up skipped that wall thinking the sign was official.
Even the somewhat corporate drone directors, and one VP at our office thought it was so funny, they didn't say a word about it. Word has it back at HQ they assumed it "must be fire code or something" and told the folks hanging the crappy art to skip that wall.
It lasted on that wall for a decade until we moved out of that building. On the last day, everything was moved, but that sign remained. No idea if it is still there or not...2 -
> Worst work culture you've experienced?
It's a tie between my first to employers.
First: A career's dead end.
Bosses hardly ever said the truth, suger-coated everything and told you just about anything to get what they wanted. E.g. a coworker of mine was sent on a business trip to another company. They had told him this is his big chance! He'd attend a project kick-off meeting, maybe become its lead permanently. When he got there, the other company was like "So you're the temporary first-level supporter? Great! Here's your headset".
And well, devs were worth nothing anyway. For every dev there were 2-3 "consultants" that wrote detailed specifications, including SQL statements and pseudocode. The dev's job was just to translate that to working code. Except for the two highest senior devs, who had perfect job security. They had cooked up a custom Ant-based build system, had forked several high-profile Java projects (e.g. Hibernate) and their code was purposely cryptic and convoluted.
You had no chance to make changes to their projects without involuntarily breaking half of it. And then you'd have to beg for a bit of their time. And doing something they didn't like? Forget it. After I suggested to introduce automated testing I was treated like a heretic. Well of course, that would have threatened their job security. Even managers had no power against them. If these two would quit half a dozen projects would simply be dead.
And finally, the pecking order. Juniors, like me back then, didn't get taught shit. We were just there for the work the seniors didn't want to do. When one of the senior devs had implemented a patch on the master branch, it was the junior's job to apply it to the other branches.
Second: A massive sweatshop, almost like a real-life caricature.
It was a big corporation. Managers acted like kings, always taking the best for themselves while leaving crumbs for the plebs (=devs, operators, etc). They had the spacious single offices, we had the open plan (so awesome for communication and teamwork! synergy effects!). When they got bored, they left meetings just like that. We... well don't even think about being late.
And of course most managers followed the "kiss up, kick down" principle. Boy, was I getting kicked because I dared to question a decision of my boss. He made my life so hard I got sick for a month, being close to burnout. The best part? I gave notice a month later, and _he_still_was_surprised_!
Plebs weren't allowed anything below perfection, bosses on the other hand... so, I got yelled at by some manager. Twice. For essentially nothing, things just bruised his fragile ego. My bosses response? "Oh he's just human". No, the plebs was expected to obey the powers that be. Something you didn't like? That just means your attitude needs adjustment. Like with the open plan offices: I criticized the noise and distraction. Well that's just my _opinion_, right? Anyone else is happily enjoying it! Why can't I just be like the others? And most people really had given up, working like on a production line.
The company itself, while big, was a big ball of small, isolated groups, sticking together by office politics. In your software you'd need to call a service made by a different team, sooner or later. Not documented, noone was ever willing to help. To actually get help, you needed to get your boss to talk to their boss. Then you'd have a chance at all.
Oh, and the red tape. Say you needed a simple cable. You know, like those for $2 on Amazon. You'd open a support ticket and a week later everyone involved had signed it off. Probably. Like your boss, the support's boss, the internal IT services' boss, and maybe some other poor sap who felt important. Or maybe not, because the justification for needing that cable wasn't specific enough. I mean, just imagine the potential damage if our employees owned a cable they shouldn't!
You know, after these two employers I actually needed therapy. Looking back now, hooooly shit... that's why I can't repeat often enough that we devs put up with way too much bullshit.3 -
What the actual...?!
So I finally packed up the courage to start looking for a job that wasn't making me travel roughly 2000 kilometers a month..... I notify the company cause I know they might want to get someone in for me to in board for more than a calendar month. After years of struggles and complaining about the same things I finally decided to make the shift. You know risk it....
And now, fucking NOW that I'm dealing with this, made a fucking plan and going through all this bloody turmoil for 3 bloody years trying to make shite work, my work and husband want to NOW meet me half way.... Like ffs guys!!! When I have been coming to you complaining and asking for help for almost 2 bloody years yall just went "ah she's such a strong character, cute little thing, she will get over it..." or what?! Did you just not fucking think that me complaining was, oh I don't know STRANGE AND OUT OF FUCKING CHARACTER AND JUST DAMWELL LEFT IT!!!
NOW you wanna go all... Oh how about we move closer... Oh you have been in 3 meetings asking for a pay increase/salary adjustment and we gave you FUCKALL while gas and everything else went up, and now you wanna match the offers I'm getting and finally give me what I'm due?!
Can everyone just get fucked?! I swear I'm packing a bloody backpack and living as a gypsy!! Everyone is just letting me down by not giving a shit and now that I'm going "OH REALLY?! FUCKING REEEAAALY?!" everyone is just like "where's this coming from" I cannot deal! 7 years of this man. And 3 years of this company and they just fucking left me to suffer and figure it all out and now they wanna jump in... The house burnt down, bye!!!11 -
TLDR; Go to bottom of post.
Around this time two years ago was the start of my group project in University. The project was to write an app in android and have a web side to it too. The group was to be overseen by a member of staff. The first meeting was introductions and to look at the spec, during the second we were to decide a group leader (PM) and other positions.
A person I shall call BD and I volunteered for PM. I didn't have experience with leadership but wanted some, and was the only one with confidence in android, the biggest part of the system. I got four of the votes.
BD, with his scouts experience, not being afraid to breathe down people's necks and bash some heads together, and having been PM last year, with his group receiving 69% (he failed the year and was resitting), earned 5. One guy was missing.
When it came to sorting out roles and responsibilities, BD confessed to not being a strong coder but that he'd help here and there. His role was planning our deadlines, doing our Gantt chart for deliverables, and was supposed to write a really detailed spec. He didn't have it at the meeting of the next week, as it was still in the works, and never messaged anyone. Next week he turned up with a Gantt chart of 1A4 page that only included the deadlines and deliverables in the spec, with three colours. One for android team, one for DB guy, and one for web team.
The guy who didn't turn up for voting got a girlfriend, a job at mcdonalds and did barely a thing. One guy in the web team did everything, carrying his friend who wouldn't do work (and also got swept out to see in a rubber boat with one of his bros lol (he was rescued)), and even though I'd done android dev I wasn't as quick a learner as two others in the team. Out of 10 people, 6 did real work.
The web guys stopped coming to meetings as they were taken over by android talk, and as we were quite behind, BG tried yellow carding them. They turned around with the website pretty much done, this one guy doing more than the 4 of us on android had. Yellow card lifted. We'd already complained about BD and his lack of everything (except screen brightness as he sat at the front of the lecture theatres with his wide brimmed hat looking at 9gag and videos (remembering he said he was resitting that year)) but grew a stronger dislike. Found out that he spent most of his time with his gf at our secretary/fellow android dev's house. Come coding week, he disappears entirely, only to attend meetings. He gave us a shell of the android code used for his previous year's project (along with documentation, complete with names and dates of updates, most of them (including the planning ones BD was supposed to do) bearing either one of two names. It was behind where we were at the time and had a lot of differences to our spec, and if we had used it BD may have used that to pull us down with him if things went wrong. He resurfaced at the end with the final documentation of how we'd all done, including reports on how each member had performed, which we were supposed to have reviewed. Our main, most proficient dev he accused of being irritable and brash, and a bad communicator. He was Norwegian, his voice was just a bit gruff, and he was driven and didn't waste time. He bashed the web team for not turning up, and had already been rude and unhelpful to everyone who voted for him in the first place.
In our own reports we all devoted paragraphs to delicately describing his contributions, excluding his suggestion that we use the code he gave us. Before we had our results and our work was completed, he individually kicked us from our group's facebook group and unfriended us.
Our 43% mark at the end, coupled with his -40% penalty from the red card we had him on, felt good, but not as good as a better result would have, especially as the fool that was BD would be inflicted on a group a third time. He changed to some other course after that year finished, so he must have failed his resit of second year.
During third year, a friend of mine who was PM for a group that passed well passed other things with too slim a margin to be happy, so chose to resit the year. He didn't have to do the group project again, and had that time free. But BD had to resit. His group had 69%. A yellow card with a 20% deduction wouldn't do it, so he MUST have had a red card as PM his previous year. Well that didn't come up when he claimed credit for his team's 69% during elections... My housemate's compsci boyfriend 2 years up overheard me talking about him, he was in 1st year with BD. BD failed and resat 1st year too. 4 years and he couldn't make anything stick. I feel bad for him through understanding the pains lack of work and internet distraction bring, and unfortunately I can't wish bad things on him because he brings them on himself. I wish I never see his face again though.
TLDR; Guy in group project lies and is dishonest from start to finish, getting PM pos by 1 vote. Gets what he earns.2 -
Should’ve posted this after it happened, but it requires a bit of background anyway.
There’s this guy that oversees our OpenStack environment. My team often make jokes and groan about him in private because he’s so overbearing. A few months back, he had to take us to our data center to show us our new racks, and he kept saying stupid stuff like “you break this and it costs me $30,000” as if he owns everything. He’s just... one of THOSE people. Always speaks in such a condescending way. We make jokes that he is our “best friend”.
Our company is shifting most of our products to the cloud in response to the coronavirus (trying to make it an opportunity for “innovation”). This has involved some structural and responsibility changes in our department, and long story short, I’m now heading the OpenStack environment alongside other projects.
This means going through grueling 1-on-1 meetings with our “best friend”. It’s not too bad, I can be pretty patient with people, so I didn’t mind too much at first. Then a few things happened.
1. He sent a shared folder that he owned containing info related to the environments. Several documents were outdated and incomplete, so I downloaded them, corrected them, and then uploaded the documents to my teams file share, as I was supposed to since we now own the projects.
2. Several files were missing, and when I asked about them, he said “Oh, did you refresh the browser?”. I told him no, that I downloaded them locally and republished them to my teams server, because he was supposed to hand everything off to us at once. He says “Well, silly, how are you going to get updates if you’re looking at them locally?” and kind of chuckles at me like I’m stupid.
3. He insists on training me how to remote into one of the servers to check on cluster space, which in itself is fine. I understand others wanting to make sure things will be done right by the people who come after them. But he tells me to download SuperPutty. I tell him, “oh no, that’s alright. I don’t need putty”. He says “oh cool, what tool do you use for ssh?”. I answer him “Just Git. If I want to I can use a CentOs bash terminal too, because we have WSL installed”. He responds “You can’t ssh through Git”.
I was actually a little shocked. I didn’t know if he was serious or not so I was silent for a few seconds before hesitantly saying “yes you can”. He says “this is news to me” and I so I tell him “every single one of our build jobs fetches code from Git with ssh” and he seemed genuinely shocked and surprised by that.... so then it occurs to me to show him that you can ssh in Powershell and that REALLY blew his mind. He would not shut up about it for several minutes. I was amused until it just got annoying.
Needless to say, my team had been previously teasing me about having to work with him, so they found it hilarious when I told them afterwards.8 -
Meetings... They say coding is 70% thinking and well.. I find meetings to be a great place to think about what am currently working on. I go in with a sketch book and sketch away. I always figure out whatever is bugging me by the end of the meeting. After all the PM will send a summary of whatever I may have missed during the meeting
-
Well, I was Always into Computers and Games and stuff and at some point, I started wondering: "why does Computer Go brrr when I Hit this Button?".
It was WinAPI C++ and I was amazed by the tons of work the programmers must have put into all this.
13 year old me was Like: "I can make a Game, cant be too hard."
It was hard.
Turns out I grabbed a Unity Version and tried Things, followed a tutorial and Made a funny jet Fighter Game (which I sadly lost).
Then an article got me into checking out Linux based systems and pentesting.
*Promptly Burns persistent Kali Live to USB Stick"
"Wow zhis koohl".
Had Lots of fun with Metasploit.
Years pass and I wrap my head around Javascript, Node, HTML and CSS, I tried making a Website, worked Out to some extent.
More years pass, we annoy our teacher so long until he opens up an arduino course at school.
He does.
We built weather stations with an ESP32 and C++ via Arduino Software, literally build 3 quadrocopter drones with remote Control and RGB lighting.
Then, Cherry on the top of everything, we win the drone flying Contest everyone gets some nice stuff.
A couple weeks later my class teacher requests me and two of my friends to come along on one of their annual teacher meetings where there are a bunch of teachers from other schools and where they discuss new technology and stuff.
We are allowed to present 3D printing, some of our past programming and some of the tech we've built.
Teachers were amazed, I had huge amounts of fun answering their questions and explaining stuff to them.
Finally done with Realschulabschluss (Middle-grade-graduation) and High school Starts.
It's great, we finally have actual CS lessons, we lesen Java now.
It's fuckton of fun and I ace all of it.
Probably the best grades I ever had in any class.
Then, in my free time, I started writing some simple programs, firstvI extended our crappy Greenfoot Marsrover Project and gave it procedural Landscape Generation (sort of), added a Power system, reactors, Iron and uranium or, refineries, all kinds of cool stuff.
After teaching myself more Java, I start making some actual projects such as "Ranchu's bag of useful and not so useful stuff", namely my OnyxLib library on my GitHub.
More time passes, more Projects are finished, I get addicted to coding, literally.
My days were literally Eat, Code, sleep, repeat.
After breaking that unhealthy cycle I fixed it with Long Breaks and Others activities in between.
In conclusion I Always wanted to know what goes on beneath the beautiful front end of the computer, found out, and it was the most amazing thing ever.
I always had constant fun while coding (except for when you don't have fun) and really enjoyed it at most times.
I Just really love it.
About a year back now I noticed that I was really quite good at what I was doing and I wanted to continue learning and using my programming.
That's when I knew that shit was made for me.
...fuck that's a long read.5 -
Argh,
Today - you son of a bitch.
It all started with a 2 hour flight out of town for business, and I mean started as in I needed to be at the airport at 4:30am!
Despite 2 coffee's to get me out of bed I proceeded to indulge myself in the magic juice, 3 cups later and it felt like my heart belonged in a Grand Prix.
Now here is the sticky part, we where briefed that we would only be doing 2 site meetings and that was it.
Low and be hold it got worse, turns out that we would be pitching our product to 3 highly regarded CEO's, now bare in mind that my position on this trip is as the lead developer, and don't get me wrong I am well up to date on every aspect of the business, hence why they sent me.
So more coffee down the gullet, and eventually the conversation leads back to a project that I had developed to allow authorization of debit orders online, now usually I'm quite a well presented person in these types of situations, but you don't realize how quick this can change.
A quick jump to the geography of the location I was doing business. Johannesburg, South Africa - its as dry as hell, smoggy and at a very higher altitude "as in above sea level".
Now unfortunately none of the above factors where helping me much at all.
Now back to where I am being asked about my project, and never in my life have I tripped over my own words, I went completely blank, I'm surprised I didn't pass out to be honest.
Now despite the death stare and my colleague kicking me under the table, I am feeling pretty terrible, fortunately I had a kick ass team that was able to cover my ass!
Luckily I was able to recover ( 2 muffins and about 3 bottles of water later). We where able to salvage the meeting and it turned out pretty well, I regained my energy and we made it happen!
Must say the flight back was amazing! Almost empty and we all had a row of seats to ourselves, which resulted in some major comfort stretching!
Thanks for tolerating my essay, I'd love to hear if anyone has had anything of the sorts happen to them.2 -
After I spent 4 years in a startup company (it was literally just me and a guy who started it).
Being web dev in this company meant you did everything from A-Z. Mostly though it was shitty hacky "websites/webapps" on one of the 3 shitty CMSs.
At some point we had 2 other devs and 2 designers (thank god he hired some cause previously he tried designing them on his own and every site looked like a dead puppy soaked in ass juice).
My title changed from a peasant web dev to technical lead which meant shit. I was doing normal dev work + managing all projects. This basically meant that I had to show all junior devs (mostly interns) how to do their jobs. Client meetings, first point of contact for them, caring an "out of hours" support phone 24/7, new staff interviews, hiring, training and much more.
Unrealistic deadlines, stress and pulling hair were a norm as was taking the blame anytime something went wrong (which happened very often).
All of that would be fine with me if I was paid accordingly, treated with respect as a loyal part of the team but that of course wasn't the case.
But that wasn't the worst part about this job. The worst thing was the constant feeling that I'm falling behind, so far behind that I'll never be able to catch up. Being passionate about web development since I was a kid this was scaring the shit out of me. Said company of course didn't provide any training, time to learn or opportunities to progress.
After these 4 years I felt burnt out. Programming, once exciting became boring and stale. At this point I have started looking for a new job but looking at the requirements I was sure I ain't going anywhere. You see when I was busy hacking PHP CMSs, OOPHP became a thing and javascript exploded. In the little spare time I had I tried online courses but everyone knows it's not the same, doing a course and actually using certain technology in practice. Not going to mention that recruiters usually expect a number of years of experience using the technology/framework/language.
That was the moment I lost faith in my web dev future.
Happy to say though about a month later I did get a job in a great agency as a front end developer (it felt amazing to focus on one thing after all these years of "full-stack bullshit), got a decent salary (way more than I expected) and work with really amazing and creative people. I get almost too much time to learn new stuff and I got up to speed with the latest tech in a few weeks. I'm happy.
Advice? I don't really have any, but I guess never lose faith in yourself.3 -
So... I've got a confession to make.
I'm no longer a Dev. After the disaster that was my last commercial gig, I went and got a sec Ops role... And I love it. It's just technical problem solving and explaining all the way.
Don't get me wrong, I still love to code. But that's exactly the thing. As a commercial developer employed by corporations, I spent close to 80 % of my time not coding, but in useless meetings, or trying to figure out just what my colleagues thought was "common sense", reverse engineering their work and documenting how to get it running, etc. Basically, fixing shit for braindead academics with next to no real world experience.
Now, when I code, I get to do it on my own terms, with my own stack and as much comments and docs as I want to have. I own my time, and the only ones that are allowed to interrupt me is the local fire department.
I can do what I'm fucking passionate about and leave the rest for the useless people.5 -
Depression and anxiety is a major challenge in my work life.
I could remember vividly when I was at my last job, any time I felt depressed I'll call for sick leave. It was hard for me to pinpoint the cause of my depression because even while on most sick leave I still felt depressed.
I blamed it on my job, blamed it on my family, on my social circle, on my friends, on my lifestyle, on almost everything. At some point it all felt like it was me versus the world, a fight I could never win.
Thoughts came in... Maybe it's because John is now married with two kids, or because Stella is now the new manager, or that David just bought a new Ross Royce and I'm still riding an ice-cream truck, or its because Steve is always on vacation and PM always complaining about uncompleted task with no acknowledgement for the 2 months task finished in a week, or because Boss is always calling for stupid meetings. Different thoughts in my head... Jealousy, Envy, Disappointment, Tiredness, Confusion, all combined at once.
But I did found a cure for my anxiety and depressed nature...
During lunch hours I visit a beach close to where I work, it's called "Tarkwa bay". I'll sit at the rock formations and glare at the shadows of the rising sun, listen to the sound of rumbling waters and passive the complete overview of nature. The feeling I get there is really calming, It occupies my head with neutral thoughts and a love for nature. 🤗
I truly experienced an improvement overall and it's been a while I felt depressed since I started such a routine.
Nature is really a gift.1 -
Before implementing a feature that is one hour of work for one developer, let's have four meetings about it, a user survey, specifications and endless discussions on resources.1
-
My current company has taught me a remarkable lesson. Just 1-2 really good full stack developers is all it takes to pull in Disney, Berkshire Hathaway and other fortune 500 companies. Cause at the end of the day these companies dont care about how many developers or how proficient the work flow is over here. They care about the history of the company, the mouth thats moving in these lunch meetings and the words being said. The sense of confidence and the nice building they see when they visit. Ive found a deep respect for marketing/sales, the facade that they can put up and the way a company builds off of facade until its no longer a facade. We literally wait until the big job is landed to hire the developers needed to make it happen. Its hilarious.
-
!rant
TLDR; Lost passion after a few years, wasted a year, went on vacation without really any technology, found my passion and am excited as hell for 2019.
After programming for nearly 5 years, I’ve hit the point of not wanting to program anymore. I’ve burnt myself out, and haven’t had a vacation in 8+ years so we’ve finally decided to take one. I’m not going to say it’s a full blown vacation, but a semi-vacation since it’s with my parents also so I do have to do a few things I’d prefer not to such as meeting relatives.
I didn’t have the motivation to work on any new projects, finish any projects I actually enjoyed, I just did a few side projects for friends that took me anywhere from 5 minutes to 30 minutes every few weeks. In general this year has been garbage in development terms, I’ve lost passion. It felt like a chore, I didn’t find the entertainment I once did.
I’ve been away from technology for about 2 weeks now, and have less than a week left before I fly back and I’m excited as hell. During this break away from technology (with the exception of browsing devRant once in a while), has me excited to work on many projects and actually start learning and improving my skills. I’ve actually gained the motivation to work on 2 projects that have been planned for nearly 2 years now, I’ve noted down ideas for them, made diagrams, etc, just never had the passion to develop them. 2019 is going to be one hell of a year, since I get back almost at the end of November, and December I have a few business meetings and University exams that I have to prepare for. Excited to see these projects through, one is going to be for the hell of it, just been a passion project I’ve wanted to do for years now. The other project is actually a project for one of my sub-companies that hasn’t officially released since I didn’t have the passion to work on it. (Not going to go into full detail yet about the companies/projects, going to save that for the future)
Alongside that, I’m excited since my main company that is totally unrelated to technology, is set to do some massive moves during 2019 also. Looking forward to that, and being able to launch my dream company (the sub-company I mentioned before).
Time for sleep now, goodnight! (Wrote this after a few drinks and in the middle of the night, hopefully it’s not full blown garbage)2 -
Non-dev crap.
I feel like I experienced so much shame in my life that I have become desensitized to it.
I cleaned up last night but I placed a box of dildo in the shelf so that I would remember sending it back. I didn't think too much about it since I was planning to reschedule a repair that's supposed to happen today. I talked to the admin and I was able to get a work permit early in the morning so we didn't have to reschedule and the workers arrived before lunch time.
A few days ago, I mentioned wearing a corset while working helps with my posture since I cannot slouch with it but this was a full-blown leather corset I wore last night and forgot it was under one of the pillows. The workers said they need to flip the bed over to get some extra space so I removed the pillows and saw the corset. I thought whatever, it doesn't look that kinky.
I went back to work as normal. I was in the living room attending meetings and testing some shit. Completely normal work day. I got up to drink some water when I saw the workers resting, one of them has his back against the drawer. No, I did not whip him and scream at him to go back to work. In my head, "That drawer has no lock (I live alone) and it has all the shit. All the shit." I'm talking lingeries, ball gags, dildos, anal plugs, nipple clamps, and you know the rest. I thought, fuck it, I'm hungry and told them I'm just gonna go down to get some lunch. I've been working with these guys for four years so stealing is not really something I'm concerned of. Not to mention, they cannot get out of the building until I sign their papers after I get back where I would see if anything is missing.
Normally, I'd be paranoid that they might accidentally open it if his shirt gets caught into the handle or something. Who knows, they could be nosy and just open it. I thought, "Whatever, they'd be the one acting awkward if they see the crap that's in there anyway."
So benefit of the doubt, I'm good. No kinky shit blatantly out in the open. Wrong. That fucking box of dildo in the shelf is there. It's right fucking there and I couldn't be bothered to snatch it away thinking they already saw it anyway, I would just look guilty if I suddenly took it and hid it. Besides, it doesn't even look like a penis or a fleshlight. It could be a tiny massager for all they know.
Note to self: Keep your stuff in the sex dungeon.5 -
Just another big rant story full of WTFs and completely true.
The company I work for atm is like the landlord for a big german city. We build houses and flats and rent them to normal people, just that we want to be very cheap and most nearly all our tenants are jobless.
So the company hired a lot of software-dev-companies to manage everything.
The company I want to talk about is "ABI...", a 40-man big software company. ABI sold us different software, e.g. a datawarehouse for our ERP System they "invented" for 300K or the software we talk about today: a document management system. It has workflows, a 100 year-save archive system, a history feature etc.
The software itself, called ELO (you can google it if you want) is a component based software in which every company that is a "partner" can develop things into, like ABI did for our company.
Since 2013 we pay ABI 150€ / hour (most of the time it feels like 300€ / hour, because if you want something done from a dev from ABI you first have to talk to the project manager of him and of course pay him too). They did thousand of hours in all that years for my company.
In 2017 they started to talk about a module in ELO called Invoice-Module. With that you can manage all your paper invoices digital, like scan that piece of paper, then OCR it, then fill formular data, add data and at the end you can send it to the ERP system automatically and we can pay the invoice automatically. "Digitization" is the key word.
After 1.5 years of project planning and a 3 month test phase, we talked to them and decided to go live at 01.01.2019. We are talking about already ~ 200 hours planning and work just from ABI for this (do the math. No. Please dont...).
I joined my actual company in October 2018 and I should "just overview" the project a bit, I mean, hey, they planned it since 1.5 years - how bad can it be, right?
In the first week of 2019 we found 25 bugs and users reporting around 50 feature requests, around 30 of them of such high need that they can't do their daily work with the invoices like they did before without ELO.
In the first three weeks of 2019 we where around 70 bugs deep, 20 of them fixed, with nearly 70 feature requests, 5 done. Around 10 bugs where so high, that the complete system would not work any more if they dont get fixed.
Want examples?
- Delete a Invoice (right click -> delete, no super deep hiding menu), and the server crashed until someone restarts it.
- missing dropdown of tax rate, everything was 19% (in germany 99,9% of all invoices are 19%, 7% or 0%).
But the biggest thing was, that the complete webservice send to ERP wasn't even finished in the code.
So that means we had around 600 invoices to pay with nearly 300.000€ of cash in the first 3 weeks and we couldn't even pay 1 cent - as a urban company!
Shortly after receiving and starting to discussing this high prio request with ABI the project manager of my assigned dev told me he will be gone the next day. He is getting married. And honeymoon. 1 Week. So: Wish him luck, when will his replacement here?
Deep breath.
Deep breath.
There was no replacement. They just had 1 developer. As a 40-people-software-house they had exactly one developer which knows ELO, which they sold to A LOT of companies.
He came back, 1 week gone, we asked for a meeting, they told us "oh, he is now in other ELO projects planned, we can offer you time from him in 4 weeks earliest".
To cut a long story short (it's to late for that, right?) we fought around 3 month with ABI to even rescue this project in any thinkable way. The solution mid February was, that I (software dev) would visit crash courses in ELO to be the second developer ABI didnt had, even without working for ABI....
Now its may and we decided to cut strings with ABI in ELO and switch to a new company who knows ELO. There where around 10 meetings on CEO-level to make this a "good" cut and not a bad cut, because we can't afford to scare them (think about the 300K tool they sold us...).
01.06.2019 we should start with the new company. 2 days before I found out, by accident, that there was a password on the project file on the server for one of the ELO services. I called my boss and my CEO. No one knows anything about it. I found out, that ABI sneaked into this folder, while working on another thing a week ago, and set this password to lock us out. OF OUR OWN FCKING FILE.
Without this password we are not able to fix any bug, develop any feature or even change an image within ELO, regardless, that we paid thausend of hours for that.
When we asked ABI about this, his CEO told us, it is "their property" and they will not remove it.
When I asked my CEO about it, they told me to do nothing, we can't scare them, we need them for the 300K tool.
No punt.
No finish.
Just the project file with a password still there today6 -
If you are a father and you find out your kind produced a pile of shit, you change the diaper and get rid of it all. No questions asked.
If you are a developer and your colleague produces pile of shit and you try to get rid of it, you end up in meetings how this piece if shit is actually master piece of shit and have to argue about it to manager that knows shit about a shit.2 -
I work for a web agency.
Over the last 18 months a company asked us about 5 different quotes for rather minimal changes to their website.
While being minimal changes, estimating costs for them still requires several hours of work for research, meetings, correspondance and writing the damn things. They never even gave us a response (neither positive nor negative), except once where they told us that they wouldn't pay for project management because their instructions are so clear that PM isn't necessary.
As a response to the last one, after several months, they send us a 10 pages long pdf with requirements for a new website (or a "restyle" like they call it, even if it has absolutely nothing in common with the current one).
We inform them that we can't permit ourselves to continue studying new solutions for free and therefore tell them that a detailed offer would cost them something like 300$, and that amount would then be discounted from the eventually accepted job. We also roughly estimate a price range of about 15k - 20k for the new website.
We get an email back, from the CEO (until now it was a secretary), with essentially 3 arguments written in condescending form:
1. he brags about his revenue being over 9 billion $$$ a year, and that being a part of a global holding for which "communication is essential" (sic.) means that they need to coordinate and "can't simply accept an offer" [even if it's 400$, for specific change exactly requested by them, I guess...]
2. 15k is too much [... for the website representing this 9 billion dollar holding on the internet, for which the requirements are written in the 10 pages long pdf]
3. He asks for a meeting
We accept the meeting, we go to their office.
When we arrive there, the secretary informs us that the CEO will not participate. So we talk the her and the head of the "Communication Dept" in videoconference.
I explain them that if the sum, which we thought would be appropriate (~15 - 20k), is too high, the Pareto principle would allow us to, theoretically, achieve about 80% of the features and quality for about 20% of the cost. Their genuine response is:
"So your estimate was wrong! You can do it for much less!".
I try to explain them that the most money in a project goes into "attention to detail".
The "Communication Dept." person, who is "doing this job since too much time" (sic.), refuses to believe and insists that "details" don't exist on the web.
I tell her: "In any kind of work, the more effort you put into something, the better it tends to get, with diminishing returns".
She insists: "I don't understand this".
So now I'm here, doing the 6th offer, free of charge, for a 5k website, for a company that generates 9kkk revenue each year, trying to define a "Definition of Done" that works out.
FML I guess.
Sorry for the long post.7 -
My patience limits are huge but our product manager seems that likes to stretch them.
You piece of fuckin shit. You ask for feature A and we agree on the way we will do it. Good. Half way you want to change it's behavior.
Fine, i accept that. Let's move on.
I'm close to finish it and you come and say let's add more on that feature and make it more complicated. I can't say anything, just fine and let me work on it.
Then you and the senior dev that "helps" us don't come to 2 meetings and just communicate via emails.
And then, then you fuckin scums tell me that is unacceptable that i haven't finished it and it doesn't work?
I used my uni time and missed lessons to work on your shitty feature and that you just yell at me?
What about comming to the fuckin meetings so we can discuss what problems occured and how i can overcome them, you sucker?
Just because our boss complained to you that the product is late because of you, that doesn't give you the right to yell at me, you piece of shit.
And the next time you tell me that you pulled the repository and it doesn't work while it does on everyone else i will come and shove your laptop up to your ass.2 -
So, we have this ma'am at work that is the least direct person I know.
She can transform one sentence in a paragraph and the meetings/talks with her I usually end up in my "happy place" at the middle of her phrases and come back latter when she isn't finished and I'm like
"wtf is she talking about yet? Damn I went away again, shit... Just nod and smile..."
We had a meeting scheduled with her and some clients today... She missed it... MOST FUCKING PRODUCTIVE DAY EVER!
Thank you.7 -
Had a conference call and one of the guys said something along the lines of "I can handle the load (ticket load)" didn't even thought about it my mouth instinctively reacted with "that's what she said".
A couple of guys laughed but the other few just "wooooow"ed like if I had thrown a 9/11 joke.
This is not a rant perse, just a reminder that if I ever launch my own startup I shall look to hire "joke sensitive" people to make my scrum meetings as awkward as possible.4 -
!related
Someone told me a teacher wants to meet us at the library at 3:00pm. I went there and there was a yellow van with some of my friends and a teacher. Then
T = Teacher
M = Me
F = Friend
T: Your name is not on the list.
M: What list?
T: You didn't attend yesterday's meeting.
M: I don't know there was a meeting yesterday.
T: No excuses.
M: But..
T: No excuses(slightly louder). I gave a message yesterday.
M: I didn't even receive the message. How do I...(even know about the meeting)
T: *interrupts* Your name is not on the list. You don't have permission from the administrators to go. You cannot go.
F: He doesn't usually attend the meetings.
(I don't even know the existence of the meetings before, no one told me)
T: You must attend the meeting next time.
M: When? What time?
T: I will send a message if we have any meetings.
M: *Flat-toned* Okay then. *keeps minimal facial expression then walk away steadily*
Inner me: What an ignorant teacher. She should at least listen to my REASONING, not treating them like empty excuses. I don't even know where they are going, I don't even have the intention to join them. Then she thought that it's my fault. I don't know what I don't know.3 -
Hi everybody (newbie here).
The most annoying thing about CEO's and bosses is theirs incapability to understand mere technical or even logical matter of topic discussed in important meetings. I found a perfect parody video, which describes how I feel when participating that kind of meeting.
https://youtu.be/BKorP55Aqvg
(sorry if repost)
P.S. Nice community this.devRant
(been lurking few weeks)7 -
So ok here it is, as asked in the comments.
Setting: customer (huge electronics chain) wants a huge migration from custom software to SAP erp, hybris commere for b2b and ... azure cloud
Timeframe: ~10 months….
My colleague and me had the glorious task to make the evaluation result of the B2B approval process (like you can only buy up till € 1000, then someone has to approve) available in the cart view, not just the end of the checkout. Well I though, easy, we have the results, just put them in the cart … hmm :-\
The whole thing is that the the storefront - called accelerator (although it should rather be called decelerator) is a 10-year old (looking) buggy interface, that promises to the customers, that it solves all their problems and just needs some minor customization. Fact is, it’s an abomination, which makes us spend 2 months in every project to „ripp it apart“ and fix/repair/rebuild major functionality (which changes every 6 months because of „updates“.
After a week of reading the scarce (aka non-existing) docs and decompiling and debugging hybris code, we found out (besides dozends of bugs) that this is not going to be easy. The domain model is fucked up - both CartModel and OrderModel extend AbstractOrderModel. Though we only need functionality that is in the AbstractOrderModel, the hybris guys decided (for an unknown reason) to use OrderModel in every single fucking method (about 30 nested calls ….). So what shall we do, we don’t have an order yet, only a cart. Fuck lets fake an order, push it through use the results and dismiss the order … good idea!? BAD IDEA (don’t ask …). So after a week or two we changed our strategy: create duplicate interface for nearly all (spring) services with changed method signatures that override the hybris beans and allow to use CartModels (which is possible, because within the super methods, they actually „cast" it to AbstractOrderModel *facepalm*).
After about 2 months (2 people full time) we have a working „prototype“. It works with the default-sample-accelerator data. Unfortunately the customer wanted to have it’s own dateset in the system (what a shock). Well you guess it … everything collapsed. The way the customer wanted to "have it working“ was just incompatible with the way hybris wants it (yeah yeah SAP, hybris is sooo customizable …). Well we basically had to rewrite everything again.
Just in case your wondering … the requirements were clear in the beginning (stick to the standard! [configuration/functinonality]). Well, then the customer found out that this is shit … and well …
So some months later, next big thing. I was appointed technical sublead (is that a word)/sub pm for the topics‚delivery service‘ (cart, delivery time calculation, u name it) and customerregistration - a reward for my great work with the b2b approval process???
Customer's office: 20+ people, mostly SAP related, a few c# guys, and drumrole .... the main (external) overall superhero ‚im the greates and ur shit‘ architect.
Aberage age 45+, me - the ‚hybris guy’ (he really just called me that all the time), age 32.
He powerpoints his „ tables" and other weird out of this world stuff on the wall, talks and talks. Everyone is in awe (or fear?). Everything he says is just bullshit and I see it in the eyes of the others. Finally the hybris guy interrups him, as he explains the overall architecture (which is just wrong) and points out how it should be (according to my docs which very more up to date. From now on he didn't just "not like" me anymore. (good first day)
I remember the looks of the other guys - they were releaved that someone pointed that out - saved the weeks of useless work ...
Instead of talking the customer's tongue he just spoke gibberish SAP … arg (common in SAP land as I had to learn the hard way).
Outcome of about (useless) 5 meetings later: we are going to blow out data from informatica to sap to azure to datahub to hybris ... hmpf needless to say its fucking super slow.
But who cares, I‘ll get my own rest endpoint that‘ll do all I need.
First try: error 500, 2. try: 20 seconds later, error message in html, content type json, a few days later the c# guy manages to deliver a kinda working still slow service, only the results are wrong, customer blames the hybris team, hmm we r just using their fucking results ...
The sap guys (customer service) just don't seem to be able to activate/configure the OOTB odata service, so I was told)
Several email rounds, meetings later, about 2 months, still no working hybris integration (all my emails with detailed checklists for every participent and deadlines were unanswered/ignored or answered with unrelated stuff). Customer pissed at us (god knows why, I tried, I really did!). So I decide to fly up there to handle it all by myself16 -
There are a lot... I am going to pick the interview dialogue (incl. test) with the government.
Following situation:
-5 recruiters
-3 candidates (including me) who have all passed an online test that did last for 3 hours
The online test was for the government to see how every candidate is good at math, English, situation adaptation, historical questions, a little bit of techy questions like "What does fps stand for?" and basic questions like that.
Even tho I did apply for a job as a software developer, there was not a single fucking question about programming. I shit you not. Anyways...
After everyone did introduce themselves. I was given the following question by one of the recruiters:"How do you think will the regular work look like to you, if you were to schedule it? We will be starting with you, <myName>"
Me:"Since this is hopefully going to be my first job in software development, I can only assume it for now. Based on my knowledge about this specific topic that I have made by reading other software developers' work experiences in form of textual content, I guess that I am going to do this [...] and that [...]. Oh and after this comes the planning phase (I had mentioned the sprints and agile "frameworks") and meetings of how the projects are doing so far.
After this comes the phase of sitting down and getting to work on the project I am assigned to.
At the end comes the "see you tomorrow, xyz" phase and everyone leaves."
Somebody else from the 5 recruiters:"I am sorry to interrupt you right here, but we are not offering you a dev job. It rather is a mixture of dev and sysadmin. You will be working most of the time fixing someone's problem with their PC and not sitting in a dark and empty corner of a warm room."
This was such a disrespect that I could not give an answer to. I was deeply shocked. Developers need more respect. Most of the fucking things you use, are created by developers, you asshole.
"We will be very happy, if you can call us by tomorrow to let us now if you are still interested."
Me does not even bother anymore and blacklists that government as a "trust me. You do not want to work there" type of job offering place.
Since I did not sign any NDA. It is the government of Germany.
PS: I did apply for a *dev* job. But somehow they did decide to create a new job and assign me to it. That is not professional.6 -
So, with couple of new people in senior managerial roles, pink slips started flying left and right before the holiday season. That didn't happen before in the company. It's still relatively small and when people left that was for better paid or more interesting work.
While I can understand that from the business perspective and especially for a few who might have been considered dead weight (devs and other roles), I have a serious problem with the way it was handled. It's one of those 5 minute notices. If we weren't remote, I guess escorting out by security would follow.
Most recent person to go is actually one of the most senior devs at the position that became redundant over time, as it clashed in the "pyramid" with another dev. He was involved in many aspects of the product and greatly contributed to the overall success during years of hard work, i'd say maybe more than any of us.
He didn't fuck up anything major as far as I know, his services were just not needed anymore, compared to the other guy. Saving money. I get that.
At T-1 day he prepared a demo of his project. Meetings, Slack, everything as usual. Next thing we got was a "we wish him well in future endeavours" e-mail.
What I find most disturbing is the fact his account was removed immediately, and then we were asked to get any files and anything else we might need, all over personal communication channels (private e-mail, Skype etc.) because he was locked out of all company accounts.
I seem to have have survived this year. One thing they have definitely achieved, based on some off the record chat and some public updates, tweets etc I can see, is for many of us to start networking, polishing CVs and generally stop giving many fucks about the company and the outcome.
I've myself started brushing up on some new skills (stacks) and some old ones (algorithms, etc.) I may need any day now, as it seems.
If they can basically tell "thank you and fuck off" to one person maybe most involved with the company growth, with zero dignity and respect for the person, then fuck them.4 -
Do real interviewers (I mean those who are smart and have some experience) still ask questions like "what are your weaknesses"?
Dumbass, why the fuck should I declare, not just to you but also to myself, that I have some particular weaknesses? I know what I'm not good at, and I'll keep trying to improve. But unless my weakness is that I get a massive boner during team meetings, you don't need to know about it. I'm not telling you. Just know my strengths - that's enough. If you're just following a standard list of interview questions that you didn't even come up with, stop pretending to be an interviewer for heavens' sake.8 -
Client A
At the first few meetings, told us they are giving sponsors to World Cup 2018 and we should totally talk about it loudly on media.
Then when we submitted our plan, they said things have changed and they no longer can mention about World Cup. We had to redo everything.
Now, they blame us that our service quality is so bad that we should learn from *some refernce* company. Said company is only talking about their sponsorship for World Cup.
---
Client B
Bought smallest package from us. Demand services greater than our largest package.
Gave us an information of a name spelled in "Barbu". We used that spelling and used it for various tasks in past few weeks. All approved by client.
Blamed us we are giving such a poor service that we cannot even spell "Babu" correctly this morning.1 -
We have a badly out of shape but functional product , the result of a "if its not broke don't fix it" mentality. The only thing manangement cares is our next release and making meetings to plan other meetings...
Now comes the time of the security Audit (PCI)...
Manager : oh noooo the audit will fix this issue, quickkk fix it !
Us : welllll its a lengthy process but doable, we just gotta do a,b,c,d,e . Part a is essentially what we need the rest are refactoring bits of the system to support part a since the performance would be shit otherwise
Manager: can you do part a before the audit starts ?
Us: yep.
Manager: do it . Oh and pop those other issues on JIRA so we can track em
Audit completed....
Manager: so we got through ok?
Us : 👍 yep
Manager: okayy, take those other issues..... and stick em at the bottom of the back log...
Us : huh ? *suspicious faces*..... okay but performance is gonna be poor with the system as it is cuz of part A....
Manager: yeaaahhh * troll face* ....about that.... roll it back and stick that too at the bottom of the log. We got to focus our next release. Lemme schedule a meeting for that 😊
Us : faceplam4 -
Did I tell you that X third party system needed to be updated due to that pos using flash? Yes
Did you bitch about budget constraints and finding workarounds and stuff like that? Also Yes
Did I mention that X system was crucial for people and that we were not going to be able to do anything about it if we did not allocate the time to modify that before it happened? Also Yes
Did I mentioned this on multiple occasions? Yes
Was my team also pulled out from working on the alternative before this happened? Yes
Did I send multiple emails about this, talks, meetings and documentation of me saying all of the above? You betcha
Oh well 🤡5 -
Story Time!
Tittle: About Larry.
Fun Game: Tell me if / when in this story you know the plot twist.
Setting: Years ago, non coding job.
I work with Larry a lot, Larry works remote. In technical terms Larry is senior to me and I escalate some technical issues that get assigned to Larry. I've never met Larry in person.
Larry can be hard to work with, but he's plenty good at his job and I don't mind his prickly side. Sometimes it takes telling Larry something a few times before it sinks it, but that's not a big deal. Sometimes it seems like Larry doesn't remember his cases entirely, but he has a lot of cases. Also Larry has good reason for how he works considering the land of scubs who usually escalate to him without any thought / effort.
Larry's escalation team is short staffed and they're trying to hire folks, but that's been like that forever.
So one day I get an email that Larry is going to be out of the office for a few weeks. Nothing unusual there.
My current case that I share with Larry sort of floats in limbo for a while. The customer is kinda slow to respond anyhow and there's nothing that I need Larry for.
Finally I get automated notice that my case has had a new escalation engineer. Laura. Laura is much more positive and happy compared to Larry. Understandably Laura isn't up to date on the case so we go back and forth with some emails and notes in the case.
The case is moving along just fine, we're making progress, but it's slow because of the customer's testing procedures. Then we hit a point where this customer's management pushes on sales for a solution (this customer's management is known for doing this rando like for no reason).
Down the management chain it goes and everyone wants a big conference call to get everyone up to date / discuss next steps (no big deal).
Now I really don't want to do this with Laura and throw her into the deep end with this customer, she doesn't have the background and I'd rather do this call with Larry & Me & Laura. Also according to the original email Larry is due back soon.
I start writing an email to Laura about "Let's try to schedule this for when Larry gets back."
Then I stop ... I don't really know why I stop but when it is a "political case" I want some buy in on next steps from management so I go talk to my manager.
-Plot Twist Incoming-
Long story short, my manager says:
"Laura IS Larry..."
O
M
G
I had no idea. Nobody told me, nobody told ANYBODY, (except a couple managers).
Back up a few months Larry apparently went to his managers and told them he was going to transition, surgery and all, in a few months.
Managers wondering how to address this went to HR and some new hire very young to be a manager HR manager drone logiced out in her bonkers head that "Well it shouldn't matter so don't tell anyone."
ARE YOU FUCKING KIDDING ME!!??
Thank god I didn't send that email...
I did send an email to Laura explaining that I had no idea and hoped I didn't say anything stupid. She was very nice about it and said it was all good.
After that incident made the management rounds (management was already fuming about being told not to tell anyone) things came to another critical point.
Laura was going to visit the company HQ. Laura had been there before, as Larry, everyone knew her as Larry... nobody (outside some managers) knew Laura was Larry either. With nobody knowing shit Laura was going to walk in and meet everyone ...
One manager at HQ finally rebelled and held a meeting to tell his people. He didn't want Laura walking in and someone confused, thinking it was a joke or something horrible happening.
HR found out and went ballistic. They were on a rampage about this other manager, they wanted to interview me about how I found out. I told HR to schedule their meeting through my manager (I knew they didn't want my manager to know they were sniffing around).
Finally the VP in our department called up the HR head and asked WTF was going on / kind of idiots they had over there (word has it legal and the CEO were on the call too).
HR had a change in leadership and then a couple weeks later there were department wide meetings on how to handle such situations and etc.32 -
(tl;dr at the bottom)
one day, an old "friend" asked if i would like to be part of a project with their friends to create a site, we had plenty of meetings, my partner and i were excited with this project until we realized that those girls literally wanted a copy-paste from another site, and i mean, exactly the same but translated in google translate. We even asked other developers for their opinion and they said the same, that it was a copypastarino.
so my partner and i talked to them about how we didn't want to be part of a copied project. Those girls went angry and we drop off that.
Yesterday, after almost 7 months, I found you that those girls won an "startup contest" and that they will be traveling to sillicon valley soon to meet a founder and start the business.
ooooh boy...
what would happen if we send an email pointing out that copied-googleTranslated project?
is the industry really that dumb or lazy? i mean, how is that even possible that they haven't found it out?
tl;dr
some girls just google-translated a site, my partner and i didnt want to be involved and now, 7 months later, they are going to sillicon valley to meet a founder and make it real.11 -
My first rant :)
It's only 2 months I work as a developer, and i get so frustrated when at meetings my boss doesn't consider me or doesn't ask me about my work, and instead he asks others about things I am doing..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!5 -
Like any frontend dev working in an organisation, all of what I do are "designed" by an UX/UI designer. Now he fucking has a problem with me and has been going around saying he's gonna resign because of me. (Apparently he said that while walking away from where I was with the intention of it falling in my ears but I was oblivious to it).
On enquiring (to another colleague)why he has a problem with me he said I don't respect him. Perplexed(more curious), I asked what is it that I do to disrespect him and what I found out was out of the world.
I DISRESPECT HIM BY ASKING HIM QUESTIONS ABOUT THE WORK HE DOES.
Awesome, right? Not only does he consider that disrespect but he also takes it personally. WTH?! I'm not supposed to ask why you do a certain things?
Some of my questions -
1. Why are there font sizes of 13px, 14px, 15px right next to each other?
2. Why is there a gap between the sidebar and the content?
3. Why aren't even sizes being used?
Etc.
So much for maturity. He's completely ignoring me, be it on the floor or during meetings. I couldn't care less. It wouldn't take me much to tell him where he's fucking up. The only reason I asked him questions was to understand things better; maybe I don't understand what I find wrong.
But now ~(˘▾˘)~4 -
Got demoted, got a pay raise and don't know how to feel about it. A story of how not to drink with your coworkers?
The story begins roughly 8-9 months ago. Me and this coworker (let's name him Tim) go out drinking after a Friday party at the office. We do some rounds and we're both smashed. Tim starts telling me how he's happy with life and that he's earning a nice salary right now. He told me his salary. It was the same as mine. Which was weird - He codes in a more hardcore languages than me and has almost double the time in the company as me. I think after some more drinking I've confessed that I make the same as him. This part is sort of a blur (drinking). I've gotten a pay raise(+30-40%) roughly a few months ago from that point backwards because another company gave be a much higher offer. The company I work for matched to keep me. Anyway, 3 months or so after the drinking,Tim is promoted to team lead, and me and a few other people are added to his team. Conversation slips and he told me his new salary - quite a bit more than me.I think it's safe to assume what happened.
The problem with that is that I was a team lead of 1 person (me) at that time, and I was managing my own time and my own tasks, was working with people individually. I was part of the weekly meetings with the CEO and other team leads. Being stripped of this title wasn't a problem at the beginning, as people still contacted me because of their problems, suggestions, whatever. A few more months pass (to now) and less and less people are contacting me - instead they are talking with Tim, and are asking of his opinion on tasks I should do, where he has no experience and roughly 0 lines in the programming language I code in. This is starting to piss me off.
There are a couple other things to take into consideration as well - The company is hiring a lot of people right now. The whole structure for team leads changed a bit, more team leads then ever right now and new roles added pretty fast.
I've gotten a pay raise a few weeks ago though(10%~).
I'm not sure on how to react to this. Should I comply and just keep on working on these tasks? Or should I still keep contacting people directly on their requests and talk to them directly, take credit for the projects I complete publicly and the stuff I do as I was previously doing? Part of me wants to reroute all of the stupids questions people have to Tim, as he is now responsible for these tasks and get this weight off my shoulders.
I'm starting to shift to learning a new programming language and thinking of jumping ship. Thoughts?6 -
TBH i didnt start to hate any big company. I use SONY as my phone and im going to stick with it probably. Due to how they handle opensource which is just awesome. Like who releases a guide to build an OS to your device that wasnt even released. AMAZING.
I never loved microsoft since it was always a piece of shit OS.
Maybe one "Company" would be the linux foundation.
Yes yes i know i love Linux from my heart and thats true and will stay that way most for sure but how they handle things is just terrible.
VMware was not following GPL rules and were law suited by Linux foundation. What do they do ? They buy a fucking seat in the board of linux foundation and everything is alright ?
Are you fucking kidding me ?????
This is ridiculous.
Linux will stay the best. Since Kernel has nothing to do with linux foundation but thats just fucked up how they handle things.
People from opensource world were allowed to come to board meetings and request something.
After VMware joined the board they said that they woudlnt be doing that at all.
Like WTFFFFFFFFFF ?
Microsoft joined the linux foundation as fucking platinum member. This is fucking wrong !!!!!!!!!!!!!!!!!!
Basically the OS thats anonym to Spying joined the Linux foundation that is against spying ???
Whats fucking wrong with you people ??????????????
This must get better ffs. Somebody should step in and make a good clean in linux foundation so that this never fucking happens again and mainly stop it NOW.
I dont explain it good in here but i recommend you to watch "Linux sucks Forever" Brian explains it pretty good in there.
We must do something about this ffs.4 -
Prior to a tech conference in Las Vegas, the department manager held pre-meetings (yes, more than one)
with the developers to outline their expected behavior (yes, there was an outline in Word). Since
they would be representing the company, professionalism would be expected at all times, not just
during the conference. He knew he couldn’t forbid gambling and drinking, but any unruly behavior
that could reflect badly on the company would be dealt with severe disciplinary action up to and
including termination. He wrote up very detailed itinerary, what track each developer was
expected to attend, meal times (yes, what time to get up for breakfast, meet for lunch, and time
to eat at night). First day was fine, casinos are kinda crazy so having an itinerary wasn’t the
worst idea and no one got lost. Days following however, got interesting. After the first evening
meal, everyone hit the casino as expected (too much drinking, etc..normal single twenty-something
guys do) and the manager especially had a good time.
Next, and following days, the manager could not be found in any of the ‘required’ technical tracks.
Not that they cared that much, but couple of devs decided to check out the casino, and sure enough,
there he was at one of the tables, drunk, and being very loud around at 10 in the morning.
Again, nobody cared much, manager wasn’t very tech savy, and so attending a track on C #threading
would be lost on him. It was more of ‘do as I say, not as I do’ kind of thing.
The manager kept to the itinerary, he met everyone at breakfast, lunch, and dinner, etc, but the
‘WTF’s didn’t get good until the manager was bragging about how wonderful the conference was, how
much he was learning and couldn’t wait to get back and start implementing everything he was learning.
It was such a joke, the guys would bait him on tracks they know he didn’t attend and an amazing amount
of BS could not be believed.
On the last day of the conference several decided to follow him after breakfast to see where he went
and watched him go into a technical track, just to walk back out and straight to the casino floor.
Again, around 10, he was drunk, not quite as loud until he threw up in a trash can (they said it was quite a scene).
He left to go back his room, which they suspected he took a nap before meeting everyone for lunch.
After that, they gathered his daily itinerary was:
- Get up for breakfast
- walk around and make sure it looked like he was heading to a track
- head to the casino
- take a nap
- eat lunch
- walk around some more
- head to the casino
- take a nap
- eat dinner
- head to the casino
- wash-rinse-repeat
Last day caught up with him. After about week of drinking, staying up late, etc, his body (he’s in his mid 50’s, 350lbs+, so imagine)
kinda’ gave up. Could barely walk 50 feet without needing to sit down, and the flight back was worse for everyone,
throwing up occasionally, moaning, you get the idea.
On the following Monday with the VP if IT, everyone was discussing the conference, what they learned,
what they liked, etc, the manager also bragged, yes bragged, on how tired he was because of how much
he learned and the reason why he probably caught the flu (he couldn’t hide how sick he was on the flight)
saying “When you’re in the learning zone, you lose track of time and then you are so exhausted, your
immune system is susceptible to all kinds of things.” . VP was so impressed by his dedication and
fighting through the exhaustion for the good of the company, he gave him the rest of the day off.
Other devs? No, they had to go back to work.3 -
Too many to count, but this one useless meeting stands out the most.
I was working as an outside dev for software corporation. I was hired as an UI dev although my skill set was UI/engineer/devops at the time.
we wrote a big chunk of 'documentation' (read word files explaining features) before the project even started, I had 2 sprints of just meetings. Everybody does nothing, while I set up the project, tuned configs, added testing libraries, linters, environments, instances, CI/CD etc.
When we started actual project we had at least 2 meetings that were 2-3 hours long on a daily basis, then I said : look guys, you are paying me just to sit here and listen to you, I would rather be working as we are behind the schedule and long meetings don't help us at all.
ok, but there is that one more meeting i have to be on.
So some senior architect(just a senior backend engineer as I found out later) who is really some kind of manager and didn't wrote code for like 10 years starts to roast devs from the team about documentation and architectural decisions. I was like second one that he attacked.
I explained why I think his opinion doesn't matter to me as he is explaining server side related issues and I'm on the client-side and if he wants to argue we can argue on actual client-side decisions I made.
He tried to discuss thinking that he is far superior to some noob UI developer (Which I wasn't, but he didn't know that).
I started asking some questions and soon he felt lost and offended. We ended that discussion with conclusion that I made my own decisions on the client-side. That lasted less than 10 minutes.
So I just sit there and eat popcorn for next 4 and half hours listening to their unnecessary discussions where some angry manager that did programing decades ago wanted to show that we are all noobs and stupid.
what a sad human being.
what a waste of time, but hey I got payed for this 5 hour meeting.1 -
Impossible deadline experience?
A few, but this one is more recent (and not mine, yet)
Company has plans to build a x hundred thousand square feet facility (x = 300, 500, 800 depending on the day and the VP telling the story)
1. Land is purchased, but no infrastructure exists (its in a somewhat rural area, no water or sewage capable of supporting such a large facility)
2. No direct architectural plans (just a few random ideas about layout, floor plans, parking etc)
3. Already having software dev meetings in attempt to 'fix' all the current logistical software issues we have in the current warehouse and not knowing any of the details of the new facility.
One morning in our stand-up, the mgr says
Mgr: "Plans for the new warehouse are moving along. We hope to be in the new building by September."
Me: "September of 2022?"
<very puzzled look>
Mgr: "Um, no. Next year, 2021"
Me: "That's not going to happen."
Mgr: "I was just in a meeting with VP-Jack yesterday. He said everything is on schedule."
Me: "On schedule for what?"
<I lay out some of the known roadblocks from above, and new ones like the political mess we will very likely get into when the local zoning big shots get involved>
Mgr: "Oh, yea, those could be problems."
Me: "Swiiiiishhhhh"
Mgr: "What's that?"
Me: "That's the sound of a September 2021 date flying by."
Mgr: "Funny. Guess what? We've been tasked with designing the security system. Overhead RFID readers, tracking, badge scans, etc. Normally Dan's team takes care of facility security, but they are going to be busy for a few weeks for an audit. Better start reaching out to RFID vendors for quotes. Have a proposal ready in a couple of weeks."
Me: "Sure, why not."1 -
Storytime!
(I just posted this in a shorter form as a comment but wanted to write it as a post too)
TL;DR, smarts are important, but so is how you work.
My first 'real' job was a lucky break in the .com era working tech support. This was pretty high end / professional / well respected and really well paid work.
I've never been a super fast learner, I was HORRIBLE in school. I was not a good student until I was ~40 (and then I loved it, but no longer have the time :( )
At work I really felt like so many folks around me did a better job / knew more than me. And straight up I know that was true. I was competent, but I was not the best by far.
However .... when things got ugly, I got assigned to the big cases. Particularly when I transferred to a group that dealt with some fancy smancy networking equipment.
The reason I was assigned? Engineering (another department) asked I be assigned. Even when it would take me a while to pickup the case and catch up on what was going on, they wanted the super smart tech support guys off the case, and me on it.
At first this was a bit perplexing as this engineering team were some ultra smart guys, custom chip designers, great education, and guys you could almost see were running a mental simulation of the chip as you described what you observed on the network...
What was also amusing was how ego-less these guys seemed to be (I don't pretend to know if they really were). I knew for a fact that recruiting teams tried to recruit some of these guys for years from other companies before they'd jump ship from one company to the next ... and yet when I met them in person it was like some random meeting on the street (there's a whole other story there that I wish I understood more about Indian Americans (many of them) and American engineers treat status / behave).
I eventually figured out that the reason I was assigned / requested was simple:
1. Support management couldn't refuse, in fact several valley managers very much didn't like me / did not want to give me those cases .... but nobody could refuse the almighty ASIC engineers. No joke, ASIC engineers requests were all but handed down on stone tablets and smote any idols you might have.
2. The engineers trusted me. It was that simple.
They liked to read my notes before going into a meeting / high pressure conference call. I could tell from talking to them on the phone (I was remote) if their mental model was seizing up, or if they just wanted more data, and we could have quick and effective conversations before meetings ;)
I always qualified my answers. If I didn't know I said so (this was HUGE) and I would go find out. In fact my notes often included a list of unknowns (I knew they'd ask), and a list of questions I had sent to / pending for the customer.
The super smart tech support guys, they had egos, didn't want to say they didn't know, and they'd send eng down the rabbit hole. Truth be told most of what the smarter than me tech support guy's knew was memorization. I don't want to sound like I'm knocking that because for the most part memorization would quickly solve a good chunk of tech support calls for sure... no question those guys solved problems. I wish I was able to memorize like those guys.
But memorization did NOT help anyone solve off the wall bugs, sort of emergent behavior, recognize patterns (network traffic and bugs all have patterns / smells). Memorization also wouldn't lead you to the right path to finding ANYTHING new / new methods to find things that you don't anticipate.
In fact relying on memorization like some support folks did meant that they often assumed that if bit 1 was on... they couldn't imagine what would happen if that didn't work, even if they saw a problem where ... bro obviously bit 1 is on but that thing ain't happening, that means A, B, C.
Being careful, asking questions, making lists of what you know / don't know, iterating LOGICALLY (for the love of god change one thing at a time). That's how you solved big problems I found.
Sometimes your skills aren't super smarts, super flashy code, sometimes, knowing every method off the top of your head, sometimes you can excel just being more careful, thinking different.5 -
When it is 645am Friday and you spent the whole week with meetings and tasks and sleepless nights.
You just cannot give a tiny rat ass about the naming of routes and functions.
DO NOT ask me about my variable names!3 -
Biggest teamwork fail? This is the general way we do business where I work right now:
My boss didn’t want to be the kind who hovers, always micromanaging. He also hates the idea of taking programmers away from their work for meetings. Sounds great, right? This has resulted in:
• All non-lead devs being excluded from all meetings other than scrum (including sprint planning and review meetings). Nobody ever knows what the hell is going on. They don’t think we “need to know.” This means most of our day is spent trying to figure out what needs to be done, rather than getting anything done.
• Our remote boss making dozens of important decisions about our platform, never telling us, and blaming us for not forcing our lead to be more communicative.
• Pull requests staying open for weeks, sometimes months, because nobody has definitively decided what version we’re actually supposed to be working on. This means our base branch could be any of them, and it means PRs that have been opened too long need to be closed, updated, and re-opened on the false promise of someone actually looking at it.
Just ranting here... but I think our biggest teamwork fail is happening right now, with all of those things ^3 -
In my previous company we developed a CRM web app for the company to use internally and it was in my humble opinion really easy to make sense of, but for some freaking we kept getting calls whenever someone got an error, and our default response was always to send us an email, then we will get back to you, as it was mostly stupid things they called about, for example, a customer might have to be status terminated, before you can click button A, button A would then be disabled and employees would call asking why. Apparently, people got annoyed by our response and went to the management, to get some guidelines as to when they could call the "development apartment" for help, so the management sends out some guidelines as to when they could call, write or whatever... The following was done without consulting us in any way ANY WAY AT ALL!... Because we all know management knows fucking best, and why bother asking the people that sit with it every day, and the way it was done was by saying:
If the background color on your error is red, it means the error is fatal and you can call the developers immediately, if its orange send an email and they will answer within 48 hours LIKE WTF... Seriously???. That was basically it, and honestly we had just been using colors, without much thought to it ofc red, was an error etc. But they we're not "OMG EVERYTHING IS BREAKING" alert, so we decided to use a couple of hours refactoring the color of the flash errors, and after that, we did not have many red alerts(None, yes none what so ever) We changed all the red ones to orange, and introduced some new colors. That worked for some time around 6 months or so, but then people obviously started calling again like, why even bother... So we created a simple service desk, blocked all incoming calls to our phones that were from regular employees, heard a lot of complaints about this from the employees, management was mad, we had so many meetings with those top paid management fuckers that know everything (way better than you and me), about how to handle this. As it took way too much of our time, that people couldn't bother trying simple things, or make some sense as to why a button is disabled etc. We ended up "winning", was allowed to block calls for some time, till the employees had learned to use a freaking simple service desk, it's not fucking rocket science Okay, stop being a pain in the ass... And it actually fucking worked! Most relaxing time after people got a hang of using the service desk instead of calling life was good after that... <3 -
At a previous job, boss & owner of company would waste hours of my time to show me, at his own desk, every small detail of some random feature he had fallen in love with on some random webpage he found, while saying "I don't want to disrupt your plans or anything, this is just something to keep in the back of your minds, as this would be a really nice thing to have, even tho none of the clients have asked for this and I have asked no one else for a second opinion, and I will most likely ask you to remove this feature in the future because I will finally have realized it wasn't that good an idea anyway."
Ok dipshit, what the fuck are we supposed to do with this information? Every week from this moment on you will ask whether we have found the time to implement this feature, even though you are fully aware that our schedule has no room for random, unplanned features and that we are already not able to meet the unreasonable deadline you pulled out of your ass two weeks into a development process that would end up taking 8+ months.
We are already overworked, we already work hours upon hours of unpaid overtime, and yet you still think it reasonable to pull us away from our work every other fucking day to talk about random extra features you want added, but don't want added to the roadmap because you want no delays... Fuck you, fuck your toxic attitude, fuck your meetings where you spend half an hour complaining about features we are still in the process of developing the backend functionality for (on test servers) not having the right font colour for the text, and fuck your legacy desktop software originally written in COBOL that you now want moved to "the cloud".
I would rather be unemployed and live as a hobo on the streets with a "will code for food" sign than work for you ever again. -
Every Monday I am privileged to wake up 1. 5 hours earlier and listen to executives talk about what meetings they had with potential customers and what news about ongoing agreements with other potential customers (which have been in the pipeline for 1 year or more sometimes)
Why is this necessary?? There has been virtually no progress on any of the topics discussed. At least nothing that concerns us devs.
Instead we get to wake up earlier, waste 1 hour, and get bored listening to what essentially seems like a sales speech while convince the employees the company is not spinning its tires while stuck in the mud.3 -
Smartphone manufacturers these days, imagine how meetings to come up with ideas for new products go about.
Product manager :ok people,what can we do to make our next smartphone 'different'.
Employee 1: let's add more cameras
Employee 2:Let's kill the notch
Employee 3:Let's include the buzzword AI in all of our marketing
Employee 4:Let's put 8Gb of Ram in our phone
Employee 5:Let's just do all of those things and also give it a screen with a ridiculous aspect ratio and unnecessarily high resolution.3 -
Got a new guy. Having a dumb meeting. New guy is humblebragging. It is making the dumb meeting longer. I feel angry. Like Warren Moon must have felt in 1995. He is a PhD. That's probably why. Ugh.1
-
a meeting on why we are behind on a project. a meeting about meeting about being behind.... too many useless meetings
-
Recently attended a meeting about lessening the frequency of meetings and making them more productive. After three hours, it was decided that we needed to block out three more meetings in the future to follow up on this topic.
-
In my case, low motivation is usually caused by askholes who bitch about broken AF code, which ALWAYS turns out to be theirs, infected with their own idiocy.
Definition: ASKHOLE
- A Person who constantly asks for your advice, yet always does the opposite of what you told them.
Pretending I'm in back-to-back meetings & general avoidance (when possible) seems to work. -
Every general meeting with a CEO who has never tried the freaking product or prototype and has zero technical knowledge.
As well, just about two out of three meetings with a HR person.
I've had meetings with a CTO too where it legit could be a boring handbook or email used for inducing sleep at night.3 -
This is long rant/story:
My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.
Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.
Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.
So, the conversation goes on as follows:
"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"
"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"
"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"
"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"
"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"
"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.
…. After an hour … the Employee had a talk with the Manager
"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."
Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.
**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.1 -
Lately I'm running into quite some negative atmosphere in meetings. Raise your hand if you think we all should improve our soft skills.
For example, we had a meeting with our client the other day. It was supposed to be only with the two most senior guys in the team and a couple of the less senior (just because one of us knows better the maths of it and the other one knows better about the limitations of the hardware), but in the end some other team members also joined.
In this meeting, we wanted to discuss an issue that had to be fixed. Quite a complex one. The main speaker from the clients, even though also technical, was having a hard time trying to explain properly to us what the issue was about. He was doing quite well, but it was complex enough. Well, one of the guys in my team kept interrupting him to ask very detailed questions (that would not help us understand it better, not until we got first the big picture). When I say "interrupting" I mean that the guy would half shout a question in the middle of a word from the client.
The client was patient and tried to answer, but our nice guy would keep answering back in a "gosh you really don't have a clue" tone.
We muted our microphone and one of the senior Devs asked the guy to please let them conduct the meeting, and that if he had such questions, he could mute the micro and ask them to us, so we knew we might have to ask about that.
Good. We unmute the microphone and 2 minutes after, our star guy goes in again and he even directs his question to someone else than who was talking (from the client).
Client gets pissed - I mean, I taught 12-16 year old teenagers for years and I don't think I would have hold it together for as long as the client did - and from then on all the meeting went in a really negative tone. Ending up with a call from the client to our senior guy to finish explaining in private the thing.
Well, our friend the interrupting guy not only got amazingly mad at the senior guy that (in private and constructively) gave him some advice on this kind of meetings. No, he also ended up spiraling into a close to insulting chain of emails towards the client -with his and our colleagues in copy- when he needed some specification.
Interrupting guy is 35yo and has been working with clients quite long. Our HR department still doesn't think we all should get communication workshops or something1 -
The more I'm on here the more I remember all the shit I have had to deal with in the past.
Anyway, lets rant! I just moved cities after college to be closer to my family, I didnt have any work lined up at that stage but started job hunting the moment I was settled in, I did some freelance for smaller companies to stay afloat.
Eventually I got a job at this agency startup where "SEO" was there main focus, still very inexperienced they put me on frontend and data capturing but will teach me how to code using their systems in due time. At this stage I was getting paid minimum wage, but I was doing minimum work and it wasnt that bad.
A new investor bought 49% of the company and immediately moved into the office space to focus more on marketing (He was one of those scaly marketing guys that will sell you babies if he could get his hands on enough to make a profit).
This is where everything starts going to shit. He hires a bunch of "SEO Gurus", fills up the small office with people like sardines squished together. Development was still our main money maker at this stage, so there where 3 new more senior developers at this stage and I started learning a lot really fast.
Here are some of the issues we had to deal with:
1. Incentives - Great more money, haha! No, No, you where 5 minutes late so you only get half of the promised amount.
2. For every minute you are late we will deduct it from you paycheck (Did I mention I was getting paid minimum wage).
3. If you take a smoke break we will dock it from your pay.
4. Free gym membership to the gym downstairs, but you can only go once a week during your lunch.
5. No pay raises if you cant prove your worth on paper.
He on purposely made up shitty rules and regulations to keep us down and make as much profit as he could.
Here are some shitty stuff he has done:
1. We arent getting a 13th check this year because the company didnt make a big profit - while standing next to his brand new BMW.
2. Made changes over FTP on clients work because we where too slow to get to it, than blames me for it because its broken the next day and wants to give me a written warning for not resolving the issue Immediately. They went as far as wanting to fire me for this, gave me 1 day notice for meeting and that I can bring a lawyer to represent me (1 day notice is illegal, you need 5 days where I am from), so I brought a lawyer since my mom was a lawyer. They freaked the fuck out and started harassing me about this a week later.
3. Would have meetings all the time about how much money the company is making, but wont be raising our pay since no one has proven they are worth it yet.
4. Would full on yell at employees infront of the entire office if they accidentally made an mistake on a clients project.
One one occasion I took a week off for holiday, my coworker contacted me to ask a question and I answered that I will handle it when I am back the following week. Withing 2 hours my other boss phones me in a rage, "he is coming to fetch the company laptop from my house in 5 minutes, he will let me know when he arrives. Gives me no time to talk at all and hangs up - I have figured out what has happened by now so when he showed up he has this long speech about abandonment, and trust and loyalty to the company. So I pass him my laptop once he shut up and said: "You do know I am on holiday leave which you approved, right?", he goes even more silent and passes me back my laptop without saying anything, and drives off.
While the above was happening Douche manager back at the office has a rage as well and calls the whole office (25 people) to a meeting talking about how I abandoned the company and how disgraceful that is.
Those are the shitty experiences I can remember, there where many more like this. All of the above eventually led to me going into a deep depression and having panic attacks weekly, from being overworked or scared to step out of line. Its also the reason I almost stopped coding forever at that stage. I worked there for 2.5 years with the abuse.
I left 2 weeks after the last shit show, I am ok now and have my anxiety and depression well under control if not almost gone completely.
Ran into Douche Manager a few months ago after 9 years, the company got bought out and the first person they fired was him. LOL! He now has his own agency and is looking for Developers (They are hard to find he says), little does he know I spread his name far and wide to all and every Dev I knew and didnt know to avoid working for him at all costs. Seems like word of mouth still works in this digital age.
Thanks for reading this far!5 -
Just finished and published iOS and Android app. Now they want to change some colors in the app theme. Never mentioned it once during weekly meetings about the app. Even tho I asked them for input. Now I have to spend half my day recompiling and making new screenshots for the store.... #fucklogic1
-
So the company decided to go agile. I am now a scrum master. And we have the local product owners and all. They made us do daily stand-ups.
I don't know what is a scrum master. Nobody knows what the hell is a stand-up. It seems to be an akward 30 minutes every day, when local product owner asks questions and demands status reports.
I did some googling and it seems that the scrum master is supposed to just support the team and solve problems. In our version the scrum master finds out the system architecture and requirements, fills the backlog, does the system design and reports to the project manager(s). Also reports to the clients about the general project status in an executive meetings. I also do the sprint planning, in which we fit the vague features that we are told into time tables with ready told dates.
Oh yeah, the team is just 2 guys. One of them is me. And the other guy relies completely on me to daily tell what to do, review the work and also answer all the project and company level questions that pop into his mind. He gets angry if he doesn't receive ready-thought solutions to all problems, since "you're the boss and it's your job to tell us what to do".
This is going to be a great year.6 -
Like half of my meetings, that could have been emails. Yesterday I was waiting for some person for 20 minutes and then, he only asked me about credentials for test environment. He sure had to schedule a meeting for that...
-
My job environment is either fucked up or am too young to understand what a job life is.
I was hired to intern for a startup having 2 main bosses/founders . one of them is mostly administrative and comes to office daily. He sets some tasks and i have to complete them, as soon as possible or sometimes till a deadline. He has little knowledge about the complexity of wotk so usually he says "just complete it as soon as possible so we could release it" but we haven't pushed any updates since i joined (of course i have completed some tasks, but they are just not pushed to the release version)
The other one , as i ranted previously is a completely different story.I think he is an elder bro or senior of the other boss,but he is just a superman: dealing with the distributers, commanding the hardware ppl, discussing with the othr boss, handling the server and most importantly the guy who wrote all the code i am working on. So he comes extremely rarely(1 or 2 days / week) , tries to communicate with me , but is immediately diverted by some other call/person and goes away.
The problem is : am feeling a little helpless. They give me tasks and i start working on them with excitement .( I don't believe myself to be a terrible beginner: i have been learning/working on android development for past 1 year, i know my things. And even if i don't, i know how to search/debug and produce results) . So as usual, i start and try to apply my skills / search for things i don't / try to understand his large,overwhelming and confusing codebase and at the end am stuck at some point where i don't understand what to do next. Sometimes its a bug which doesn't seems to fix, sometimes its a thing thats in the codebase but i couldn't find or sometimes it's just something i couldn't seem to understand why isn't it working. At that time, I only wish that boss to be here and look at what and how i have done, if its a correct approch and how can we together take it to completion (or simply wtf am i doing wrong, see my shit and tell me) .
But again, the tech boss is busy or wouldn't have time to understand my problem in our short , incomplete meetings. But he or the nontech boss will definitely have the time to ask the sttus of project and pressurise for the "deadline" .
Like today, i was so stuck at this fucking one line error that i couldn't detect that i just messaged him that am leaving for home 3 hours early. He came running and for the first time in history gave me a complete undisturbed time. It was such a small mistake, but i wasn't able to catch on my own. But when i told him, he immediately caught , changed a single line and the code started to work.
I am feeling irritated. Is this all a correct environment?2 -
During one of our 'pop-up' meetings last week.
Ralph: "The test code the developers are checking in is a mess. They don't know what they are doing."
ex.
var foo = SomeLibrary.GetFoo();
Assert.IsNotNull(foo);
Fred: "Ha ha..someone should talk to HR about our hiring practices. These people are literally driving the company backwards."
Me: "I think unit testing is complete waste of time."
- You could almost see the truck hit the wall and splatter watermelon everwhere..took Ralph and Fred a couple of seconds to respond
Fred: "Uh..unit testing is industry best practice. There is scientific evidence that prove testing reduces bugs and increases code quality"
Ralph: "Over 90% of our deployments are rolled back because of bugs. Unit testing will eliminate that."
Me: "Sorry, I disagree."
- Stepping on kittens wouldn't have gotten a worse look from Fred and Ralph
Fred: 'Pretty sure if you ask any professional developer, they'll tell you unit testing and code coverage reduces bugs.'
Me: "I'm not asking anyone else, I'm asking you. Find one failed deployment, just one, over the past 6 months that unit testing or code coverage would have prevented."
- good 3 seconds of awkward silence.
Ralph: "Well, those rollbacks are all mostly due to server mis-configurations. That's not a fair comparison."
Me: "I'm using your words. Unit tests reduces bugs and lack of good tests is the direct reason why we have so many failed deployments"
Boss: "Yea, Ralph...you and Fred kinda said that."
Fred: "No...we need to write good tests. Not this mess."
Me: "Like I said, show me one test you've written that would have prevented a rollback. Just one."
Ralph: "So, what? We do nothing?"
Me: "No, we have to stop worshiping this made up 80% code coverage idol. If not, developers are going to keep writing useless test code just to meet some percent. If we wrote device drivers or frameworks for other developers maybe, but we write CRUD apps. We execute a stored procedure or call a service. This 80% rule doesn't fit for code we write."
Fred: "If the developers took their head out of their ass.."
Me: "Hey!..uh..no, they are doing exactly what they are being told. Meet the 80% requirement, even if doesn't make sense."
Ralph: "Nobody told them to write *that* code."
Boss: "My gosh, what have you and Fred been complaining about for the past hour?"
- Ralph looks at his monitor and brilliantly changes the subject
Ralph: "Oh my f-king god...Trump said something stupid again ..."
At that point I put my headphones on went back to what I was doing. I'm pretty sure Fred and Ralph spent the rest of the day messaging back-n-forth, making fun of me or some random code I wrote 3 years ago (lots of typing and giggling). How can highly educated grown men (one has a masters in CS) get so petty and insecure?7 -
How many hours of actual productive work do you devs average a day? Honestly, I think I average about 2 hours of honest, good work in my 8 hour day. Between random meaningless meetings that could be emailed out or just daily distractions (coworkers chatting, my phone, etc). Am I alone in this?9
-
A meeting to redefine the definition of done. Which a "senior" programmer threw in.
3 hours after we are still there to "define"... All of this because this developer and a couple more want to keep a physical board which has no space for a "testing" section, so the tasks need either to be done-but-not-really and this is technically wrong (who cares?) or in-progress-but-not-really which is technically wrong (again, who cares?).
Just effin find a bigger board and don't waste 3 hours of my life and/or start thinking pragmatically and accept tasks can move backwards or have a ticket saying "testing" stuck to them, ffs!
The funny part? This dev is probably one of the grumpiest devs I met when you talk about meetings which are actually useful.4 -
Monday morning client meetings are usually a pain. If they're not delayed once, they're delayed twice, and they go on for hours, taking up the entire morning for everyone on the project.
To make today even better, it was about an hour of our client ripping into us developers on the project, and the application we're making, to shreds, saying that we have a lack of attention to detail and are working well.
(not bearing in mind, we're building a hybrid application, so it's a glorified web page and we can't test on every android phone, or iOS device and any combination of keyboards for those in between, and every problem comes with its own quirks when you're forcing things with html, js and angularjs).
I feel back for the pm, she had literally 5 more hours of salty, salty calls with our other poc about the issues raised and how we could go about fixing all these minor issues, since they know the solution to them, despite having little to zero technical knowledge.
Just another day in the office I guess. -
Meetings.. Was I not listening? Blame it on the ADHD (Attention Deficit Hyperactivity Disorder).
Maybe society has AEHD (Attention Expected Hyper-Delusion).
Seriously, who can pay attention to someone speaking AT you.
We have amazing magical devices one can enchant to do their bidding; Contemplating the details of such, often, is more enjoyable than what your rambling on about, talking head.
Not sorry, ;).
Also THANK YOU, you amazing MIT's (Manager of Information Technologies). A lot of you understand and even may use your underling employee's as a vented heat sync for your frustrations. I love what you do and thank the universe I don't have to engage myself in those activities. I have sympathy for the decision to give up your jeans and t-shirts for business attire; keep strong, your role is vital. <3
The insomnia is going to have to give me a break. Work in 3 hrs, time for a nap; and no, I don't take ADD medication (Amphetamine). I don't need a prescription; I can procure my own drugs, thank you.
Nor would I do them to get through work, that's drug abuse.5 -
Debating on whether to quit my job.
Part of the reason it's hard for me to make a decision is there are a lot of good things about my job:
- almost all the projects we work on are blue sky; no technical debt anywhere
- great teammates; people help each other out and generally there's a good vibe
- reasonable boss; he's totally fine with me managing my own schedule, and since I get my work done, he basically never questions when and where I work
- about 1 hour of corporate meetings each week
- best healthcare I've ever had; basically everything is paid for
- 3 weeks PTO & all major US holidays
- free food; generally healthy office snacks and such
So why would I want to quit this environment?
- I hardly get to code anymore. About 2 years ago, I got asked if I would mind helping spec out projects. Since then, I've moved from writing code related to projects to helping my teammates understand the business situation so they can build the right thing.
- I'm in lots of meetings. So we have very few meetings for the company itself. We have a bunch of customer meetings, though. And progressively, I've getting pulled into meetings where there's really no reason for me to be there, aside from "we should have a technical person present."
- The sales people are getting tired of turning down clients that our product isn't targeted for. So they're progressively pushing to make products in those areas. Unfortunately, I'm the only one on the engineering team has any experience in that other tech stack. Also, the team really, really don't want to learn it because it's old tech that's on its way out.
- The PM group is continuously in shambles. Turnover there has averaged 100% annually for about 5 years. Honestly, IMO, it's because they're understaffed. However, there has been 0 real motion to fix this other than talk. This constant turnover has made it so that the engineering team has had to become the knowledge base for all clients.
- My manager has put me on the management track, but has been very slow to hand off anything. I'm the team supervisor, and I have been since the beginning of the year formally. When the supervisor quit last year, it basically became obvious to me that I was considered the informal supervisor after that. However, I can't hire or fire; I can't give a review; I don't have any budget; I can't authorize time off. So what do I do now? Oh, I'm the person that my boss comes to ask about my co-workers performance for the purpose of informing promotion/termination/pay increases. That's it. I'm a spy.4 -
When you manage a large project and 1 of the devs helping you is bitching about 10 mins daily status meeting "in other places it's not like that " ... Who the fuck cares , this is how I want it to be so unless you are going to do 50%of the work like I will then come to the meetings and stop bitching , it's just 10 mins dammit7
-
we are organizer of really big trade fair and wanted to place a new product. It was a landing page for exhibitors especially for the fair, the exhibitor would get a subdomain with his company name. This landingpage had some highly requested features such as a calender for scheduling meetings, some floorplan features and other stuff... long story short: not a single exhibitor booked it. it was just trash and huge waste of time. dont get me wrong, this was actually a really great idea but the endproduct just sucked... now 4 resignations later we may start a new try :D
wish i would be a more passionsted ranter/writer... i have a ton load of such things i could rant about... but most of the time i get my consolation by reading your rants here.
obligatory: fuck, shit, cunt -
I've been a "firefighter" on our big money-making project for like a year now and probably will be for the next year. Every sprint, fully booked out.
However, this sprint, some people think I have time to brainstorm, learn new tech and attend meetings related to a completely new project.
"Will it done in 2 weeks?"
"How long do you estimate?"
I can knock up a rough version of your fucking application in about a week if someone grows some fucking balls and schedules me some fucking time for it. STFU and stop interrupting my other work. Allocate some time or shove it up your ass so far until you regurgitate it then swallow it again and choke on it. -
Been made redundant today.
Get some tissues cause imma spill my tea across your keyboards.
It was my first job. I was a UX designer.(I guess I have to use past tense?) I was there for 6 months. It was enjoyable and rewarding,slightly stressful because I worked for two companies under an umbrella company and was split 50-50.
I was told to come to work and I went and I saw one of my bosses in the room aswell ( I have two bosses btw - 2 companies)
The head of IT comes in and tells us we both have been made redundant as our company is not doing well ( its a travel company)...
I was shocked and I cried. I felt sorry for my boss he was there for ten yrs. And he has kids. I was told I could go home but I went to bathroom and cried. I came out and I didn't know if I was supposed to finish the day ( I had 3 meetings) or go home.... So I went to the meeting like a dumb dumb.
Most awk meeting because the other company didn't even know I was made redundant. The meeting was about how even though its a difficult time for us we r United and we aren't firing u guys just take unpaid holidays etc. Btw IT head was in that meeting was shocked to see me there ... I don't even know why I went. Anyways I found out they got rid of 174 employees across the umbrella company. I had to awkwardly tell my other boss I've been made redundant. He was shocked... I don't even know what to do. How to do. Sigh. I asked him if we wanted me to finish work off he's like do whatever u want to do.... I mean whattt.
Also does anyone know what a redudancy consultantion meeting is? It's my first job I have no idea what happens. Anyone here made redundant? How did u cope with it? Do u think I'm gonna get another job in this pandemic? Sorry I'm just a bit lost7 -
I work on many projects at work. There's divisions of teams and each team typically has one project. Each one of those projects have weekly Sprint meetings.
That's great! For the team. That means each team has one meeting a week so it's not too disruptive for those individuals.
Me on the other hand? I've got my hand in all the buckets. I'm on every team. I'm the only person on every team. This means I get to go to every meeting.
Let me rephrase that:
This means I -have- to go to every. Single. Meeting.
Which means I have a meeting every. Single. Day. Even if I didn't touch that project that week.
It is literally THE biggest waste of time. I sit there in a 1-2 hour long meeting saying absolutely nothing, not even being spoken to. I could be working on other projects.
And these meetings normally interrupt something I'm working on. Conveniently in the middle of me being in my zone. It makes me completely un-motivated to work for the hour before the meeting because why bother if I'm just going to get interrupted? And then it takes an hour to get back into everything after the meeting because everyone is fooling around or complaining about the meeting.
So that's three hours of my 8 hour work day completely wasted.3 -
I have been a professional Dev for about a year for a cyber security startup. Unfortunately, startup died do to finance mismanagement. My lead Dev said that he wanted to start a co-op contract business and since we all work great together than we should stick around. So we tried to obtain contracts and it is going much slower than imagine. I am going on my second month of no work or contract work. I'm working on my own site to do some freelance work on the side for myself offering ever, marketing and ERP software services. That is the goal for side hustle. However, for the main hustle well I'm stressed now of being home and we'll meetings not turning into money. I actually want to call it quits and do my own thing and look for normal gig. It just feels rough as he has been my mentor and offered me my first software gig. I don't feel like I own anyone anything I'm regards money or time. However, I do feel bad of I take off it will hurt them from being able to handle larger contract if they do get one.
Note: I'm pulling from my savings
Thoughts??3 -
Just went an entire day at work without a computer.
I know we usually rant about meaningless meetings and waste of time conversations but they are great for avoiding work while seeming very busy and productive.1 -
Today, my manager received a brand new Macbook pro with all its cool features while I am still stuck using an old Macbook pro (mid 2012 model). I always complained him about performance issues and all he did was to approve an OS upgrade (to Sierra). How does that even enable me to be productive? I am already running applications at the peak of the machine limits. Sometimes, the JVM crashes and other time Node.js runs out of heap space.
The manager is not a programmer. All he really does is attend online meetings, track and report to management, and write emails. Ideally, he would need a Mac Air or perhaps a Windows machine. I still wonder how did the company management allowed this. He is simply misusing his privileges as a manager and I can do nothing about it.2 -
People just can’t show up on time. I respect people’s time and I do not waste a minute of anyone s time. I do not like it. Time is a precious resource and we should all treat it as such. I expect the same from other people too.
There was a meeting supposed to happen a month or so back. Me and another guy. This meeting was basically giving him the resource utilization and some cost related details for the budget our team used up. They wanted a more granular report than the generic ones we submitted.
He scheduled it once and about ten minutes before he cancelled it. Fair enough.
A week later he sent an invite and the next day he cancelled it a few hours before the meeting. Fair enough I’m still not pissed.
A month or so since the first scheduled meeting, he scheduled a meeting and I turn up and he s not there and I wait for about half hour before I leave. Next day I get an email saying he s sorry. Now I’m pissed.
A couple weeks back he schedules a meeting and I turn up and I could see through the glass door and he s talking to someone in the room he s in. He signals to me to wait for five minutes. It takes about 20. Finally I go in and he s relieved so he can finally get the data from me. I tell him I waited for twenty minutes and I have to somewhere and asked him to reschedule the meeting. He asks when and I tell him a time where I know he won’t turn up. About 8 30 in the morning. He says yes.
Next day I show up he s not there and I wait for ten minutes and just he s walking in to the floor I exit the room and run to my place. He comes over and asks and I tell him I waited for sometime and I’m busy now and he mumbles and goes away.
By this time it is already a week or so after the deadline. The bigger boss from finance turns up and asks me why I haven’t given them the data I asked for. I tell him they schedule meetings and don’t turn up on time and my other work is getting affected productivity blah blah and he says okay make the report and give it to me. I tell him no I’m not wasting anymore time on this.
He goes to my boss creates a little ruckus my boss comes over and he goes wtf. I tell him what happened. He says it’s okay give them the report. I’m like I don’t know where I kept it must be somewhere I can’t waste anymore time on this. Guy from finance joins us at this point and angrily says he’ll find it himself and don’t need our help anymore.
The file is in my laptop I use for travel. Just a local copy. Zero fucking backups. And I just deleted it.
Fuck. You.1 -
!dev
I hate family meetings!
I'm youngest in the whole family, everyone have a job but I'm just student in first year on uni.
Almoust everyone treats me like a child and ask me questions about school. I hate it!
Plus my mom brought MY electric guitar (cheap ST imitazion from second hand) which I have only for a year, to aunt's husband, WITHOUT EVEN ASKING ME! OK, he played a guitar and he had a band but still, IT IS MY GUITAR YOU SHOULD ASK ME FIRST!!!
Also I don't have time for practicing, so I'm not very good at it, I was so embarrased when they want me to play somethig.
OH GOD WHY? WHY ARE YOU DOING THIS TO ME?
P.S.:
Sorry for my english.10 -
Hold a meeting that the participants actually want.
The biggest time wasters I had to attend were:
- "generic weekly meet up of people not working together telling what's new on their side" (I don't work with you, I DON'T CARE)
- "management wants updates/wants to talk about doing instead of letting us do" (go read Jira tickets, and ffs stay out of the experts' field... They're experts in it for a reason)
- "no agenda, this is just to get to know each other" (I get to know people on my own terms, stop forcing what can't be forced)
- most Scrum meetings (some people need guidance, I don't! Your Scrum chains actually hinder my productivity! Can we please stop wasting my time and nerves?)
And the best meetings? A couple of coworkers realizing "hey we need to make a decision here, let's book a conference room together" and "hey you know your stuff about xyz, can you teach us what you know?".10 -
Can't wait until I'm done at my current workplace (about a month left). I've had enough of this fucking shitty ass ancient ASP.Net ERP-system and employer.
For the system:
1. The build times are horrendous and eats up all CPU power.
2. The "classic" UI and UX is absolute garbage. If I was an accountant, I would go nuts trying to invoice someone. Companies pay millions to use this garbage.
3. Besides the "classic UI", there is a mishmash of different JS frameworks plastered on top.
4. Absolute no fucking technical documentation whatsoever
5. The in-house relational database is a mess, no relations, entirely denormalized, no documentation.
6. The frontend is structured in HTML tables with iframes inside <td>
The company:
1. If you're a implementation consultant and you quit your job, you get stripped off all your projects, you won't get to join anything social and you're placed on 1st line support for three months. They might as well force them out.
2. Anyone can work from home anytime they feel like it without any valid reasons, and believe me they do.
3. The senior devs are overworked as all hell. By the end of the year, some of them have hundreds of flextime hours and won't get anything in return.
4. The CEO seems like a jolly guy, but when you quit, he doesn't like you at all. He also acts like a bigshot, always getting driven around meetings when there is literally a very good metro network in this city.9 -
Well, I am not sure whether this is supposed to be about worst experience as a reviewER or a reviewEE so I'ma do both. First as a reviewer.
So, on my first project in this company, I introduced automated build scripting (read: suggested, was "volunteered" to do it, then had to bust my ads to get it done). Prior to this, our process was run the thing in Visual Studio a bunch of times (don't ask) and package the resulting files. Well, new requirements made this not sustainable.
So after many many meetings in which I assured my co-workers that the script wouldn't cock up and go sideways and format our server (HOW???) and showed them how to work it AND added all the features they requested. I finally send the script out for code review. Oh the joy. Questions like: "why did you implement this?" Came from the guy who told me to implement it. "Can you change the formatting?" I checked and no. "Why isn't this to the code standard?" Because the code standard doesn't include scripting languages.
And here is the piece that takes the whole piss soaked shitsicle pie "I don't understand why we're doing this in the first place. We have a build process already, why do we need a new one?" FUCKING REALLY?!?!? YOU WERE IN THE GODS DAMNED MEETING WHERE WE DECIDED TO DO THIS!!! SET OUT THE REQUIREMENTS!!! LITERALLY EVERYTHING TO DO WITH THIS SCRIPT YOU WERE THERE AND YOU'RE ASKING WHY WE'RE DOING IT NOW!?!?! Fucking hell. I forced it through anyway because I had the higher ups all signed off on it, but seriously. Just because we're doing something new that slightly inconveniences you, doesn't mean it doesn't need to be done. Stop being afraid of change.
Side note: these people actually would regularly hold up process and product improvement because change is scary.2 -
Meetings.
Too many meetings.
"Why do you explain...." 10kv electrical shock.
Explanation so everyone has the same knowledge.
"But CD ES process of LCE..." Water. From the emergency hose. In the face.
For fucks sake, we are using speech in a meeting so stop using motherfucking abbreviations you shit hole.
"We had bugs". Taking an hot iron and shoving it somewhere nice.
Explain - what the fuck are you talking about? What bugs? Tickets? Documentation? Implications of the bugs? Hate. Much hate.
Um. I don't know. Maybe. But if.
Thumb wrenches.
Please, stop wasting time, if it's non important, a " No " doesn't hurt....
Let me show you. (4k Monitor, 10 px font, bright neon colors, IDE looks like LSD trip in bad).
Crucification.
If you present stuff, good - but for christs sake, shove your motherfucking shitty IDE setting in your own arse and turn on presentation mode with neutral colors - bright or dark mode, I don't care, but readable without danger of seizure.
I can't stream my monitor right now because of "bla" "blabla" (some private shit that has ZERO to do with work).
I'll need some oxy if this goes on.2 -
A tale of silos, pivots, and mismanagement.
Background: Our consultancy has been working with this client for over a year now. It started with some of our back-end devs working on the API.
We are in Canada. The client is located in the US. There are two other teams in Canada. The client has an overseas company contracted to do the front-end of the app. And at the time we started, there was a 'UX consultancy' also in the US.
I joined the project several months in to replace the then-defunct UX company. I was the only UX consultant on the project at that time. I was also to build out a functional front-end 'prototype' (Vue/Scss) ahead of the other teams so that we could begin tying the fractured arms of the product together.
At this point there was a partial spec for the back-end, a somewhat architected API, a loose idea of a basic front-end, and a smattering of ideas, concepts, sketches, and horrific wireframes scattered about various places online.
At this point we had:
One back-end
One front-end
One functional prototype
One back-end Jira board
One front-end Jira board
No task-management for UX
You might get where this is going...
None of the teams had shared meetings. None of the team leads spoke to each other. Each team had their own terms, their own trajectory, and their own goals.
Just as our team started pushing for more alignment, and we began having shared meetings, the client decided to pivot the product in another direction.
Now we had:
One back-end
One original front-end
One first-pivot front-end
Two functional prototypes
One front-end Jira board
One back-end Jira board
No worries. We're professionals. We do this all the time. We rolled with it and we shifted focus to a new direction, with the same goals in mind internally to keep things aligned and moving along.
Slowly, the client hired managers to start leading everything in the same direction. Things started to look up. The back-end team and the product and UX teams started aligning goals and working toward the same objectives.
Then the client shifted directions again. This time bigger. More 'verticals'. I was to leave the previous 'prototypes' behind, and feature-freeze them to work on the new direction.
One back-end
One conceptual 'new' back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One functional prototype
One back-end Jira board
One front-end Jira board
One product Jira board
One UX Jira board
Meanwhile, the back-end team, the front-end team overseas, all kept moving in the previously agreed-upon direction.
At this stage, probably 6 months in, the 'prototypes' were much less proper 'prototypes' but actually just full apps (with a stubbed back-end since I was never given permission or support to access the actual back-end).
The state of things today:
Back to one back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One 'working' front-end
One 'QA' front-end
One 'demo' front-end
One functional prototype
One back-end Jira board
Two front-end Jira boards
One current product Jira board
One future product Jira board
One current UX Jira board
One future UX Jira board
One QA Jira board
I report to approximately 4 people remotely (depending on the task or the week).
There are three representatives from 'product' who dictate features and priorities (they often do not align).
I still maintain the 'prototype' to this day. The front-end team does not have access to the code of this 'prototype' (the clients' request). The client's QA team does not test against the 'prototype'.
The demos of the front-end version of the product include peanut-gallery design-by-committee 'bug call-outs', feature requests, and scope creep by attendees in the dozens from all manner of teams and directors.4 -
Our company hired a "Human resource consulting" to help with our internal processes and policies. Yesterday they showed us an Excel that we should fill when we travel to attend meetings, events, courses, etc.
This spreadsheet... OH, THIS SPREADSHEET... you should've seen that.
Most of the "labels" of the "fields" were writen with terms that we do not use in our daily basis. The fields were ambiguous. You shout put a number on the Transportation quantity (ex.: 5) but have no space to describe which transport you will use (bus, metro, uber... so... 5 what?). When we asked which name shoud go on the field "superior" (director, pm, scrum master...) the woman from this consulting said "oh, I don't believe you're asking about this" (and since then, she became more rude by the end of the meeting).
We care for quality in our apps, and UI/UX is a big thing in our company. The last thing we want is need to read a f*#1n manual to fill a spreadsheet. Make it intuitive and you will not need an hour and a half to explain how to fill this obsolete form.
It's sad to think that this person was hired to improve our company, but did not bother to understand the company's culture (and values, and terms) first. -
There is an "SA" who doesn't know anything about different architectures used around, does not ask if he doesn't know and assumes stuff and puts us in those cringe-worthy moments where everyone in the meeting kind of becomes quiet because he is uttering obvious bullshit. He does this in meetings with senior managers and developers from other teams which clearly puts our team down!
-
Too many to name. In general though any meeting that could have been a short email and meetings about planning future meeting.1
-
Recruiters or their bosses with sick ambitions and zero feedback.
Do I need to say more?
Spent few days to make my site looking good on desktop/mobile with few screenshots and even video to show my working projects in production. Even more few days to make really detailed 2 A4 CV with my previous job and what I was doing there. All generated from markdown.
I even saved money around half a year to go and live month in other country (Ireland, Dublin) and then on site send about 150 applications on various sites, emails, linkedout and local IT meetings.
Null, nada, nil, NaN accepted applications.
Is it some kind of joke? All companies almost cries for new workers and they don't even answer someone which founded and have no problem with growing own IT company for almost 5 years with self learnt, practically applied in production linux, HTML, CSS, JS, PHP, Go, bash, KVM and Openvz virtualization knowledge?
What they really want?
Astronaut with Brainfuck and Cobol with fluent backwards speaking Esperanto riding on monocycle with 3 hands and no need for sleep for -1 whoopercoin?1 -
Sometimes I really feel humiliated in my lab.
We have several presentation/discussion groups in my lab that meet once a week or so where members present their progress reports. Generally people in my lab are not so enthusiastic about them. Which is okay, I also don't like doing presentations, but you know, you have to improve somehow and get feedback somehow.
So I've been in a really passive group for a while and I decide to join this other group since they seem to have good discussions, but nope fuck me.
The first time I present, the professor doesn't show up since he has some meeting, so obviously nobody cares to show up. And I'm there presenting for a guy who is half comatose. Alright, I guess that's the price for joining a new team, it's gonna get better next time.
Second time. Spent all night to prepare my presentation and been training my model for two weeks. I am actually really happy with the results of my networks. But the enjoyment of showing some good results, I shall not have.
Meeting leader doesn't show up. Two guys who should present don't show up. Professor doesn't show up. A different professor substitutes him and has no idea what I am talking about and asks stupid questions that don't really have an answer. Fuck me, I'm so angry, this shit is a waste of time. If you don't show up, care to fucking send an email or a message on slack, but guess you're too fucking retarded to even do that.
I'm so done with this. I've gotten better feedback from reddit, than what I've cumulatively gotten from my laboratory. I'm a moment away from walking up to the meeting leader and telling him that the meetings are stupid and a waste of time. Don't get me wrong, my professor is really nice and knowledgeable, but he fails to see that some people in the laboratory are shit.
What do I do? How do I deal with these people? Right now they're planning a trip! Why are you planning a trip? WHAT ARE YOU REWARDING YOURSELVES FOR? YOU HAVE DONE NOTHING IN WEEKS? omfg3 -
When the monthly scrum retrospective reaches the 90 minute mark...
You know when people are being stress tested and they break by getting up, run around screaming and ultimately knock themselves unconscious by running into a wall?
That. I felt like doing that.
I swear someone activates some sort of gravity well when these meetings begin because time beings to stretch on and o........n....... while they meetings happen.
I began to list things I think I'd rather be doing than be in that meeting.
1) Tax returns.
2) Prostate exam (not old enough to need one yet but at least I'd be out the meeting).
3) Visiting the dentist.
4) Assembling IKEA furniture.
5) Watching soccer at least they have the decency to give you a break in the middle and I find sports as engaging as a dog turd on the sidewalk.
So bored was I that I began to notice notches and holes in the ceiling tiles and when I remarked upon them others became engrossed in them and began to speculate upon their origins.
I don't know who a speaker is, what department they are from, what product they're working on or what's so important about the algorithm they're working on. There is no context, no explanation and half way through a show and tell I had to check we were still in a show and tell.
I was bored shitless. I actually felt physical pain from boredom, I've not felt that way since I was a child.
I really, really hate that scrum is implemented in this way.
It left me with only half an hour of coding time left and really it sapped my energy and motivation to the point where I just went home early.
Excuse my language, but:
Fucking bloody cunting waste of time, I've had more productive moments in the restroom. They need to piss off or committed seppuku, ideally both. Dante got it wrong the seventh level of hell is this. I'm usually a very calm and balanced individual but yesterday, yesterday I just... Fuck! Argh! Fuck you meeting, fuck you.
If you are the type that schedules meetings like this:
May a thousand Jabberwockies plague your nightmares and be it that the next seventy seven times you lay with a human shall ye experience bitter failure! I hope Cthulhu himself visits his "enlightenment" upon you and you fear sleep henceforth.
I'm bringing a rubix cube or juggling balls into the next meeting so that I can say at least I learned something and it wasn't time wasted.3 -
Last week my PM scheduled a meeting for the whole team of 14 devs to talk about our tasks, how we can improve our workflow, so he's up to date on daily stuff nad sprint progress. After an hour and a half of lots of brainstorming i just asked
- what exactly do you want to achieve with all these changes?
- basically i would like on overview of current progress on each task
And he proposed couple of different meetings during the sprint, which would waste dev time. He proposed to apoint one person reaponsible to keeping him informed during each sprint. He proposed we change our meetings, our process, all of it.
So I just sat with my laptop during the same meeting and I prepared a jira board with swimlanes, filters, etc. Where you can sort by priority, size, what is blocked, what is, waiting in queue, what is being currently developed, what is being tested, what's ready for deployment, etc. Easy. 5-10mins of work.
- does this solve your problem?
-....
- you have everything here
-... What if someone doesn't update the ticket status?
- we check everything during our dailies, so, worst case scenario is the status is not update for 24h
-... Umm.. Yeah.. I think thats it. Thank you.
So, we basically wasted 20+ man-hours on another bullshit meeting because the guy thats supposed to be using these tools doesn't know them at all. After working here for 6 months. -
So my team got this new clueless "Delivery manager" who doesn't know ANYTHING ABOUT AGILE!
Her favourite timepass ? To eat development team's time asking stupid questions just to make her presence felt. And she does that by visiting each developer personally. MULTIPLE TIMES A DAY !
Why can't you leave the team and let them do some actual work??😑
She would join our scrum meetings to ask questions like "what are story points again?", "How do we calculate team velocity?"
Dear miss Clueless: It's not cool to be dumb! It's cool to take up an online agile crash course if you insist to contribute.
The other day, she suggested a QA guy to "test properly" with a smirk!
I mean seriously ? Was that actually necessary to tell them? This team was working just perfect without you. How about you look before you leap?
I try being nice to her but at times it's just too much to take. -
Tales From "PM vs Chen"
PM: *Walks up to Chen's cube*
Chen(that's me): *Taking off headphones* "Are we about to have another meeting about the meeting we just had?"
PM: "Yes"
Chen: "Okay. Just checking." *Waits for PM to share his thought*
PM: We're almost done.
Chen: "Yes" *Waits again for PM to share his thoughts*
PM: *While walking away* "Making Progress"2 -
Story time.
Previous role.
Have a BA working and overseeing the team.
Development is an absolute shit show at the company.
Basically constantly focussed on putting out fires and reeling from the 100 WTF’s a minute thanks to the batshit code the yes-men offshore Indian devs had created.
I’m quite outspoken, and don’t just roll over when people are cunts to me.
I ended up in so many meetings about communication and tone, merely because I wasn’t putting up with the BA’s two-faced cuntery where he tried to be my friend but at the same time be an utter fucking jobsworth.
Genuinely, I really got so close to decking him a few times.
Pic related.1 -
TL;DR The "senior dev", that the client hired on their end, is acting as a middleman between me and the project requestors. Taking the credit for my work.
I've already bitch about this before. I've been in a crusade to defend the production server from this fraud for a long time now.
But most recently he has removed me from all meetings with the actual project owner. I create the solutions, then he goes through them to understand it a bit. He proceeds to present it to the project owner in a way that almost blatantly says that he made it.
I'm sick and tired of working with this asshole. He is literally useless, worse he is slowing things down and breaking others.
I'm just gonna begin countering this... -
- have/share an agenda as soon as possible
- each talking point should identify a problem. Make a list of strategic questions answers to which would make it perfectly clear what and by whom has to be done to resolve them.
- plan meeting duration according to the list of questions. Make sure you meeting room reservation gives you enough time
- take notes
- be prepared for a need for another meeting(s), if during that meeting it comes clear that:
> more/other people need to be engaged
> some things are not clear and need more investigation before going further
> you have run out of time
> there are other problems tgat need to be worked out and it might cobsume too much time to do this in a current meeting
- do not turn the meeting into a chat. It's counter-productive, tiring to the listeners and a waste of time
- do not try to cover many topics. The less, the better. Unless they are very tightly coupled.
- do not invite people you do not need or there is a very slim chance you will need.
- only schedule meetings when the situation needs to be DISCUSSED among multiple parties
- that being said, do not schedule meetings when it's more convenient to communicate otherwise, like email, chat, etc.
- after the meeting make a summary and send it our to all the participants. They might reply and clarify if you have misunderstood smth or missed some important point.
- during the meeting assign tasks to each other. Verbally. Make notes. After the meeting reflect them in jira, rally, wtv.
- while assigning tasks nake sure the assignees have no blockers to work on them and make sure they understand what, when and how should be done. Some tasks might be dependedt on each other, work the sequence out.
- while assigning tasks ask "for ETAs. They might be as silly as 1-hour-to-2-weeks, but they still let you know what to expect.
- offer your assistance to the task assignees if they need any while working on their tasks
- work on your language, grammar, syntax, etc. Reading texts with typos/mistakes is repelling
- be a leader, an authority everyone is looking up to. Not a boss.
- avoid saying NOs. Be more of a "do we really need this; can we do this some other way/time; I can't promise anythibg but I'll see what I can do about it" kind of person. -
Am I the only one who feels like morning scrum meetings are a complete waste of time? At least in the way that my team does them. It's 30 minutes of "I did this thing yesterday, and I will continue to do that same thing today." All of this information can be sent in an email, but we insist on meeting every morning to say the same exact things.
For the past 3 weeks, the majority of the team has said the same exact things during scrum: "I continued to work on this big feature yesterday. Thank you." Like how does a detailed retelling of what this person did yesterday pertain to the rest of the team? It's just meeting for the sake of meeting, and talking for the sake of talking.
If you have this little technical issue that only pertains to work that this single person is doing, then meet with that person separately and discuss it. There's no reason to make everybody else sit and listen to information that will never be useful to them.
And most of the time, this scrum stems into spontaneous unplanned longer meetings afterwards. So suddenly this "quick" 30 minute scrum turns in 2-hours of meetings and a morning wasted on information that could've easily been discussed over email instead6 -
Alright , i am angry and sad to the point where i am taking timeouts just to evaluate my situation. So here goes the rant.
1. Ever since my senior has left there hasn't been any real filling of his position and i had to adjust to this new style of working . I had raised these concerns with my tech lead before and he said that it would be managed by a joint support of other seniors, and my effort. But things are going .. awkward (rant link for the senior leaving story in comments)
Like recently there came this big task of creating a new referral link screen that came onto me. at that time i was not even aware of the flow or the frontend/backend communication , but it was discussed on the first day of sprint only so i thought yeah i can do that ( side question #1 : how do you count the days in sprint ? Is it 10 or 14 days if weekends are a holiday?)
So i decided a personal plan and i guess made the first mistake :/ . My plan was like this : as i am alone working on this screen, i should read the already available code to get the better idea. Once i have doubts i will ask tech lead . Then i will start working on it.
But what i actually did was i started reading the code, but meanwhile the manager was continuously asking for status update and making requirements changes, so TL and i sat and used an old screen code , refactored it and made some work on it. I was happy, a lot of my work was done when i sat with TL. I just had to add the ui. Easy stuff ,right? NO
The tl and i had actually integrated understood wrong and integrated a different api. For TL who knew all code he said "oh okay, no big deal. Ywtf, just check this code here in x file nd integrate likewise" . BUT I DIDN'T UNDERSTOOD THAT CODE,YOU DID THAT MANN!
Anyhoo i sat back looking at the 2 files , 1 for the new wrong code and 1 for the old unrelated code, tried to understand all the working without the actual logics and api calls for hours and hours until i rewrote the whole ui part and had very narrow scope questions about the api. This process took quite time and in the process i caught the issues from a lot of people : the manager had missed crucial cases when she said "like we did before" , the designer had missed important ui views that governed various logics and the already present code was also making some unneeded calls which could have been removed.
This took 2-3 days and weekend the next days i was scolded by TL about why its taking time. Like wtf? No one's helping me , i am like a blind man with a broken stick trying to touch everything and understand what it is. But he's a cool and awesome guy , he asked another senior to help me , that senior sat with me , listened to what i have been doing , pointed all the problems , reviewed my code and finally we were able to get that feature done. Pheww, right? Nah.
#2 ) By the time we finished it, next sprint has already started and that too had some big big changes. Ughh.
but this time i already told my TL that i will either work on code after a proper KT of line by line, or assign some senior to me who has the knowledge of code and could command me what to do. So things started correctly this time.
#3) However again the managers are being stupid and continuously iterating the requirements. Me and this senior are very calmly handling this stuff but the SHEER AMOUNT OF MEETINGS OH MANN FUCKKK.
- Morning standup
- mobile team standup,
- manager messaging on slack with @a @b @ywtf @c @d , hoping for a discussion
- Standup for future feature discussion,
- standup for feature kt,
- "hey ywtf , i wanted to test your old feature from a 1000 years ago now because i am another lazy tester person, shall we connect on call?? "
Aagh kill me now . I am already a miserable guy trying to code in standard office hours ,your meetings are making elongating my work time to 14-15 hours :/
I think This is neither a waterflow nor an agile mode of development. We are applying waterflow on the devs while trying to get them work at speeds of agile . I mean like working till 10 or 11 pm and then after 12 to 3am has become so common for me that i have forgotten what extra stuff i should be doing. My life is like meetings + very less work in office time, work in after office hours , eat sleep..FML9 -
I drop a pile from top of my head. Don’t bother to read.
About release:
When is release ? ( discussed 2 minutes ago )
Who will release ? ( there is always same person doing it )
What was added ?
What information add to clients about release ? ( it was always the same )
About bugs and features:
There is this bug.... ( without specifying)
It doesn’t work. ( there are 3 environments )
Is this ok ? ( clicking randomly )
Is this bug fixed ? ( without specifying )
Where is this feature ? ( while looking at webpage with feature )
How to use this ? ( not specifying what )
Where ? ( while clicking randomly )
When ? ( while scrolling calendar )
Why ? ( still clicking )
Where to click ? ( what I am doing here ? )
About meetings:
When is meeting ?
Where is meeting ?
Why we’re meeting?
Who will be there ? ( information in calendar )
I heard all of them at least once per month. Now I’m recovering at home and my friends are asking why I’m tired. -
When you bullsh*t stuff the whole meeting, then they setup a meeting tomorrow to continue where you left off today
-
So just got news via comments about retarded devs leaving twilio creds. in their apps published to the app stores, attached below is an interesting snap of the document appthority has published, wonder who is getting beat up right now for leaking corporate meetings 😶4
-
When you have so much work
To do, but can't start any of it until you have the meetings about it. Meetings meetings meetings.2 -
So either i am in a tight position and about to get fucked or everything is just in my head. Its been 3 months since i joined this company. sometime after joining, i was assigned to a core part of product say X, where me and 1 senior(say VV) would work on various tasks and bug fixes. I , being a fresher and junior would attend meetings alongside, the senior bosses would tag both of us in every task, but he and i would divide the tasks amongst ourselves .
I would usually get smaller tasks that i would spend some time with, finish up in 3-4 hours and then make a PR for his review. he would work on larger bugs, fix them and make the build.
Everything was fine until 1 day, he calls quits and is now leaving the job in a week . Now am not sure how this all is gonna fare out. the code he use to write was … very different for the lack of better words and even though i have a rough idea of how code is working, there are huge gaps in my knowledge .
I don’t know how company is gonna play this out. would they be hiring new senior dev? would they be expecting me to fix stuff as “YWTF knows the code as he have worked alongside VV on it” . because in the latter, am truely shitting my pants because am not ready for this !!5 -
omg this is not what the meetings are about!!!!! keep dumbass questions to yourself until the q/a period...
-
I’ve had meetings specifically for team A’s problems. Team B gets invited to assist. Within ten minutes the meeting was all about team B and none of team A’s problems were solved. “Team B” is notorious for hijacking meetings. I’m not a psychologist. I don’t feel qualified to speculate about WHY they do this...2
-
just as Erik Meijer said scrum is the most stupid shit in modern development process. I worked in an organization hires ppl as full time scrum master, which is joke. each day the asks what did u finished yesterday and how long it need to finish the task assigned to u. btw the scrum masters know nothing about programming. come on man how can u finish any serious shit in one day and who cares how much shit others finished. each week just attending those freaking meetings without coding. each programmer are assigned at least 5 bosses, and what the fuck is product manager doing, it's not adding indirection can solve anything.2
-
My love for you I can't describe it,
so I dont't even try and hide it.
Dev. you are my one true passion
you are always there to teach me a new lesson.
Some missing semicolon;
I have searched for you soo long.
Or was it a wrong indent,
ah f**k it was the missing increment.
Thinking through endless loops
in while, for and even do form,
just that my programs do a little better perform.
You give me the possibility to express myself as who I am and who I want to be,
in so many languages, from java, JS, GO, python and even C.
You give me bugs and issues that I track,
from motivation for you I never lack.
There are projects out there, where I contribute to
oh what a beauty are you.
And now you even bring fun into my life
with devrant, I now know how to survive.
How to survive client meetings and non devs around me,
oh how much stupidity I there see.
Let's exit this small programm of mine, this so called rime,
where I an immutable statement define:
I think about you even when we are not together,
My dearest DEV I will love you forever. -
We were having a project followup and a colleague starts boasting to the client about her perfect school grades, so a friend, our tech lead and I start sending messages mocking her, so the tech leads bursted laughing in the middle of the meeting, then the pm asked him what was going on and he rated us out, since then he never uses his cellphone again during meetings.
-
Working with a group on a startup idea. We have weekly Google chat meetings with the full team and sometimes me and the other two founders have side calls. Our group is getting bigger so the weekly is getting longer so the 3 of us were talking about ways to make them more efficient. One was, background distractions like TV, random people talking in bg, kids...
So then yesterday the 3 of us went over a different topic and the guy who had brought up the distraction issue was in the bathroom shaving and trimming nose hairs the whole time. He kept asking questions about the agenda which we all had access to. I shouldn't even care much. I drink through the meetings anyways.2 -
The meetings for SEO.
The SEO guy is really, really nice. He's patient, comprehensive, he's quite good looking and everything, but my boss is a total moron when speaking about internet stuff. He makes us repeat everything at least three times, he will note everything on a sheet of paper that he will lose and write again... these reunion last 2 hours and we have one twice a month. Uuuugh... -
The futility of working in a bank, or probably any other big corporation.
I was working in a small dev team that made improvements to the applications and processes of the department we were in. I was given the project of creating a small data entry system to track some communications. The comms were currently stored in a spreadsheet and had no validation which made any analysis of the data difficult.
Boring but easy, should have taken about a week.
We had 3 meetings just to define requirements, they took about a month to send me their shitty little spreadsheet so I could actually see what they were recording. Over the next 2 months they kept changing what they wanted. Finally got it finished just before I went on maternity leave.
Went off thinking, that I’ll never have to deal with that clusterfuck again.
Had a baby, went back 9 months later.
First thing I got given was that shitty project back. They hadn’t even tested it - in 9 fucking months! I transferred departments not long after. I have no idea if it ever got done.
And that is on my list of reasons as to why I’ll never work in a large corporate again.3 -
Worst meeting I've ever been in.
Everyone texting, then complaining about the number of meetings. If this is terrible let's make it useful and have one good meeting! -
Story of my first successful project
Being part of a great team, I've shared in a lot of successes, one I am particularly proud of is my first attempt to use agile methodologies in a deeply waterfall-managment culture.
Time was June/July-ish and we applied for a national quality award where one key element in the application stated how well we handled customer complaint resolution.
While somewhat true (our customer service is the top-shelf good stuff), we did not have a systematic process in resolving customer complaints. Long story short,
the VP lied on her section of the application. Then came the 'emergency', borderline panic meeting (several VPs, managers, etc) to develop a process to better manage
complaints before the in-house inspection in December.
As most top priority projects go, the dev manager allocated 3 developers, 2 DBAs, and any/all network admins we would need (plus all the bureaucratic management that wanted their thumb in the pie).
Fast forward to August, after many, many planning meetings, lost interest, new shiny bouncing balls, I was the only one left on the project. The VP runs into the dev manager in the hallway and asks "Is my program done yet? If its not ready before December with report-able data, we will not win the award."
The <bleep> hit the fan...dev manager comes by...
Frank: "How the application coming along? Almost done?"
Me:"No, haven't really started coding. You moved Jake and Tom over to James's team, Tina quit, and you've had me sidetracked helping other teams because the DBAs are too busy."
Frank: "So, it's excuses. You really think the national quality award auditors care about your excuses? The specification design document has been done for months. This is unacceptable."
Me: "The VP finished up her section yesterday and according to the process, we can't start coding until the document is signed off."
Frank: "Holy f<bleep>ing sh<bleep>t! No one told you *you* couldn't start. You know how to create tables and write code."
Me: "There is no specification to write to. The design document is all about how they plan on reporting the data, not how call agents will be using the application to serve customers."
Frank: "The f<bleep> it isn't. F<bleep>ing monkeys could code against that specification, I helped write it! NO MORE F<bleep>ING EXCUSES! This is your top priority from now on!"
I was 'cleared' to work directly with the call center manager and the VP to develop a fully integrated customer complaint management system before December (by-passing any of the waterfall processes that would get in the way).
I had heard about this 'agile' stuff, attended a few conference tracks on the subject, read the manifesto, and thought "I could do this.".
Over the next month, I had my own 'sprints' and 'scrums' with the manager (at the time, 'agile' was a dirty word so I had to be careful of my words and what info I shared) and by the 2nd iteration had a working prototype.
Feature here, feature there (documenting the 'whys' and 'whats' along the way), and by October, had a full deployed application.
Not thinking I would get a parade or anything, the dev manager came back from a meeting where the VP was showing off the new app to the other VPs (and how she didn't really 'lie' on the application)
Frank: "Everyone is pleased how well the project turned out, except one thing. Erin said you bothered him too much with too many questions."
Me: "Bothered? Did he really say that?"
Frank: "No, not directly, but he said you would stop by his office every day to show him your progress and if he needed you to change anything. You shouldn't have done that."
Me: "Erin really seemed to like the continuous feedback. What we have now is very different than what we started with."
Frank: "Yes, probably because you kept bothering him and not following the specification document. That is why we spend so much time up front in design is so we don't waste management's time, which is exactly what you did."
Me: "We beat the deadline by two months, so I don't think I wasted anyone's time. In fact, this is kind of a big win for us, right?"
Frank: "Not really. There was breakdown in the process. We need better focus on the process, not in these one-hit-wonders."
End the end, the company won the award (mgmt team got to meet the vice president, yes the #2 guy). I know I played a very small, somewhat insignificant role in that victory, I was extremely proud to be part of the team. -
When people are too busy complaining about doing documentation while they are putting medical devices on the market with fatal defaults.
Oh sure, endless meetings and a little note in the manual will fix that..1 -
How do I help a software engineer student be better at developing software?
Background: I have this friend that started university with my young brother, two-or-so years ago my brother finished the career and got his degree while she is still there trying to finish the same career (!), we were looking the chance of changing careers but due to her low grades this is not possible and according to her U's counselor is better that she just finishes the career and gets her degree.
We scheduled a Zoom meeting for Sunday next week, to talk about her pain-points and see what improvement we can chase; issue is that I've never mentored anyone ever in my professional life (my brother from time to time drops a question to me or so, but that's different).
My plan is to either see if she suffers from lack of practice (meaning: she does not write software more often in order to improve her skills) or if it's hard for her to think in abstracts, either way, I believe that the latter improves if you do the former (just correct me if I'm wrong), thus the plan would be to assign her a bunch of programming exercises and have meetings at least once a week during her vacations.
My plan would be for her to actually learn game development with Godot, since the final result is always a game my hope is that having something to show encourages her to do the thing, but, who knows.
Have you ever done something like this for someone with the same issues? What was your experience and what nuggets of knowledge can you lend me?
P.S.: We don't live in the States but in Costa Rica, she does not have to deal with crippling student loans.6 -
Welp, it is panic attack time. Can't sleep because of work stress, which stresses me out even more. Can't get my work done because of bullshit meetings I can't skip. Coworkers are possibly being purposefully idiotic. Can't take vacation because we are in the middle of shit. I am not even coding, just writing documentation about the same crap everyday because of perviously mentioned idiotic developers. They have the same info as me, but refuse to work on even a draft version until I paint a screen WITHOUT the button they need to remove. I want to code so I can point at it and feel good, but no. And people keep talking to me. FUCK! AAAAAAAAAAAAAHHHHHHHH!!!!3
-
Me, working hard on a SQL project with a deadline that is half what it should be with no support from the other people on the project and was mostly made with with data I imagined would be in there cos no one could get me any fucking shit done (i.e. effectively designed, built, tested, fixed, upgraded, documented on my own for an entire weekly/monthly/ad-hoc analysis process that would output various reports for internal/external/management)
Manager - man who is a known waste of space but for some reason is in charge of the smallest part of the project, shouldn't have been fucking involved fucking management guzzling stain magnet...
Manager: Hey, do I need to refresh the database?
Me: .................
Me: .................
Me: ............I dunno, do you think we should refresh the database that this entire project is reliant? I mean...why do we need up to date transactions to analyse? Wait....you telling me it's not been being refreshed this ENTIRE time?
Manager: No....you never said I should. So should I?
Me: ..................I never said you should!?!? Are you not in the meetings talking about dependencies?????? Do you think i should have up to date trans or just run this with old stuff????? Why would you not update it!??!!?!?!? Its transactions...... (Desperately trying not to punch through my screen, through his, into his throat)
Manager: ..............
Me: .................
Manager: I think i'll refresh it and add it to the job?
Me: ....................(goes back to work cursing with music in so I think its quiet but who knows).
Tard, don't know how he even gets to work without someone holding his fucking hand.
Happy ending, I don't work there anymore :p
Sad ending, his spirit of tard follows me to my new jobs and possesses someone (or three sometimes) -
So, I have to begin with saying that I was 19 and my first real job. I was assigned to ongoing project for big german web company who outsourced project for german government. I am fast learner so I quickly ended up as a only developer who works on this project, because company had another important projects. And since I studied outside of my native country and I can speak Polish and English so I was also responsible for explaining everything to customer during meetings. I worked for around 4 months on the project and was heading up to the end. 3 weeks before production deadline client wanted show the results to the german government but I was still working on the functionality. My boss decided to put the web team leader to my project around 8 hours before this presentation to speed up the development. around 30 minutes before the pitch I realised that some of the latest functionalities stopped working. I was trying to figure out what I did I asked my team leader, he said that he have refactored some parts of my code. When we found the right commit it was around 3 min to presentation and after the checkout some of the .htaccess file was broken so I fixed it quickly but Germans started the meeting a bit earlier. The website was crashed almost half of the presentation. After 5 minutes my boss come to my desk and he says that he just talked with our customer and they are so freaking mad and pissed that they will not pay us. At this point I was certain I'm fired...
Suddenly the web team leader joined the conversation protecting me that it was the fault of the project menager because he should assign someone else to this project because even though I am good it is always good to have someone more experienced to work with you and review your code.
Project manager was fired about 3 months later. I was saved 😀1 -
Reading a couple rants from students and teachers lately, brought back to my mind a memory from the first lesson in my Software Engineering course when I was in college.
Teacher entered the room like he was the king of the world, turned around facing the students and started his intro speech:
"my name is {name} bla bla bla I will teach you software engineering bla bla bla let's point out one important thing: In your life you have written how many lines of code for a software? 10? 100? If you have NEVER written at least 1,000,000 lines of code for a program, you're not a developer. Now let's start talking about waterfall, endless specification requirements and meetings..."
Me 😐
And that was the moment I left the room moonwalking1 -
Impostor syndrome is too real. I frequent feel stress about tasks that are getting delayed. Saying yes to any task given to me (even if there isn't really time for it).
Most recent I had a 1 man project (which I hate, cause I always think it's better to work in teams). It was estimated to take 1 week and ended up being done 2½ weeks after. Remembered I took 1 sick day, just feeling awfull about the project being so delayed and couldn't get my self to go to work.
Well week after the project was done, I had a "employee development conversation" with my CEO and my boss. (like I do every half year). As always they loved to have me on the team and thought I was doing a great job. Same thing I always hear to these meetings.
Deep inside I know I am doing a good job. Keeping up with new things. But my problem is always taking to much on my plate. In the middle of all the code and stuff, I always seem to forget that I am doing a good job and doing my best and start feeling worse again. It's a really bad cycle and causing me to take "fake" sick days just to cool down again. (which often makes me feel even worse, for letting the project getting delayed more).
// DevRant / DevConfession2 -
!tech . Tldr = last para
I have been doing this social experiment about my interaction with the people for last 7 something years and here are some of the details and observations:
- i graduated college in 2020. All the people ihave met in the last 4 years (related to college ) were connected to me via whatsapp in muted/unmuted groups. During college the interactions were usual but once we all got the results in hand, all the groups were gone quiet. The only interactions were when someone posted an interesting status and the other commented in 1-1 chat. 1-n or n-n chats were completely 0.
My experiment was to not post something for a month and even mute status update so that I don't get to see what they are doing. And a month after , i am rarely even opening whatsapp as there are no chats
I finished my school in 2016. At that time all my schoolmates were obsessed with Facebook, like we would play games on fb , like/comment on posts have group chats etc. There also i got the same results : deleted fb after 12th results and today I don't even remember the names of my batchmates(guess they feel the same about me)
We moved to a different locality in 2011. At the new place, i would initially go to park, play with local guys , chat with this neighborhood girl of my age, went to the same tutions.
Later life happened, studies got tougher, i stopped going to parks, the girl and my family clashed over some topic and we changed tutions later. 10 years past, 2 of the guys are still my homies with whom i get on call every now and then, and the rest people are like , we meet in the streets, say hi and on our way..
My parents got in clash with their siblings amd families when i was like 5 or 6. Since then , the uncles/aunts would occasionally call/meet their would be some fake interactions and meetings but once they woul go away (or we would come back from their house) , everyone would take a big sigh of relief
Moral of the story is :life happens. I would have met 7-8k people in the last 10 years, would be on a daily interaction relation for a period of time and then all gone. New people , new time period and old ones now just a name in contact book.
Its not like i lost every friend , there are around 1-2 people that i interact with on a daily level and 9-10 people who i contacted in the last 30 days, but the point is its just not me who don't wanna interact. Everyone just simply moves on.
We humans pride ourselves of being the "social creatures" , talking about scaling and reaching out to millions of people, when we can't stay in touch of 50 people from our football team or graduation batch or something like that.
And this end brings me to a question for all the 35+ people : how are you all surviving in the world? Is it just me loosing all the touch with my contacts (intentionally/unintentionally) or is it for every one? And is anyone even trying to maintain those relations?are those relations worth maintaining?7 -
I really dislike being the only remote in meetings.
Everyone keeps talking to eachother in person, and I can't hear them. Letting them about that is such a pain.
Every comment you make sounds like it's interrupting the conversation as well. It really sucks... -
The needs of the many outweigh the need of the few, or one.
Yet they fucking stopped all the trains in Sydney because one idiot climbed the power lines.
How about those people who missed their job interviews? Business meetings? Doctor appointments? Scrum meetings? No they had to stop all the trains18 -
As an intern a couple of years ago I was in a meeting about our department were having to many meetings. The outcome was two more meetings and a workshop about how to have more efficient meetings.
-
I’m from the UK, should I go freelance?
Last few weeks I’ve been feeling really bored with my job. Like mega fucking bored. It’s basically just meetings 7 hours a day, 4 hours planning and then 3 hours of talking about how everything didn’t get finish (I know. I keep saying it’s the fucking 7 hour fucking meetings).
Pay is pretty decent, we have a few juniors, not exactly great code base, kinda cool idea, pretty unique, business will defo work or be sold by corporate owners. (Start up owned by corporate)
I just feel really flat and bored. Mega bored. Keep wondering about going solo and being more of a consultancy or my own little agency? I’ve tried before but I suck at marketing and freelancer and similar sites never provided enough income.
I guess my questions are (if anyone wants to answer):
- What’s this new IR35 or whatever? Is it now pointless to be self employed?
- how would I boost my leads?
- should I do a bit of contracting to get used to it maybe?
- should I just stay where I am and deal with the feeling of not really feeling like I was hired to do anything?
I do also have a little side business I started that I could also work on whenever I have free time, it’s not taking any money at the moment though, early years I suppose?
I’m really sorry if anyone feels offended to read that I’m fucking bored and don’t have a clue what to do with myself. Please don’t reply with some sarccy comment. I really cba to have an internet keyboard troll fight about some stupid opinion we’ll all forget about in a few days. This now counts as a rant. So fuck you. It’s a rant. And I’m rant about the possibility you might comment on my post not bring a rant coz I can’t tell what category I’m posting on. I live in the 5th dimension. Deal. With. It. Or just ignore and scroll on 👍🏼5 -
So, I'm an intern and I'm always eager to learn new things and do new things. I want to give all the knowledge I have to improve the projects at work.
I give a lot of opinions about the projects I'm working. Ways to improve it. I sometimes ask why somethings where done that way, to understand.
My supervisors don't like that.
Sometimes I get very anxious because my life is very fucked up in the moment.
I think no one there likes me.
It's funny because in one of the meetings we had about this at some point in the conversation, I don't remember why, they said that "people are not robots", "people have feelings".
But they are always mad about something I said or asked (meanwhile, everyone else are saying bad things about the projects, about other people, even about HR).
I guess people need to unload their stress into someone.
I just want to finish this internship, get my fucking grade, and get out of this fucking company.
I'm thinking about turning myself into a robot.
A human robot.
I'm only going to say: yes, ok, sure, yes sir, hello, goodbye.
Just work like a robot like they want.4 -
Our clients came from abroad to have 4 days of business meetings and planing about next stage of product development. Of course they wanted to go shopping and to restaurants etc. Obviously they can not call a cab because they cannot say the name even close to its correct pronunciation. Who do you think needed to babysit them? You guessed right - me. FUCK MY LIFE2
-
!wk94
Those meetings.
Those bloody meetings are nothing but time suckers. Much akin to some family event where they bring everyone together, regardless of their relevance to the agenda.
Also, the fact that we have been scheduling some important meeting always since 2 fucking months, only to be declined ALWAYS. The bloody meeting has been floating as an action item for 2 months, but none gives a fuck.
But no, we want to have meetings about meetings, and meetings about why a meeting didn't happen.
Also they ask us to stretch and accommodate, sucking time out of dev.
W H Y ?1 -
Hey guys. I am in a situation where I need to decide wether to take on a new project or not. And if not, how to turn down that client so that I would not burn any bridges. So I need your opinions on this matter in order to make the final decision.
To make things clear heres some background info. 10 months ago I quitted my fulltime position in another EU country and went back to my own home country. 10 months forward till today and I have my own ltd company which currently has 5 projects. Its doing pretty well money wise. All projects combined, I already earn more then I ever did and I need to work max 10 hours a week since all projects are remote projects so I dont waste time on useless meetings and etc. However I dont feel fulfilled or challenged anymore because surprise surprise doing well paid projects doesnt guarante your sense of fulfillment.
So I noticed that I have lots of spare time which I spend diving into rabbitholes with hobby projects. I decided that its time to scale my company and take on more projects and maybe even hire more people.
So I started searching for other projects I could work on (prefferibly remote projects or flexible ones where I could come in 2-3 days a week in office and work remotely rest of the week). Reason being that I am already out of sync with fulltime position lifestyle and I am totally result oriented, not punch in my hours and go home oriented.
For exampleIf i get my weekly tasks I prefer to do them in 1-2 days (even if it requires doing double shifts which rarely but happens) but then I want to have rest of the week off. Thats how my brain works and thats how Im wired. I cant stand fulltime positions especially in enterprise bigger companies where I come in and do maybe 2 hours of actual work everyday because of all useless meetings and blockers from backend/etc. Its soul crushing to me.
So I posted linkedin ads and started searching for new clients/projects. One month ago I went to an interview for an android project in a startup.
The project looked interesting enough. Main task was to rewrite their android app from java to kotlin. Apparently their current current app was built by a backend developer who wants to focus solely on backend.
So during the interview they showed me their app which was quite simple frontend wise but not so simple backend wise from what I was able to figure out.
Their project lead (also a backed guy) asked me my estimation of price and completion of task. I told them maybe 2-3 months to do everything properly.
Project lead was basically shocked because all other candidates told him they can rewrite the app from java to kotlin in 2-3 weeks. I told him that everything is possible but his app quality will suffer and for a better estimation he would we would need to sign an NDA so I could evaluate the costs. So we ended the interview.
After that we kept in touch for one month (it took them one month to google a generic NDA and sign it digitally with me).
So heres the redflags I noticed:
1. They dont respect my time. Wasted 1 month of my time and after signing NDA gave me 2days to estimate their project and go to a meeting and give them detailed info about what I can offer. I thats not a brain rape then I dont know what it is
2. They are changing initial conditions we talked about. We agreed on rewriting the codebase and be done with it. Now they prefer a fulltime worker who would be responsible for android app as his own product. So basically project lead was not able to find a fulltime dev so now hes trying to convert me (a company owner) to his fulltime worker.
3. Lack of respect. During the interview he started speaking in his own native language to me with some expression (he seemed pissed off at that moment when he switched languages).
4. Bad culture fit. As I said Im used to relaxed clients and projects where I dont need to be chained to a desk a monitored and be micromanaged. I mean lets sign a contract give me access to your codebase and tell me what to do, I will produce results and lets be done with it.
5. Project lead is a backend guy who doesnt understand how complicated android apps can be. No architecture and no unit tests are in his frontend app. He doesnt care about writing proper app since he ships it in his own device so he doesnt need to worry about supporting custom devices or different api levels of android and etc. But not having any architecture? Cmon.
So basically I am confused. Project lead needs a fulltime dev but hes in contact with me in hopes that I would sign a fulltime contract. But how I can work fulltime if all what I can see are redflags?
Basicaly I thinkthis was a misundersanding. Im searching for fulltime remote projects and hes offering fulltime inhouse projects. Project lead never outsourced so hes confused as well.
As you can see decision is already basically made to turn him down, I just need to know how to tell him to fck off in the most polite manner and thats it.6 -
i think it's nice that the company wants to include me in the administrative meetings, but honestly i have no clue what they are talking about and i could be doing my tasks
-
It is my new aim to use the most ridiculous naming frameworks so I can talk about them in corporate meetings. Discovered chaos monkey today. What else you guys got?2
-
I saw a post on Twitter about a company's management luring developers to meetings that they don't want to attend. THEY HAVE STARTED USING FOOD TO LURE DEVS TO MEETINGS!
Devs!!!! It's a trap!!🤣1 -
The first dev project, like real dev project, I participated in was a school one and it was double.
The class was meant to make us learn about the software's life cycle, so the teacher wanted us to develop a simple, yet complicated, thing: a Web platform to help tutors send/refer students to the university services (psychologist, nutriologist, etc) and to keep track of them visits.
We all agreed on it being easy.
Boy were we so wrong.
I was appointed as dev leader as well as some others (I was the programming leader, the other ones were the DB guy and the security guy) and as such I was in charge of the technology used (well, now we all know that the client is the one in charge of that as well as the designer) and I chose Django because we had some experience with it. We used it for the two projects the teacher asked us to do (the second one was to find a little shop and develop something for it, obviously with the permission and all that), but in the second one I decided to use React on top of Djangl, which ended being a really good combination tho.
So, in the first project, the other ones (all the classroom) started to discuss and decided to use some other stuff like unnecessary carousel for images, unnecessary functions, they created mock ups for stuff that was never there to begin with, etc. It was really awful, we had meetings with the client (the teacher) with updates on the project, and in not a single one he was satisfied with the results. But still, we continued with the path the majority chose and it was the worst: deadlines were not met, team members just vanished until the end of the semester, one guy broke his leg (and was a dev leader) and never said a word not did anything about the project. At the end, we presented literal garbage, the UI was awful, its colors were so ugly because we had to use the university official colors, the functionality was not there, there literally was a calendar to make appointments for the services (when did the client ask for that? No one knows), but hey, you could add services and their data to it, was it what the client wanted? Of course not! What do you think we are? Devs?
Suffice to say that, although we passed with good grades, the project and the team was shit (and I'm counting me in)
The good part is that the second project was finished by me and it looked really good, yet it didn't matter, the first project was supposed to be used by the university, but that thing was unusable.
Then, in the subsequent vacations I tried to make pretty and functional/usable, yet I failed because I had a deadline for another thing I had to do, but hey, the login screen looked amazing! -
Dear god...I hate planning meetings. Especially planning meetings that aren’t even for my team. Just listening to these folks jerking themselves off about their accomplishments. Doesn’t help that the chairs are these painful folding chairs that hurt my ass.
-
Advice for software developers -
(Mention something according to your view in comment box :))
Solve a problem. A business one - that created the need for the software you are developing.
Software is such a complex product (like cars and houses), it requires a team of engineers. Employers pigeonhole developers into little specializations. You can happily stay a sniper, machine gunner, or radio operator in your squad arrangement. You can even go to the officer’s academy (business school) to be promoted through official channels. But you need to try it first: comprehending the whole battle and rising above the specialist rank. At least in your mind.
You don’t have to write the entire system’s code to do that. Just look at the big picture, identify problems not directly related to you, raise them, and help your teammates to solve them. Solve some yourself - something outside your specialty. Become a generalist.
Will your bosses reward you for that? Not a chance. You are not doing it to earn official brownie points or even get noticed. In fact you won’t be noticed in a good way. Your boss would think you are undermining him/her and aiming for his seat. You don’t. That’s a dead end too.
Even if they reward you, don’t get comfortable. Well, that depends on your ambitions. How much “higher” “salary” you want? The most important skill you just learned is solving a problem. You are a project starter now. Or project savior. You can do anything: research, analyze, design, and implement. If you need help with coding, you can split that work with others, while coordinating the development. Yes, your boss needs to be afraid. Who cares? Let him/her sit in meetings and write useless documentation. You can produce the same system w/o your company’s bureaucratic overhead.
So now you have two paths. If you know a valid niche: a consumer or business problem to be solved, you can start your own company. Hire capable friends, find like-minded people. Don’t quit your day job. You can manage “dual-tasking”. Today’s dysfunctional IT workload is not that high. And the abundance of open-source technology makes everything virtually free. Except for the developer’s time. You can pay others in equity - if you need them.
If you want the security of an established company, apply there. It doesn’t need to be your current employer’s competitor. You can go anywhere - after researching the company business, ideally their pain points, and bringing the solution plan. Or even a prototype.
They’ll look at you differently, even if you are completely off base about their pressing problems. Just the effort alone shows who you are - a high-level problem solver. I hope you understand the difference between a problem solver - who makes things work and the pain disappear; And a formal “Solutions Architect” selling something on behalf of his/her consulting company - or purchasing if he/she works in the IT department.
Beats coding exercises, doesn’t it? I know it’s not up to you at the interview. What’s up to you is finding a company to apply at the higher, problem-solver level. It won’t be easy. The current hiring system is focused on acronym resume filtering. Companies hire either scientists or acronym specialists. Not problem solvers. As much, as I hate this generic advice, w/o a an independent unbiased recruiting system, aimed to find problem-solvers, you’ll need to network - easier said, than done.
My point is, however you get to that interview, through recruiters or the best connections, you still need to convince them that you can solve a real multi-million problem to command the higher pay. Otherwise you’ll just be a slightly higher paid pawn, reaching your salary cap in a few years after a few job hops.2 -
PM comes into my office: "Hey, if <client> asks about his edits, just tell him they're scheduled for this week."
me: "I thought they were scheduled for this week, I thought that you were currently in a meeting to get final specs so you could tell me what needed changed."
PM: "Yeah, he wants to take the plugin from 5 steps down to 3, we told him it wouldn't be a problem and we would have it done this week."
me: "Ok, there are limitations as far as what I can cut out of the process, his tag line when he started as a client was '5 easy steps' and I built something that did what he wanted in 5 steps. Changing things this late in the game is not simple, I'm talking a minimum 6 hours of work."
PM: "Well I tried to make sure that what he wanted was possible but I didn't have a developer in the meeting. It shouldn't change anything that much."
He ended up scheduling a meeting with me and the designer to go over the edits Thursday afternoon. So I will have the new specifications which I said would be a minimum 6 hours of work and I will be given ~10 hours in which to do it. I sure hope nothing unexpected pops up while I'm working on this.
I'm also the only developer this week (and technically speaking I'm junior) since our senior dev wrecked his car over the weekend and isn't planning on being in all week. I'm the only computer literate person in the office of 50 or so, which means that if there is any kind of tech issue I'm ripped away from my desk for 'emergency help'. I have two other sites to get ready for client approval meetings by Friday afternoon and if the clients approve I will be launching their sites that afternoon as well.
The sign on my door currently says "Error 500: unable to handle your request" I need something to throw at these people.4 -
It's been about 3 months since I've become a lead dev. I've been working with this company for more than 6 years. And many of my teammates have also been working for 6 - 5 years.
We've been friends for all those period who joked, ridiculed, worked all nighters and everything for the last 5+ years.
But ever since I became the lead, I've been attending a lot of meetings. Some of it team related and some of it company related. The amount of meetings is so much that I cannot focus on coding. If I have to, it would have to be at home, which I don't want to do anymore.
I sort of feel that my teammates can share the responsibility of coordinating tasks within the team, but no one is stepping up. Even when I ask 1 person to do it, (s)he isn't interested in doing it. What should I do? I asked as a friend and not as a lead. I can talk to my manager and ask him to assign responsibilities, but just wanted to know if there is something else I can do.14 -
There was this tech guy in our project. I don't really know how techy nor what his role was, but I do know he was a techie.
Lately we'd noticed he was behaving more and more managerish. Orchestrating resources over slack, scheduling meetings, the managerial slang... Bulletpoints... It was obvious what's going to happen - he was striving for a manager's chair. Cool. He seemed like a guy who can indeed do this well. And the fact that he's a techie was promising - he should understand so many things.
Boy did that come around and bite us in our asses. Turns out this guy is a googler. If we are working on some case [as we always are] he jumps in and offers his opinion, although he is far from our technical area. We explain how/why it is not a good idea. Then he does some googling and comes back with a different idea! And insists on testing it out... FTR, a single test in our project could take from 1 to 6 hours. And he's a manager now!! We can't just ignore his requests...
Allright, we do that testing. Results are far from satisfying. We continue investigating. He does as well. We'd like to try something out, but there he comes with a new idea! And ofc we are asked to test it out as well.
Our own testing is postponed again.
A few days like this one pass by. In a daily meeting we are blamed for taking that long to do our investigation and we are questioned as engineers.
Superb...
Honestly? I'm having second thoughts about this new role. It's supposed to be fun and challenging and all, but this kind of shit is just too much...7 -
About 3 years ago, we had 4 different WordPress sites for various clients.
My colleagues thought it'd be a genius idea to keep them all in one repo. Even more genius, for local development, a single installation which implements a switcher for the wp-config.php files so we can switch between sites. Not bad in theory.
Fast-forward to present day. 1 client left; another site got converted to using Laravel because they always asked us to update their content so no point using a CMS; whereas the remaining 2 sites use differing versions of WordPress on their live sites, no less than 18 months out of date, have no dev sites, different collection of plugins and themes and both modified to the deepest darkest depths of fucking hell that's barely recognisable as WordPress anymore and next to no documentation or comments around the changes.
The functions.php file of one of these themes is over 4000 lines long!!!
We're keen to upgrade our servers to use Ubuntu 16.04 which defaults to PHP7, so all the already deprecated WordPress functions will then fail to work completely as will have been removed.
Both of these clients have agreed that they wish to convert Laravel as well so there's not really much point in going through the clean up process of their WordPress sites. Just copy the database nuke it all and start a fresh with Laravel FFS!
They also wish to completely redesign and discuss what features to keep/add/remove. With no date for these redesign meetings in sight, we won't be converting to Laravel any time soon, nor upgrading our servers in the foreseeable future either!
This is all because of one dev in the office and his history of failing to keep on top of breaking changes!
Fuck you! Seriously, fuck you!!!
If I was your superior, then you'd have been fired long ago!3 -
My company has 3 core partners but one works remotely nearly every day of the week and the other has his own business to run (attorney). It's funny being the one in the middle hearing about how each of them never knows what the other is working on for the company in an exasperated fashion, when all it would take is for them to talk to one another. I literally schedule meetings on their behalf just so we can all get on the same page. "Oh, you don't know what he's putting into that business proposal? We could just ask him and find out."
-
So Thursday our first beta client is supposed to go live. Tomorrow there is a team meeting to discuss the status. Team lead wasn't in at work last Thursday and Friday and gave me his work to finish, which I need to proceed with mine. I hardly made progress on it. So now I have to tell him about that tomorrow. And I'm dreading it so hard. More so because for some reason HR/support sits in on our meetings and will be on my ass again I'm not meeting deadlines. I did say last week it looked like it wouldn't be done in time but I was told it just needs to happen because the release date was already announced. So yeah the coming week is going to suck. And I'm on leave myself this coming Friday so I expect people to explode. I know I should just stop caring and get on with job searching but the whole injustice of being set up for failure by others and then being blamed really makes me mad.3
-
Meetings have the ability to slow you down like nothing else. The moment you feel you are about to crack the problem you have been working on.. ding! there comes a notification for the next meeting.
Currently my team has a mid sprint review meeting, an end sprint meeting, a let's plan the next sprint meeting, a team meeting, but the one I have absolute hatred for are daily standups.1 -
So... a fucking frontend developer is responsible for
- conducting meetings regarding the future of the website,
- talking to the bosses at their own desired times,
- researching on the designs,
- then asking the designer to make the design,
- then implementing those designs
- then again talk with the boss if he likes those designs, then again research ask designer to make designs, and then again fucking implement those designs?
Well fuck it. The politics everyone tries to play at different levels just to grill the poor intern is beyond repair.
A simpler flow could be that boss directly interact with the developer and the designer in a meeting, the designer could then come up with a design based on boss's suggestion, could interact with me and the boss regarding acceptability and practicality and then we could make it once and for all. But nope. 2large is the 10x dev intern that the world needs to grill .
The above is a somewhat exaggerated but real description of what I am currently facing. Since people are good here and am not being pressurized for the time delays, am somewhat cool about it.
But this kind of thing was something that haunted me to the core at another company, where people were not much nice. :|
Blames are actively being thrown on each other . Designs are impractical. the senior devs just "assumes" that junior/intern would magically make stuff without any instructions. And not just the product, but the 100% clean, bug free product, so they don't need to neither review nor provide a direction nor any help when intern couldn't do it.
"But you are an engineer , right? what did you do in your college life? Didn't you studied those subjects" : Fuck you, govi .
Welcome to "Product Based Startups" . God, how long I have to face such unfunctional systems? or do I have to just adapt and learn the art of lying, delaying and playing the blame game?1 -
Rant
The rumour goes that, with meetings with the highest staff, attendees lay their tokens (to enter the building) on the table in case they get fired and have to leave that very moment.
I once had to attend such a meeting as a simple application engineer. They had heard I could "do stuff with SharePoint".
The part about the tokens was a myth but that people get fired right away was not! One did get fired! I shit bricks back then. Especially when I got asked something very ridiculous and impossible... how would I say no?
Luckily I came up with an alternative.
But Damn. .. glad I left that place -
someone asks me : What do people not tell you about being a software engineer?
So the thing is , No one actually knows what they’re talking about.
See, the thing about building software is that usually you are inventing something.
Not in a pretentious way. I don’t mean “inventing something” as in inventing the light bulb, but I mean making something new that someone else hasn’t built before (well, hopefully — if you’re building something someone else already built, then you might be doing it wrong).
Because of this, people are usually just coming up with solutions based on what they think will work.
And that’s about the best you can do. Sure, the more experience you have, the more you can recognize certain patterns, or lay certain architectural foundations, but you’re mostly just coming up with something new. Maybe not 100% new, maybe some sort of slightly different thing than another thing that exists, but it’s still new.
So yeah, no one knows what they’re talking about. You’ll sit in meetings, with people talking about all kinds of smart-sounding stuff. Most people are trying their best to understand and play catch-up. No one wants to be the dumb one. People try to make it a science as much as possible, but if you really wanna be honest, people are just trying stuff and seeing if it works.
It’s not a bad thing. That’s just the nature of software development.6 -
The PM asks me almost hourly about my progress on this project. I am slowly training him to ask me through PM instead of face to face.
Meetings are now being taken at my desk through apps like Hangouts Meet instead of the Conference Room.
I'm chipping away, guys and gals....I'm chipping away.3 -
from rant import workflow
Tl;dr - I have a share of the product's backend, everyone expects it to work, no one cares how and i can spare with i, me, and myself getting there.
CTO: We need this solution, what do you need for data?
ME: Okay, thing0, thing1, thing2, preferably a ton of samples.
C: Here, also, there's a new full-timer who will help you. And you can do some sparing with.
M: Cool, i have several approaches to discuss.
*new full-timer attends fewer times than me as a part-timer*
*standup meetings talks about status, problems - yeah, whatever reactions*
*full-timer doesn't attend still, gets a "quick" (in case of consistently showing up) task to fix something in another backend part*
Me @ a standup lately: So, approach 4 worked, polishing it, but I soon-ish need to know a few things so I can finish up and fully integrate it.
CTO: Okay, when *full-timer* gets in so she's included.
*waiting for X days (x>8)* -
The people who run these scheduling meetings need to remember that this building is just one big tinder box ready to go up in smoke. 30+ minutes talking about bull shit that only affects a small percentage of the team. AND we're behind and dealing with a push that happened on a Friday before the guy who wrote the code left for vacation to go to Tennessee to watch the eclipse for some reason.
-
Stupid timeline, there is this company I was working for. It was sub-contracted by another company to do a government project. Government only pays after you deliver in my country. It was a complex system I must say. We were to work with my buddy on this project...now the timeline we were given were not feasible since another company had been given the same project and were not able to deliver. We had a meeting and discussed with our CEO about the project timelines. From the workload the feasible timelines were around 8months if we were to work as two devs. My CEO said that was not going to happen.. The only timelines that was allowed was not more than 3 months. So we suggest use an existing system to customize. .The meetings with the clients were to be weekly demos. So we choose to go with google docs api for the document management part. We were working around 20hrs a day to be able to achieve the target deadline..we management to complete the project within the given timeline..on the commissioning date of the project we faced a government panel and this was my worst disappointment. At the point of login we had to use Google email for business to obtain the API. Just as I was logging in the guy noticed and yelled. "Is that google account ?" and I replied yes..and he said "no need of proceeding since it will be of no use and they won't approve the system". That was my lowest moment in programming. I thought I had done the best project in my life as a programmer only for stupid man to declare my project as null. I felt like calling him son of a bitch but I knew that would have made me more angry...i just walked out. I went to the toilet and all I did was cry for the first time as I can recall.. My question was I was doing weekly demos. Why didn't they raise any questions by then so as to change the entire system??? Later after that demo we went and discussed about the issue and there was time extension. I redid the project using 'open office' but just before deploying the system I got a better job. I wasn't feeling like working on that project anymore. I want to release that project as open source. Recently after one year they haven't yet deployed the system. They are calling for my help. And I don't feel like helping after the humiliation...
-
I'm beginning to understand that thing about useless meetings that can be sorted out with an email.1
-
About a month after I quit a job, I dreamed that I would still work there sometimes having to sit through bullshit meetings and such, but since I'm also lucid dreaming at some times it allowed me to really mess with my old colleagues 'virtually' haha...
-
Why is it necessary that software be in a schedule meeting when software has 2 items on the schedule? This meeting is effectively useless for software. It is an unnecessary expenditure of money on a contract that is overrunning. It is right before we go on holiday break and they are training a new planner. And the lead is leaving in January so why is he still asking me questions about what I'm doing. Especially when I have told him what I am doing 4 times already. Fucking hell. Why is it that no one seems to trust me to do my job and be on top of things? And why is it that the people with shit memories are the ones that want to be involved in everything? And most importantly, why does everyone pretty universally hate meetings and regard them as useless yet insist we hold them?2
-
When you complain about having too many meetings, and then get invited to a meeting to discuss other meetings FMDL 😡1
-
Be honest. Given that you're not in crunch mode. Do you actually work 8 hours every day?
I have had some days but usually it's impossible for me to do actual work as a developer for 8 full hours, 5 times a week.
I feel that (without meetings), my ideal schedule for days of normal workload would be 5 hours a day. I'm strictly speaking about focused work, actual programming. Meetings don't usually rack up more than 2-3 hours per week for me.
I do my best to be in the office during the expected hours but I can't help but feel that everything about my engagement, focus and contribution at work would be better if I could just stroll in around 10, well rested, do some actual work, take a short lunch break, go at it again and go home around 15:30...
Because I feel like this I quickly get judgemental about myself if I come in at 9 and leave around 16:30 too often during a work week.
What are your thoughts on this subject?4 -
So, PM who has arranged 1.30 hours of meeting to ask us about 'the agenda' requested by client, decided to send 'another agenda' asking explanation what client exactly wants, which clearly wasn't the agenda of this meeting.2
-
So I am working in this startup at Stockholm for 6 months and 1 week ago decided to leave.
I am still under probation period(5 days left until probation period is over), so I should have actually given 1 months notice. However we had many meetings about this and we decided that I will give 2 months notice.
Like we decided, previous week I gave founders a notice of 2 months and they agreed to it. I sent them e-mail and they confirmed it so I have proof.
This week all of a sudden they are saying that their plans have changed and there won't be much work to do for me so they are are forcing me to leave after 3-4 weeks.
I understand their point of view. Since my salary is 41k, they are spending totally 53k sek on me monthly. So their idea is to save extra 53k sek by forcing me to leave 1 month earlier. Also I've heard that they plan to hire another person 2-3 months later after I leave, so essentially they will save 150-200k sek and that's fine, I get it, it's business as usual right?
What I don't understand is how can they be so inhumane?
We agreed that notice is 2 months. I informed all my relatives (since I will be leaving Sweden). I gave notice to my landlord (deposit is 10k sek) and etc. I wanted to have 8 more weeks to plan what I'm going to do when I leave.
When asked wether I can leave by the end of this month I didn't know what to answer. I said that I will need to think about it and now I'm "thinking" about it. First of all I mentioned to them that I am risking to loose my deposit. Instead of offering any compensation, they keep asking me how they can help me to leave as soon as I can?
Situation is really messed up.
Since according to the contract I am still under probation(even though I started working earlier than stated in contract, so technically I shouldn't be under probation) I have no idea what they can do if I don't agree to their terms.
As far as I know they are obligated to give me 1 months notice if they are firing me while I'm under probation, so it doesn't seem that I would have much power in this situation.
If I would try to force them to keep me around for total 8 weeks, they can just officially fire me while I'm under probation and I will have to leave in 4 weeks. However after one week I will become a permanent employee and then they will have to give me 2 months notice if they want to fire me. So it seems that they are trying to save their face by trying to force me to leave earlier on my own will.
My current plan is to agree with them and actually leave at the end of this month. But with conditions.
First I need to get in touch with my landlord, explain the situation and hope that he would give back my deposit even if I'm leaving 1 month earlier than I've told him before.
Also, since these guys decided to mess up my plans by trying to save some money, I think I should demand for some compensation? Like 10-15k? I had plans goddamit and we agreed that notice will be 2 months via e-mail after all.4 -
I've been thinking about "dress for the job you want, not the job you have" as I was putting on collage pants, sports shirt and construction work socks. How should I dress for the job I want, which is software research and development?
I do want to separate myself from the sales so noone gives me any of those duties. I'm comfortable working with existing customers through Slack and such + the occational development meetings, but not more then that.5 -
When you are about to finish a 4 month project with a client and he decides to hire a 'head of innovation' person one week left to project delivery. F*ck it, now you have to change whatever you agreed on those previous 30 meetings.1
-
How does a person get better at speaking in technical situations? I've been in the tech field for a loooong time now, but I really have trouble articulating my ideas. Someone else on my team can explain why our architecture isn't optimal because of X, and we should try to integrate Y because it buys us Z, and I usually can come up with some variation of "It sucks, because bad."
The things I want to say are generally the same as the person who makes sense, but my brain apparently has a disconnect between understanding it technically and being able to express it. I had kind of figured that by this time in my career I would have been exposed to this stuff so much that being able to talk about it would be easy, but it's not.
I've had Toastmasters suggested to me before, but I don't really need help talking in front of people. As long as I have time to prepare, I can do that kind of speaking with little trouble. I just want to be able to respond in meetings and informal situations and show that I do have a clue what I'm saying.4 -
"Hi, I was wondering if we have a way to <do a standard thing that we have support for, and has already been done in their project>"
Also, of course, let's CC every team lead and manager we can find so they all think it's something dire and we can end up in tons of meetings about it. Great. -
Traditional meeting when sales says "I need a technical guy for this meeting" and I ended up being the only "technical" guy in the room. Best of these meetings was when the customer would ask me about sales questions, disguised as "technical" ones...2
-
So I’m the frontend developer in this company. I am the one with 10 years of experience when it comes to html, css and js.
How can it be then that I’m not invited to frontend meetings?
I checked the meetings colleages have and came across a excel sheet. My name is mentioned about 10 times in this sheet. Which was what the meeting was about. However I am not a part of this? Wtf?2 -
Stand-up meeting at 9:00 AM in the boardroom. It's called stand-up meeting but everyone will be sitting lolz...
I hate this Monday meetings, too many stupid talk. PM mostly doesn't have any clue about the project. I bet she didn't update the client last Friday. -
doing documentation in word and having meetings about it, code reviews where people say great code quality with all good practices but... we would like to do it differently, reasons? less lines of code but real reason is not understanding design patterns, also 6 levels of hierarchy and wasted effort to prove that approach is good and considered as good practice just to be changed by someone who doesn't write code anymore. Decisions that other approach is better because they did it that way 10 years ago on last project where they were developers on totally different tech stack. dear friends, welcome to corporation!1
-
The worst meeting I was in I didn't know how bad it was until later. It was my first week at a new job, and I mostly just spent that week pulling tickets off of the top of the backlog and getting acclimated to the build environment and the project structure.
The meeting was a "sell off" where we would "sell" our efforts to the product owners, which were executives. After my project mentor went over the things we had accomplished, an executive asked why we accomplished those things but not the things that were asked for. I don't recall everything that was said, the basically our project manager threw us under the bus.
After the meeting, I looked at the backlog, and nothing that the Executives talked about was in the backlog, nor anywhere to be found. Our project manager, expected us to just "know" what we were supposed to work on, and create our own user stories. Apparently, what I found out after, was that the project manager went to one of the executives and complained that we, the developers never did what he asked and that we were just rogues working on whatever we wanted to work on. He was our project manager for another month, and he never created any tickets for us, even after two hour long meetings with the project owners. I honestly don't know what he did all freakin' day. He was always in work early. I'm sure a quick brush through his browser history would reveal some interesting things.
The results of that meeting led to this developer to not receive a bunch of RCUs with the rest of the developers amongst another things. Turns out those RCUs were golden handcuffs for everyone else. He left sometime after that and found another place. I interviewed at that place, too and got the job. Now I have the shortest, most productive meetings ever. -
Most useless meetings I attended was in my previous company. Our f***king boss suggested that manager must have to take one morning meeting with the whole team about that tasks what needs to be done. And our bastard manager calls the whole team and wasted time all of us cause our work is not related to each other so he is explaining one on one and rest are looking at his face what type of species he is :P