Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "pm problems"
First off, a Merry Christmas to everyone who celebrates, happy holidays to everyone, and happy almost-new-year!
Tim and I are very happy with the year devRant has had, and thinking back, there are a lot of 2017 highlights to recap. Here are just a few of the ones that come to mind (this list is not exhaustive and I'm definitley forgetting stuff!):
- We introduced the devRant supporter program (devRant++)! (https://devrant.com/rants/638594/...). Thank you so much to everyone who has embraced devRant++! This program has helped us significantly and it's made it possible for us to mantain our current infrustructure and not have to cut down on servers/sacrifice app performance and stability.
- We added avatar pets (https://devrant.com/rants/455860/...)
- We finally got the domain devrant.com thanks to @wiardvanrij (https://devrant.com/rants/938509/...)
- The first international devRant meetup (Dutch) with organized by @linuxxx and was a huge success (https://devrant.com/rants/937319/... + https://devrant.com/rants/935713/...)
- We reached 50,000 downloads on Android (https://devrant.com/rants/728421/...)
- We introduced notif tabs (https://devrant.com/rants/1037456/...), which make it easy to filter your in-app notifications by type
- @AlexDeLarge became the first devRant user to hit 50,000++ (https://devrant.com/rants/885432/...), and @linuxxx became the first to hit 75,000++
- We made an April Fools joke that got a lot of people mad at us and hopefully got some laughs too (https://devrant.com/rants/506740/...)
- We launched devDucks!! (https://devducks.com)
- We got rid of the drawer menu in our mobile apps and switched to a tab layout
- We added the ability to subscribe to any user's rants (https://devrant.com/rants/538170/...)
- Introduced the post type selector (https://devrant.com/rants/850978/...) (which will be used for filtering - more details below)
- Started a bug/feature tracker GitHub repo (https://github.com/devRant/devRant)
- We did our first ever live stream (https://youtube.com/watch/...)
- Added an awesome all-black theme (devRant++) (https://devrant.com/rants/850978/...)
- We created an "active discussions" screen within the app so you can easily find rants with booming discussions!
- Thanks to the suggestion of many community members, we added "scroll to bottom" functionality to rants with long comment threads to make those rants more usable
- We improved our app stability and set our personal record for uptime, and we also cut request times in half with some database cluster upgrades
- Awesome new community projects: https://devrant.com/projects (more will be added to the list soon, sorry for the delay!)
- A new landing page for web (https://devrant.com), that was the first phase of our web overhaul coming soon (see below)
Even after all of this stuff, Tim and I both know there is a ton of work to do going forward and we want to continue to make devRant as good as it can be. We rely on your feedback to make that happen and we encourage everyone to keep submitting and discussing ideas in the bug/feature tracker (https://github.com/devRant/devRant).
We only have a little bit of the roadmap right now, but here's some things 2018 will bring:
- A brand new devRant web app: we've heard the feedback loud and clear. This is our top priority right now, and we're happy to say the completely redesigned/overhauled devRant web experience is almost done and will be released in early 2018. We think everyone will really like it.
- Functionality to filter rants by type: this feature was always planned since we introduced notif types, and it will soon be implemented. The notif type filter will allow you to select the types of rants you want to see for any of the sorting methods.
- App stability and usability: we want to dedicate a little time to making sure we don't forget to fix some long-standing bugs with our iOS/Android apps. This includes UI issues, push notification problems on Android, any many other small but annoying problems. We know the stability and usability of devRant is very important to the community, so it's important for us to give it the attention it deserves.
- Improved profiles/avatars: we can't reveal a ton here yet, but we've got some pretty cool ideas that we think everyone will enjoy.
- Private messaging: we think a PM system can add a lot to the app and make it much more intuitive to reach out to people privately. However, Tim and I believe in only launching carefully developed features, so rest assured that a lot of thought will be going into the system to maximize privacy, provide settings that make it easy to turn off, and provide security features that make it very difficult for abuse to take place. We're also open to any ideas here, so just let us know what you might be thinking.
There will be many more additions, but those are just a few we have in mind right now.
We've had a great year, and we really can't thank every member of the devRant community enough. We've always gotten amazingly positive feedback from the community, and we really do appreciate it. One of the most awesome things is when some compliments the kindness of the devRant community itself, which we hear a lot. It really is such a welcoming community and we love seeing devs of all kind and geographic locations welcomed with open arms.
2018 will be an important year for devRant as we continue to grow and we will need to continue the momentum. We think the ideas we have right now and the ones that will come from community feedback going forward will allow us to make this a big year and continue to improve the devRant community.
Thanks everyone, and thanks for your amazing contributions to the devRant community!
Looking forward to 2018,
- David and Tim49
Just want to recommend the DevRant stress ball. I wasn't quite sure how to use it (it doesn't come with instructions) but since stuffing mine down the PM's throat my stress level has reduced dramatically.4
You know what?
Young cocky React devs can suck my old fuckin LAMP and Objective-C balls.
Got a new freelance job and got brought in to triage a React Native iOS/Android app. Lead dev's first comment to me is: "Bro, have you ever used React Native".
To which I had to reply to save my honor publicly, "No, but I have like 8 years with Objective-C and 3 years with Swift, and 3 years with Node, so I maybe I'll still be able help. Sometimes it just helps to have a fresh set of eyes."
"Well, nobody but me can work on this code."
And that, as it turned out was almost true.
After going back and forth with our PM and this dev I finally get his code base.
"Just run "npm install" he says".
Like no fuckin shit junior... lets see if that will actually work.
Node 14... nope whole project dies.
Node 12 LTS... nope whole project dies.
Install all of react native globally because fuck it, try again... still dies.
Node 10 LTS... project installs but still won't run or build complaining about some conflict with React Native libraries and Cocoa pods.
Go back to my PM... "Um, this project won't work on any version of Node newer than about 5 years old... and even if it did it still won't build, and even if it would build it still runs like shit. And even if we fix all of that Apple might still tell us to fuck off because it's React Native.
Spend like a week in npm and node hell just trying to fucking hand install enough dependencies to unfuck this turds project.
All the while the original dev is still trying TO FIX HIS OWN FUCKING CODE while also being a cocky ass the entire time. Now, I can appreciate a cocky dev... I was horrendously cocky in my younger days and have only gotten marginally better with age. But if you're gonna be cocky, you also have to be good at it. And this guy was not.
Lo, we're not done. OG Dev comes down with "Corona Virus"... I put this in quotes because the dude ends up drawing out his "virus" for over 4 months before finally putting us in touch with "another dev team he sometimes uses".
Next, me and my PM get on a MS Teams call with this Indian house. No problems there, I've worked with the Indians before... but... these are guys are not good. They're talking about how they've already built the iOS build... but then I ask them what they did to sort out the ReactNative/Cocoa Pods conflict and they have no idea what I'm talking about.
Well, one of these suckers sends a link to some repo and I find out why. When he sends the link it exposes his email...
This Indian dude's emails was email@example.com...
We'd been played.
Company sued the shit out of the OG dev and the Indian company he was selling off his work to.
I rewrote the app in Swift.
So, lets review... the React dev fucked up his own project so bad even he couldn't fix it... had to get a team of Indians to help who also couldn't fix it... was still a dickhead to me when I couldn't fix it... and in the end it was all so broken we had to just do a rewrite.
None of you get npm. None of you get React. None of you get that doing the web the way Mark Zucherberg does it just makes you a choad locked into that ecosystem. None of you can fix your own damn projects when one of the 6,000 dependency developers pushes breaking changes. None of you ever even bother with "npm audit fix" because if security was a concern you'd be using a server side language for fucking server side programming like a grown up.
Mine are still working.34
Boss: make this thing
Me: yeah no worries. Where is the spec?
Boss: We don't have enough one but we outsourced the design so call him
Designer: haven't started yet
Boss: I'm going on holiday. I'll leave this to you.
Me: erm ok. I'm having a few problems getting stuff out of the designer though.
*2 weeks later and still no designs*
Boss: I'm back. Where is the progress?!
*1 week later i get half designs that sort of make sense*
Boss: hurry up!
*1 week later*
Me: designer you're busting my balls here
Designer: yeah lol
Me to boss: still having problems. No idea what I'm doing.
Boss: deal with it
*2 days later*
PM: we are demoing it to clients tomorrow
Me: brilliant. I'll become a magician then.
* Meeting goes well and no one notices the thing is a bit buggy*
*2 days later*
Me to boss and pm: you already know whats going on but I'll keep trying.
Boss: ok it's just a proof of concept anyway.
Designer: yeah here's the rest of the designs lol
*1 week later, the designs made no sense, no idea what they wanted but hey it's a proof of concept so I'll just do my best...*
*suddenly again, hey you have 1 week before we sell it. Lol. smashes a product together as fast as humanly possible, due to half designs and no time to do it right even html classes and CSS aren't right - didn't know things would be repeated at the time. No time to fix entire thing. Luckily just a proof of concept*
New senior developer: hey boss just said this is being sold tomorrow.
Me: wtf..It's a proof of concept and i was given longer...
New senior developer: no
Senior developer and all colleagues: it's full of bugs and doesn't work
Me: yes that will happen without specs, random tight deadlines, no designs that made sense and a total of about a week and a half to make an entire system for multiple user types to make applications, send messages, post jobs, handle all paperwork and move paperwork among different user types as they go through applications. I told everyone what was going on but i get no support...
Boss: wtf i gave you so long! All i know is my entire staff is working on a product that should be done ages ago
Me: ok, however i have said almost every day i need-
Boss: I'm not interested
*I finish my placement year and never get any promised work or the job offer*
Welcome back to practiseSafeHex's new life as a manager.
Episode 2: Why automate when you can spend all day doing it by hand
This is a particularly special episode for me, as these problems are taking up so much of my time with non-sensical bullshit, that i'm delayed with everything else. Some badly require tooling or new products. Some are just unnecessary processes or annoyances that should not need to be handled by another human. So lets jump right in, in no particular order:
- Jira ... nuff said? not quite because somehow some blue moon, planets aligning, act of god style set of circumstances lined up to allow this team to somehow make Jira worse. On one hand we have a gigantic Jira project containing 7 separate sub teams, a million different labels / epics and 4.2 million possible assignees, all making sure the loading page takes as long as possible to open. But the new country we've added support for in the app gets a separate project. So we have product, backend, mobile, design, management etc on one, and mobile-country2 on another. This delightfully means a lot of duplication and copy pasting from one to the other, for literally no reason what so ever.
- Everything on Jira is found through a label. Every time something happens, a new one is created. So I need to check for "iOS", "Android", "iOS-country2", "Android-country2", "mobile-<feature>", "mobile-<feature>-issues", "mobile-<feature>-prod-issues", "mobile-<feature>-existing-issues" and "<project>-July31" ... why July31? Because some fucking moron decided to do a round of testing, and tag all the issues with the current date (despite the fact Jira does that anyway), which somehow still gets used from time to time because nobody pays attention to what they are doing. This means creating and modifying filters on a daily basis ... after spending time trying to figure out what its not in the first one.
- One of my favourite morning rituals I like to call "Jira dumpster diving". This involves me removing all the filters and reading all the tickets. Why would I do such a thing? oh remember the 9000 labels I mentioned earlier? right well its very likely that they actually won't use any of them ... or the wrong ones ... or assign to the wrong person, so I have to go find them and fix them. If I don't, i'll get yelled at, because clearly it's my fault.
- Moving on from Jira. As some of you might have seen in your companies, if you use things like TestFlight, HockeyApp, AppCenter, BuddyBuild etc. that when you release a new app version for testing, each version comes with an automated change-log, listing ticket numbers addressed ...... yeah we don't do that. No we use this shitty service, which is effectively an FTP server and a webpage, that only allows you to host the new versions. Sending out those emails is all manual ... distribution groups?? ... whats that?
- Moving back to Jira. Can't even automate the changelog with a script, because I can't even make sense of the tickets, in order to translate that to a script.
- Moving on from Jira. Me and one of the remote testers play this great game I like to call "tag team ticketing". It's so much fun. Right heres how to play, you'll need a QA and a PM.
*QA creates a ticket, and puts nothing of any use inside it, and assigns to the PM.
*PM fires it back asking for clarification.
*QA adds in what he feels is clarification (hes wrong) and assigns it back to the PM.
*PM sends detailed instructions, with examples as to what is needed and assigns it back.
*QA adds 1 of the 3 things required and assigns it back.
*PM assigns it back saying the one thing added is from the wrong day, and reminds him about the other 2 items.
*QA adds some random piece of unrelated info to the ticket instead, forgetting about the 3 things and assigns it back.
and you just continue doing this for the whole dev / release cycle hahaha. Oh you guys have no idea how much fun it is, seriously give it a go, you'll thank me later ... or kill yourselves, each to their own.
- Moving back to Jira. I decided to take an action of creating a new project for my team (the mobile team) and set it up the way we want and just ignore everything going on around us. Use proper automation, and a kanban board. Maybe only give product a slack bot interface that won't allow them to create a ticket without what we need etc. Spent 25 minutes looking for the "create new project" button before finding the link which says I need to open a ticket with support and wait ... 5 ... fucking ... long ... painful ... unnecessary ... business days.
... Heres hoping my head continues to not have a bullet hole in it by then.
Id love to talk more, but those filters ain't gonna fix themselves. So we'll have to leave it here for today. Tune in again for another episode soon.
And remember to always practiseSafeHex14
My PM: I don't like when you get up and help out other colleagues with their problems on their computer. You're not at their service.
Me: okay, I'll refrain from doing so.
The next day, I arrive 5 minutes before 8, I get myself a coffee, talk with a few colleagues, and:
PM: Hey, can you please come and help me review this email?
Me: ** fuck it, I still have 2 minutes ** Yeah I'm coming
PM: Now please.
Also my PM, 5 minutes later: Hey I don't manage to print my document, can you help me?
10 minutes later, I get a call:
PM: did you call XY about ZX?
Me: Yep, sent you a mail about it 2 minutes ago
PM: Really? I don't see it
Me: I sent it.
PM: Can you send it again?
Later that day:
PM: Hey, what are you up to?
Me: Well, I'm working on our improved websi-
PM: Can you please create a new campaign on Mailchimp? We're all under water here and a bit of cooperation from you would be great
Me: ** huh? ** erm, ok?
PM: Do it now
Me: Yeah yeah, don't worry. ** click ** here, done. Now, where was I...
----- PM on holidays
Other colleague from another department: Hey Phlisg! I have a small problem on our platform, can you help me?
Me: ** writes a script to help her out **
Her: awesome, thank you!!
Her own PM, 5 minutes later: Hey! Thank you very much for your help, it helps us out a real lot, very much appreciated :)
I lost my smile at work since the beginning of the year, but that little help I gave my colleague just gave my smile back to me :D14
Agile in practice.
I finished my story with 3 days left in our 2 week sprint.
Me: What story should I pull in next?
PM: Story <number> to add <new feature>
Me: ok, sounds good
PM: Will you finish it before our sprint ends?
Me: No, probably will take me 5-7 days.
PM: But it can't spill over, it will make our metrics look bad.
Me: I can't finish it in 3 days.
Me: Can't you just explain the spillover as us working ahead?
PM: It will look bad on our <automated-report>
Me: So don't want me to get started on <new feature>?
Me: <internally sighing> What do you want me to do?
PM: Maybe you can pair program with <Overpaid-Idiot-Programmer> to help finish their story
this happens way too often in our company
PM: did you made that change I requested?
me: yeah, its on the live server now, why?
PM: I cant see it...
me: *wtf, I specially forced the JS to reload to eliminate problems with cache* could you send me a screenshot?
PM: *sends screenshot*
me: I dont get it... I can see the changes in my browser *dev feeling intensifies* ... refresh the site and try again
PM: oh... suddenly its there, ...anyway, thanks! it looks great!
turns out our managers just dont refresh websites, they want changes to take place immediately3
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
At a certain client, was asked to help them with an "intermediary" solution to stopgap a license renewal on their HR recruiting system.
This is something I was very familiar with, so no big. Did some requirements gathering, told them we could knock it out in 6 weeks.
We start the project, no problems, everything is fine until about 2.5 weeks in. At this point, someone demands that we engage with the testing team early. It grates a little as this client had the typical Indian outsourcing mega-corp pointey-clickey shit show "testing" (automation? Did you mean '10 additional testers?') you get at companies who put business people in charge of technology, but I couldn't really argue with it.
So we're progressing along and the project manager decides now is a great time to bugger the fuck off to India for 3 months, so she's totally gone. This is the point it goes off the rails. Without a PM to control the scope, the "lead tester," we'll call her Shrilldesi, proceeds to sit in a room and start trying to control the design of the system. Rather than testing anything in the specification, she just looked at the existing full HRIS recruiting system they were using and starts submitting bugs for missing features. The fuckwit serfs they'd assigned from HR to oversee this process just allowed it to happen totally losing focus on the fact this was an interim solution to hold them over for 6 months and avoid a contract renewal.
I get real passive aggressive at this point and refuse to deliver anything outside the original scope. We negotiate and end up with about 150% scope bloat and a now untenable timeline that we delivered about 2 weeks late, but in the end that absolute whore made my life a living hell for the duration of the project. She then got the recognition at the project release for her "excellent work," no mention of the people who actually did the work.
Tl;Dr people suck and if you value your sanity, you'll avoid companies that say things like, "we're not in the technology business" as an excuse to have shitty, ignorant staff.6
Back in college.
We had this course in which we gathered in teams and worked the whole semester for another teacher building a product. We had roles, like QA, devs, PM...all the works.
I was PM and during our first presentation of the product to our teacher and the client we showed the work of our first month of work. At the end, our teacher asked our QA, who have been silent the whole project and hadn't answered my mails asking for tests, if he had found any problems. "Oh, yes. The whole site is broken. I can easily break throught it"
The faces of the rest of the group showed a level of surprise that made the teacher ask if he had informed us: "No..."
Our client, another SE teacher, started to laugh and that was that.
It was awful3
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
We were 6 devs on a big project that needed to be completed in 3 months. Probably my first project as a full-stack dev and the work was very demanding.
The senior of my team was a very sharp and energetic, but also a very "in your face" kinda guy. Like, he was cool, but sometimes a little too much to handle for some people.
Anyway, this guy "Senior dev" worked faster (naturally) and harder than the rest of us and was always willing to help if somebody had problems with a framework, tool or other technology. Also, there was this other guy also a good dev (second best I would say) that just hated the first guy's guts for being "rude and obnoxious" as he put it.
One day, the PM and the senior had an argument about a major change that the PM had agreed to (just to save face with the client) that will force the team to come to work on the weekend. In the end he saved us the trouble of going throught that and the PM had to tell the client that the change wouldn't be made. From then on it went downhill for "Sr. dev" in the company. Until one day he was told that his contract was not gonna be renewed.
Short after, he showed some of us a screen cap. somebody sent him of an email from the "hateful" dev to the PM in which he wrote he had heard that the senior guy was leaving and he couldn't be happier because he was "damaging, problematic and a stressful part of his job". That was such a dick move, we thought he should get back at the guy.
So he sent a fake email to the PM using the "hateful" guy's email ID, that read:
"Dear PM. I'm sorry I said those things about 'Senior dev', I guess I'm just mad that he's a better professional than me and mad that I was born with no genitalia".
After the senior dev left I worked on one more project with the "hateful" dev and he was let go mid project for "not being proactive and making little effort on completing the project".
Let me tell you the story of how a feature request no one asked for got put in an early grave:
PM walks into weekly meeting with a single use case that one user called in about, despite never having this issue during the past year and a half that our app has been in production. PM's boss (genuinely one of the best people i have ever worked with) happens to sit in this particular meeting for no reason other than he felt like he should once in a while.
PM brings up use case and wants to devote 3 weeks' development time and another 3 weeks to test RIGHT NOW while other projects are already in motion. PM's boss speaks up with this: "Listen if this guy is really this upset, we can just tell him to build his own service. All the other end users have no problems with this, so it's not worth spending the resources on, i don't think."
And that is how i went from "this is bullshit" to "i love you" in the span of 20 minutes.2
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
PM sends email to development team with the whole management team in cc.
"Guys, the data is not updating correctly! Make sure all the updates are being done! If we can't get this right then we can just forget about this whole thing!"
Me: Yes, because making generalized statements and inflammatory remarks actually help in correcting the problems...
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
My first project it’s an emotional roller coaster. I was a little trainee/ junior dev at my job with a little more than a month learning RoR and one day my tech lead receives an email from the big boss saying: “We got a big client who wants a total redesign of his web and we said yes we can do it in a month, so please check if anything it’s reusable”, after reading my tech lead said to me “Do you want to help me with this ?” And well, we spend like 2-3 hours checking all the controllers, views, assets, etc. We conclude that the project was mostly front end changes and the back end will stay the same, so yeah it can be done in a month. The next day in a meeting with all the team I was nominee to be the person in charge of that project, because it was an easy project and all my teammates hate to do front end stuff, so I take the challenge. After that I met the Project Manager, another guy who recently start as PM about a month, so yeah we were two new guys who need to handle the project of a big client, nothing can go wrong. We did the planing, I give an estimation ( first one in my life ) for the tasks and added like 4 hours in case anything goes wrong. Then the first sprint came by, and I couldn’t finish it because the time given to some features was to low and the “design” was a mockup made by the PM, ok, no problems, we add more time to the tasks and we ask for a real design. At the half of the sprint the client start adding more and more stuff, the PM doesn’t talk back, just say yes yes yes. Then in a blink of an eye the easy project became a three months projects with no design at all, two devs ( a new guy who recently begin as dev enter the project ), just mockups and good hopes. But somehow we did it, we finish it! Nope. The early Monday of the next week I received an email of the PM saying we would have a second version and the estimation of the tech lead was a minimum of six months ( that became 8 months). This time was hell, because the client doesn’t decide what the hell he wants so a task would take a couple of days more or so, the PM became the personal bitch of the client, but it wasn’t his fault, because we later knew that the company became partner with this client and because of that the PM didn’t have too much choice :/, the designs were cool, but they weren’t on time ever, our only design guy had to do designs to our project and another 5 projects of the company, so yeah, we weren’t the only ones suffering. At the end we survive, the project was done and the client somehow was happy. Of course the project didn’t end and it was terminated half a year later, but I’ll always remember it because thanks to this project I was given the opportunity to work as a Front end dev and I’m happy still working as one.
Company uses Trello to track bugs and features the devs are doing.
End of the week the PM: "So what bugs and features did you work on this week?"
If only there was a platform that we could track all these things... 🤦♂️1
Well this isn't the first time I tell how I got my burn out, but since is the week topic...
I work in a molding company as a cnc operator (should already be a programmer).
My section boss and the company boss (not the owner) are people that got their place trough time in the company and don't know how to deal with people.
So I'll try to resume 3 years of history:
I joined the company while finishing the cnc course (1 year left), I talk to much, I'm smart and like to explain stuff and correct people. The company boss only has 4th grade and tryed to make me flunk class.
First I had to do extra hours, till I flunked.
Then I threatened to call the authorities, so I started working from 6 am to 5 pm and class till 11...
4 hours sleep a nighty for months
After that I started having health problems, when I was taken to the hospital after I pass out I as diagnosed with the burn out, been trying to recover since, while the fukers only did worst stuff, treated me like a dog and such.
I never made the complaint because the owners are owsome people, the kind who gives a lot to help the ones in need and make campaigns to help the poor. Now there are 6 complains again the company (last I've heard). And why? Because there was no consequences after what they have done all that shit to me, they started to do the same to others... Others that have no reason like me to hold back and not fuck the company...
The owners were building a second company to expand...
Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding3
-Interviewer: "do you have any problems in working after 19.30?"
-Me: "what do you mean? if something's wrong and it's my fault, l'll do my best to ..."
-Interviewer: "well, we have people here that works usually after 19.30, so if you have any problems in doing this, better to know now."
(uhm... the job was from 9AM to ... WTF PM?!)11
Whenever you feel the need to rant about your project manager, always remember you'd wish you had one if you reported directly to the CEO.3
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
Our current project...
First three sprints... going fine and slow get used to each other.
Later sprints get more of a clear scope. With a deadline a couple of months later. The team raises some red flags with problems.
Seems like the PO/PM doesn't get it or ignores it.
More sprints later with more confrontations. PO/PM still doesn't get it.
Team introduces a new theme song
Hopes she gets it now . . .
Have you ever found a infinite task? Well, I did.
So, the software that I'm working now was under responsibility of another company for development and maintenance (I'll call them X) from 2014 to last month , and the company I work for was handling only with the business part. Now we took all the development for us as well.
This software has a lot of reports , so it has a lot of templates for this reports.
When X was handling the software, they asked the client and the old project manager if they wanted the templates to have the client's products dynamic (no need to change the template when adding a new product) or hardcoded for some products they already had, they choose hardcoded because it would be faster. Butterfly effect.
Fast forward to this week, the team leader designated a task for me, It looked easy at first, just fix 2 templates, easy.
Oh boy, I was so wrong.
I fixed the first template, discovering in the process the hardcoded things, had to add the product reference in a lot of places.
So i went to the second item, a super template that they use to put together some smaller templates.
It was really weird, I couldn't find all the templates that it was supposed to use, and I didn't really know the exact problem, the only thing I knew was that it was not being generated, the reason could be the super template itself or one of the 15 smaller templates, that could happen to have sub templates.
So I called the team leader and explained to him wtf was happening, he called the senior business analyst, that called the PM, we agreed that it would be infinite because of those fucking hardcoded things, they prepared a excel sheet with this and a lot of other problems and will send this to the client, explaining that we'll need a lot of time to put this new product up and running.
Now I'm in the middle of this shit storm seeing a time of darkness in the future.
Ps: This new product was supposed to be inserted in the software since last November, when it was under X responsability, and they analyzed it and said that it would take 190 hours to be completely done, the client refused. It was the first rain drop of what would become a shit storm.
So, while working on a story, I noticed something which the lead dev did that is now giving me problems.... and he's offline while in another building.
Ok, I'll just contact our PM to see how much is due today (visual happy path only or API call is needed too)...same state as lead dev.
Scrum master, the person who's in charge of contacting anyone... no flipping clue where she's at.
It's great being on such a small team!2
So the project I have been working on for the past 5 months was finally released yesterday with only very minor problems, this stemmed from both programming side, and users entering data incorrectly.
It has been a rather hectic 5 months. I've had to deal with crap like:
- clients not knowing their own products
- a project manager that didn't document anything (or at least everything into a Google Slides document)
- me writing both requirements AND specifications (I'm a dev, not a PM)
- developers not following said specifications (then having to rewrite all their work)
But the worst thing I think would be the lack of vision from everyone. Everyone sees it as a "project" that should be get it over and done with rather a product that has great potential.
So with the project winding down, and only very few things left to fix/implement. Over these 5 months I learned a lot about domain driven design, Laravel's core, AWS, and just how terrible people are at their jobs. I imagine if I worked with people who gave a damn, or who actually had skills, I probably wouldn't have had such a difficult project.
Right now I'm less stressed but now feel rather exhausted from it all. What kind of things do you to help with the exhaustion and/or slow down of pace?1
> mfw a non-dev customer shows me an exception that is easy to reproduce to answer my sarcastic questions whether she got any problems with the application
> mfw no dev or PM ever thought of using the application like this1
Oh its ok Mr. "Senior PM"...its totally ok to take a week of PTO during crunchtime...a week before launch...that wont cause any issues at all....1