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 - "backlog"
1. The quality of the coffee and toilet paper you encounter during an interview tells you more than promises about table tennis or fruit baskets.
2. Try to determine who their primary client is: subscribers, app buyers, advertisers, etc. It's a major influence on the company dynamic.
3. Before an interview, you can just say: "I would like to sit down with a PO and run through one backlog feature and one bug, to get a feel for the type of tasks at the company". Such an activity immediately reveals team structure, whether they have product owners & scrum masters, what a sprint looks like, how they prioritize tasks, and how organized/chaotic your work experience will be.18
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23
Things have been a little too quiet on my side here, so its time for an exciting new series:
practiseSafeHex's new life as a manager.
Episode 1: Dealing with the new backend team
It's great to be back folks. Since our last series where we delved into the mind numbing idiocy of former colleagues, a lot has changed. I've moved to a new company and taken a step up as a Dev manager / Tech lead. Now I know what you are all thinking, sounds more dull and boring right? Well it wouldn't be a practiseSafeHex series if we weren't ...
DEALING! ... WITH! ... IDIOTS!
Bingo! so lets jump right in and kick us off with a good one.
So for the past few months i've been on an on-boarding / fact finding / figuring out this shit-storm, mission to understand more about what it is i'm suppose to do and how to do it. Last week, as part of this, I had the esteemed pleasure of meeting face to face with the remote backend team i've been working with. Lets rattle off a few facts to catch us all up:
- 8 hour time difference to me
- No documentation other than a non-maintained swagger doc
- Swagger is reporting errors and several of the input models are just `Type: String`
- The one model that seems accurate, has every property listed as optional, including what must be the primary key
- Properties go missing and get removed at the drop of a hat and we are never told.
- First email I sent them took 27 days to reply, my response to that hasn't been answered so far 31 days later (new record! way to go team, I knew we could do it!!!)
- I deal directly with 2 of them, the manager and the tech lead. Based on how things have gone so far, i've nick named them:
So lets look at some example of their work:
- I was trying to test the new backend, I saw no data in QA. They said it wouldn't show up until mid day their time, which is middle of the night for us. I said we need data in our timezone and I was told: a) "You don't understand how big this system is" (which is their new catch phrase) b) "Your timezone is not my concern"
- The whole org started testing 2 days later. The next day a member from each team was on a call and I was asked to give an update of how the testing was going on the mobile side. I said I was completely blocked because I can't get test data. Backend were asked to respond. They acknowledged they were aware, but that mobile don't understand how big the system is, and that the mobile team need to come up with ideas for the backend team, as to how mobile can test it. I said we can't do anything without test data, they said ... can you guess what? ... correct "you don't understand how big the system is"
- We eventually got something going and I noticed that only 1 of the 5 API changes due on their side was done. Opened tickets. 2 days later asked them for progress and was told that "new findings" always go to the bottom of the backlog, and they are busy with other things. I said these were suppose to be done days ago. They said you can't give us 2 days notice and expect everything done. I said the original ticket was opened a month a go *sends link* ......... *long silence* ...... "ok, but you don't understand how big the system is, this is a lot of work"
- We were on a call. Product was asking the backend manager (aka "Ass") a question about a slight upgrade to the new feature. While trying to talk, the tech lead (aka "Hole") kept cutting everyone off by saying loudly "but thats not in scope". The question was "is this possible in the future" and "how long would it take", coming from management and product development. Hole just kept saying "its not in scope", until he was told to be quiet by several people.
- An API was sending down JSON with a string containing a message for the user with 2 bits of data inside it. We asked for one of those pieces to also come down as a property as the string can change and we needed it client side. We got that. A few days later we found an edge case and asked for the second piece of data to be a property too. Now keep in mind, they clearly already have access to them in order to make the string. We were told "If you keep requesting changes like this, you are going to delay the release of the backend by up to 2 weeks"
Yes folks, there you have it, the most minuscule JSON modifications, can delay your release by up to 2 weeks ........ maybe I should just tell product, that they don't understand how big the app is, and claim we can't build it on our side? Seems to work for them
Thats all the time we have for today,
Tune in for more, where we'll be looking into such topics as:
- If god himself was an iOS developer ... not
- Why automate when you can spend all day doing it by hand
- Its more time-efficient to just give everything a story point of 5
- Why waste time replying to emails ... when you can do nothing instead
See you all next week,
Looks like I'm getting fired on Wednesday :)
*I add first unit tests to project.
*Boss adds new functionality and breaks all the tests so I can't compile and write more for what I'm working on.
*Boss is very fragile and cannot handle any comment that can possibly be taken as a slight against him.
Me: "I wanted to ask what our policy on unit tests is please? Because we haven't really said how we are treating unit tests, and everyone myself included is not thinking about them. I also haven't added tests when I fixed bugs and this time your changes broke the tests"
Boss 10 minutes later: "I want to speak to you in private".
Boss: "you are too forceful and direct. You said I should have added tests."
Me: "yeah but I didn't mean in a nasty way"
Boss getting louder and more aggressive: "You are too forceful"
Me: "I didn't mean it in a bad way"
Boss: "I didn't want to add tests for that!"
Me: "then why add any tests?"
Boss: "Fine we are not having this conversation now!"
*Boss storms out
I decided I can't speak to the guy about anything without upsetting him spoke to the manager before I quit because I can't work like this.
That resulted in a meeting with my boss, his boss and the head of HR where I ended up savaging him and told them I can't bring up anything as I can never tell if it will offend him and that I spend ages writing emails and trying to document communications because I just can never tell if I will upset him. Also that I cannot bring up any ideas because I can't tell if he will somehow get offended and that I can't even write code because if I change something he wrote at some point he will get angry.
My boss claims that I am extremely forceful and disrespectful and that I am constantly insulting him and his decisions.
We go back over a ton of shit and I refute everything he says. In the end I have to have a meeting with him on Wednesday where we either get things straight, he fires me or I quit.
I think at this point that our relationship is too fucked for him to be my team lead on a 6 man team.
Side note I keep bringing forth ideas because we have one database shared between 6 Devs, no pull requests (apart from mine and another new guy), no test driven development, no backlog, no team driven story pointing, no running tests before merging, no continuous integration setup, no integration tests, no build step on merge, no idea of if we are on track to our deadline other than his gut feeling, no actual unit tests backend - just integration with a test db, no enthusiasm to learn in the team and no hope.23
The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.
*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"
Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.5
--- GitHub 24-hour outage post mortem ---
As many of you will remember; Github fell over earlier this month and cracked its head on the counter top on the way down. For more or less a full 24 hours the repo-wrangling behemoth had inconsistent data being presented to users, slow response times and failing requests during common user actions such as reporting issues and questioning your career choice in code reviews.
It's been revealed in a post-mortem of the incident (link at the end of the article) that DB replication was the root cause of the chaos after a failing 100G network link was being replaced during routine maintenance. I don't pretend to be a rockstar-ninja-wizard DBA but after speaking with colleagues who went a shade whiter when the term "replication" was used - It's hard to predict where a design decision will bite back and leave you untanging the web of lies and misinformation reported by the databases for weeks if not months after everything's gone a tad sideways.
When the link was yanked out of the east coast DC undergoing maintenance - Github's "Orchestrator" software did exactly what it was meant to do; It hit the "ohshi" button and failed over to another DC that wasn't reporting any issues. The hitch in the master plan was that when connectivity came back up at the east coast DC, Orchestrator was unable to (un)fail-over back to the east coast DC due to each cluster containing data the other didn't have.
At this point it's reasonable to assume that pants were turning funny colours - Monitoring systems across the board started squealing, firing off messages to engineers demanding they rouse from the land of nod and snap back to reality, that was a bit more "on-fire" than usual. A quick call to Orchestrator's API returned a result set that only contained database servers from the west coast - none of the east coast servers had responded.
Come 11pm UTC (about 10 minutes after the initial pant re-colouring) engineers realised they were well and truly backed into a corner, the site was flipped into "Yellow" status and internal mechanisms for deployments were locked out. 5 minutes later an Incident Co-ordinator was dragged from their lair by the status change and almost immediately flipped the site into "Red" status, a move i can only hope was accompanied by all the lights going red and klaxons sounding.
Even more engineers were roused from their slumber to help with the recovery effort, By this point hair was turning grey in real time - The fail-over DB cluster had been processing user data for nearly 40 minutes, every second that passed made the inevitable untangling process exponentially more difficult. Not long after this Github made the call to pause webhooks and Github Pages builds in an attempt to prevent further data loss, causing disruption to those of us using Github as a way of kicking off our deployment processes (myself included, I had to SSH in and run a git pull myself like some kind of savage).
Glossing over several more "And then things were still broken" sections of the post mortem; Clever engineers with their heads screwed on the right way successfully executed what i can only imagine was a large, complex and risky plan to untangle the mess and restore functionality. Github was picked up off the kitchen floor and promptly placed in a comfy chair with a sweet tea to recover. The enormous backlog of webhooks and Pages builds was caught up with and everything was more or less back to normal.
It goes to show that even the best laid plan rarely survives first contact with the enemy, In this case a failing 100G network link somewhere inside an east coast data center.
Link to the post mortem: https://blog.github.com/2018-10-30-...7
Worst of 2020:
Seeing company get stuck in an organizational swamp. Devs tend to be reasonably good at working from home...
Management isn't. Meeting quality has gone down the drain, half of management thinks "if the boss can't see me why work at all?", the other half has constant calls with tiny working groups where nothing is final and everyone is left confused.
I'm convinced: Everything management is afraid of about allowing devs to work from home is based on projection of their own weaknesses.
They're not passionate enough to work without oversight. They might not be introverts, but extroverts are perfectly able to communicate poorly, especially when a few digital hurdles get in the way.
The average developer might actually be more attuned to the intricacies of emotionless text chats, and preventing disruptive elements in video calls.
Also, unless someone physically helps a manager to remove their head from their own ass once in a while, their "gut feelings" about the market and products are actually just amplified bias caused by their endless self-absorbed yelling into the echo chamber that is their stretched out rectum.
Holy motherfucking hell, have I seen some weird projects float by in 2020, pooped out by isolated product managers whose brain clearly has melted when they had to survive without office fruitbaskets and organizational post-it walls.
Yeah let's promote our international character, by giving away travels and hotel bookings, using pictures of happy hugging people in foreign countries... Great promo during a pandemic.
Or let's get "woke" and promote the "colored users" on our platforms, by training ML to categorize people by skin pigment (Apart from how illegal and ethically insane that is on multiple levels, about 85% of our users pick shit like anime characters and memes for their avatar).
Or how about we make a Microsoft Store app, even though the vast majority of our end users are students using cheap Android phones, older iPhones, Macbooks and Chromebooks.
Anyway, now that I have dressed up my Christmas tree with some manager intestines...
Best of 2020:
I got to play through my Steam backlog, work on hobby projects, and watch a lot of YouTube.
All this pandemic insanity has convinced me all the more that I want to work way more in Rust, and publish way more on open source projects.
I became maintainer/collaborator on a bunch of semi-prominent libraries & frameworks, and while no community is perfect, I enjoy my laid-back coffee-fueled debugging on those packages much more than listening to another crack addicted cocksucker in a suit explain their half-assed A/B test idea to me at 9AM.
So, 2021 will be me half-assing through the spaghetti at my official fuckfest of a job so I can keep filling my bank account — and investing way more time and effort into stuff I find truly engaging, into projects with a heart and a soul.3
When somebody submits an issue to your backlog that not even Software Development Jesus himself could fix8
Back in Hell, we had a “company summit” where everyone flew in for an all hands meeting.
It was three days long in a tiny office with very lacking air conditioning in the middle of a Las Vegas summer. Basically the entire thing was the CEO / goblin salesman king chewing at us and expounding about / proselytizing his latest and greatest sales ideas and how they’ll change the world. And randomly asking “which of you are HUNGRY?! Which of you want to be FILTHY FUCKING RICH?!” etc.
One good thing came out of it, which was that any and all new endeavors needed a “co-signer” and a sign off from development before we (developers, or more accurate: just me) would work on it. It reduced the growth rate of my backlog by like 80%, which was nice.
While dreading the “summit,” I hated him more than I had in quite awhile.
During the summit, I hated him more and even flipped him off.
After the summit, I swore to leave the revolting wreckage that was the company.
(And months later, I did just that —after becoming the sole dev and the only person holding the damned company afloat. When I gave him my two weeks’ notice, I absolutely relished his terror. And my time spent writing my 43 page no-sugarcoat handoff document that was guaranteed to scare off any hapless dev he might find. 😇)
But I digress, three 10-hour days with him and the rest of the sales team, the sleazy lawyer, the CTO who mentally checked out years ago, the yes-man contractor, and me. The only good thing that came out of that meeting was one good idea that he dismissed, and the sign off idea that saved my backlog a bit.
One of the sales people quit shortly thereafter. So it was a huge expense that wasted everyone’s time and added absolutely nothing of value to the company. GG!
Oh, it was also in the “totally better” office — meaning… cheaper, unfinished (literally plywood floors), and was one room in another company’s office, who often locked the door leading to their offices because they trusted him so much. But it was in downtown Las Vegas, with no parking at all, where gang members were hanging out almost every day, and it was next to low-income housing and weird no-service restaurants with shockingly high prices.
Weird and scary.
Totally carried pepper spray every time Mr. Goblin asshole forced me to go into the office. Didn’t get raped, though, or my laptop or car stolen. So that was nice.5
So I'm a entry level female Developer and I started a contract to hire position in July. Its my first job as a developer and I love almost everything about it. Except this..., there is a Senior Female Developer on my team who hates me and isn't shy about it. She goes for the throat man! She magnifies any mistake I make, hell she calls me out on things that people would consider positive. In sprint planning this week she got mad at me for pulling tasks from the backlog after finishing mine early. I've tried to do everything I could to make her like me. I patiently listen when she goes on and on about her damn cats, kids, sports, ah everything, and she is a non stop talker.
Her main problem with me, so she tells the head of engineering, is that I bug her too much. I almost laughed when I heard this was her main issue with me! Sure, I asked her the normal amount of newbie questions but it's not like I don't know how to read code or google! In fact I started avoiding talking to her about a month ago because she was so rude to me. Now getting hired on full time comes down to whether or not she can stand me still if I am working on another team. I'm so frustrated because it's impossible to prove my worth to this company with this crazy lady making me look bad. I have no problems with anyone else at work. In fact a lot of us have become good friends. No one understands why she hates me so much. It feels like middle school all over again.
On top of that there is an even newer hire who she is supposed to help bring on to the team, but because of her horrible management skills, I have become his defecto mentor for learning the project, as well as the technologies we use. The stress of being in an uncertain contract to hire position + tyrant coworker + helping the new guy + still learning and having my own work to do has been overwhelming! I don't know what to do other than hope that she doesn't try to sabotage me moving to a new team.29
Start-up: hires 3 junior devs to save money.
Start-up: expects things to get done faster-- BUT-- Start-up keeps adding things to the TO-DO list and backlog-- i.e. it's all relative!!
Start-up: gets angry at 3 junior devs why they can't deliver when they keep adding tasks and ask we fall behind.
Dev team: "Seriously? You hire more devs to finish tasks faster, but you keep adding more than are being finiahed-- obviously it's gonna take longer now regardless"
Git --pull life together2
Management had the idea to have a hackathon on saturday. Everybody should gather ideas what to do on this day, but top priority is to have fun.
In the end, management decided that we should work on tasks from our backlog.
Yeah... unpaid work on saturday... sounds like fun10
(Written March 13th at 2am.)
This morning (yesterday), my computer decided not to boot again: it halts on "cannot find firmware rtl-whatever" every time. (it has booted just fine several times since removing the firmware.) I've had quite the ordeal today trying to fix it, and every freaking step along the way has thrown errors and/or required workarounds and a lot of research.
Let's make a list of everything that went wrong!
1) Live CD: 2yo had been playing with it, and lost it. Not easy to find, and super smudgy.
2) Unencrypt volume: Dolphin reports errors when decrypting the volume. Research reveals the Live CD doesn't incude the cryptsetup packages. First attempts at installing them mysteriously fail.
3) Break for Lunch: automatic powersaving features turned off the displays, and also killed my session.
4) Live CD redux: 25min phonecall from work! yay, more things added to my six-month backlog.
5) Mount encrypted volume: Dolphin doesn't know how, and neither do I. Research ensues. Missing LVM2 package; lvmetad connection failure ad nauseam; had to look up commands to unlock, clone, open, and mount encrypted Luks volume, and how to perform these actions on Debian instead of Ubuntu/Kali. This group of steps took four hours.
6) Chroot into mounted volume group: No DNS! Research reveals how to share the host's resolv with the chroot.
7) `# apt install firmware-realtek`: /boot/initrd.img does not exist. Cannot update.
8) Find and mount /boot, then reinstall firmware: Apt cannot write to its log (minor), listed three install warnings, and initially refused to write to /boot/initrd.img-[...]
9) Reboot!: Volume group not found. Cannot process volume group. Dropping to a shell! oh no..
(Not listed: much research, many repeated attempts with various changes.)
At this point it's been 9 hours. I'm exhausted and frustrated and running out of ideas, so I ask @perfectasshole for help.
He walks me through some debugging steps (most of which i've already done), and we both get frustrated because everything looks correct but isn't working.
10) Thirteenth coming of the Live CD: `update-initramfs -u` within chroot throws warnings about /etc/crypttab and fsck, but everything looks fine with both. Still won't boot. Editing grub config manually to use the new volume group name likewise produces no boots. Nothing is making sense.
11) Rename volume group: doubles -'s for whatever reason; Rebooting gives the same dreaded "dropping to a shell" result.
A huge thank-you to @perfectasshole for spending three hours fighting with this issue with me! I finally fixed it about half an hour after he went to bed.
After renaming the volume group to what it was originally, one of the three recovery modes managed to actually boot and load the volume. From there I was able to run `update-initramfs -u` from the system proper (which completed without issue) and was able to boot normally thereafter.
I've run updates and rebooted twice now.
After twelve+ hours... yay, I have my Debian back!
So I found out I'm only earning 50 cents higher than the minimum wage. Nice, very nice...
... And that's why the backlog of unfinished tasks keep piling up. You get what you pay for.12
I think I figured out why so many companies jumped on board the Agile approach. Companies heard Productivity Bonus and Put Stuff into a List Of Things to Do, and left out all the rest of their responsibilities. One of my past companies was like "We're going to take an Agile approach to everything! Except, we're not going to shield developers from everyone who has stuff in the backlog, and we're going to have other meetings during the day on top of the scrum meetings to check on your progress, and we're going to measure points in time instead of complexity".
I feel like the creators of the Agile Manifesto would be really upset at all of the poorly implemented processes. Because all of us developers are pretty upset.6
After completing my sprint and some lingering stuff in the backlog
Me: Hey, there's this tiny feature people have really requested, I'll go build it since I got nothing else to do at the moment. It'll only take like 1h
PO: Hmm ok. Don't work on that yet, we need to check with business people and agree on the user stories and bla bla bla
Me: Ok, well there's these bugs I can take care of then, I'll get them fixed, won't be long.
PO: Hmmm, we need to measure the impact first. Let me get back to you on that a bit later
Me: Meh, oh. I'll refactor this bad component meanwhile then.
PO: Have you created a story for that in JIRA? Create the story first and then we'll groom it and take it in when we've time
Me in my head: Dafuq! Im trying to work on your fucking project but you keep throwing all that business bueraucracy shit at me. What am I supposed to do then? Sip coffee in the kitchen and talk about the other fucking billion failed "new business opportunities" with my peers? Fuck this circle jerk of a billion management people all trying to make themselves important. Nothing. Ever. Gets. Fucking. Done!!!
Me: Ah right, I'll do that *proceeds to the water cooler*5
The best thing that can happen to a dev?
A 2-hour meeting got cancelled. Yeah!
No backlog tomorrow!6
this is how I destroyed my career in IT and how I'm headed to a bleak future.
I've spent the last 10 years working at a small company developing a web platform. I was the first developer, I covered many roles.
I worked like crazy, often overtime. I hired junior dev, people left and came. We were a small team.
I was able to keep the boat afloat for many years, solving all the technical problems we had. I was adding value to the company, sure, but not to mine professional career.
There was a lot of pressure from young developers, from CEO, from investors. Latent disagreement between the COO and the CEO. I was in between.
Somehow, the trust I built in 10 years, helping people and working hard, was lost.
There was a merge, development was outsourced, the small team I hired was kept for maintenance and I was fired, without obvious explanations.Well, I was the oldest and the most expensive.
Now I'm 53, almost one year unemployed.
I'm a developer at heart, but obsolete. The thing we were doing,
were very naif. I tried to introduce many modern and more sophisticated software concepts. But basically it was still pure java with some jquery. No framework. No persistency layer, no api, no frontend framework. It just worked.
I moved everything to AWS in attempt to use more modern stack, and improving our deployment workflow.
Yes, but I'm no devop. While I know about CD/CI, I didn't set up one.
I know a lot of architectural concepts, but I'm not a solution architect.
I tried to explain to the team agile. But I'm not a scrum master.
I introduced backlog management, story mapping, etc. But I'm not a product manager.
And before that? I led a team once, for one year, part of a bigger project. I can create roadmap, presentations, planning, reports.
But I'm not a project manager.
I worked a lot freelancing.
Now I'll be useless at freelancing. Yes I understand Angular, react, Spring etc, I'm studying a lot. But 0 years of experience.
As a developer, I'm basically a junior developer.
I can't easily "downgrade" my career. I wish. I'll take a smaller salary. I'll be happy as junior dev, I've a lot to learn.
But they'll think I'm overqualified, that I'll leave, so they won't hire me even for senior dev. Or that I won't fit in a 25 y.o. team.
My leadership is more by "example", servant leader or something like that. I build trust when I work with somebody, not during a job interview.
On top of that, due to having worked in many foreign countries, and freelancing, my "pension plan" I won't be able to collect anything. I've just some money saved for one year or so.
I'm 53, unemployed. In few years time, if I don't find anything, it will be even harder to be employed.
I think I'm fucked25
Yeah boss, lets study Scrum extensively so you can:
- Create variable length sprints
- User stories that are meaningless like 'fixes'
- Tasks that should be User Stories
- Duplicated tasks/stories that are on the fucking backlog already
- Cross sprints on projects
- No meetings at fucking all to determine who will do what
- Assign people on vacation to current sprints
The list goes on...
An when I point things like that out lets just look at the guy who spent 6 months studying this shit, taught you ( at least tried... ) as if he is saying nonsense while our projects get delayed and our code spaghettifies because we are always in a hurry for lack of time to plan anything :)2
I had a job that was one big meeting for 6 months. I kid you not. We had our stand up, had another meeting that extended the stand up to discuss issues highlighted in the stand up, then we would have a scrum catch up type meeting then after that work until about 12 so an hour ish? Then a call after lunch to catch up about the work we’d done and make sure everyone was ok, then probably a backlog meeting, then likely a company wide meeting and then at about 4? Probably a meeting. I don’t know by this point I’d lost the will to live. One massive joke of a company I swear5
Greetings @dfox @trogus, et al,
Here is some feedback with aspirations for the backlog.
I think it would be a good addition in the devRant UI if we could paste in code snippets and have that code display with proper fonts and syntax formatting, and even ideally with highlighting by language.
Currently, if we paste in any code or text for that matter it is translated into a sans-serif font (14px Helvetica Regular on webapp) which is fine for the poetic prose from our fine and noble devRant colleagues, but not ideal for shared monospace snippets of lesser and grand design.
Here are two websites that provide conversion of code snippets into formatted syntax, and HTML. http://hilite.me/ and http://markup.su/highlighter/
Both of these sites provide an API so highlighters can be used as a service.
Thank you @jaaku for your post, and welcome.
devRant for the win
Client: we are using Scrum. Next week we have sprint review organized by the project manager.
Me: it’s not Scrum.
Client: in the next sprint we work on a mockup not releasable in production.
Me: it’s not Scrum.
Client: sprint backlog is changed again, at the end we must do everything that is written in the contract with that fixed amount of money.
Me: definitely not Scrum.
Client: we are using Scrum.
I walk into the kickoff meeting today. The first part of this project had 5 developers and a project manager. Former project manager handled communication and sheltered us from bullshit. We built an amazing piece of software in a very short time. Customers were so amazed that they decided to reboot the project, boost the funding by several million, and let us go again. They specifically requested the same team.
Now the team looks like this: the neediest tester guy, a UX lady that doesn't have any UX background, an agile "visionary", a project manager that doesn't understand how development works, a solutions architect, 3 COTS platform specialists, a devops specialist, and an account lead. They have booked all kinds of workshops and other shit to kick things off.
So development capacity is only 60% of what it was. Management ratio was 1:5 before. Now the management ratio is 9:3. The new project manager thinks developers should be on more customer calls and responding to all customer emails during sprints. We already built this system and devops pipelines end to end. The COTS people, solutions architect, or the UX person can't program. They want us to magically convert this custom application into one based on COTS. What we need to do is make the rest of the business processes that we omitted, integrate known feedback, rework the backend, build better automated testing, improve logging and reporting, add another actor to the system, add a different authentication method, and basically work through the massive backlog.
How do they think this is going to work? Do they think we can download a custom engineered enterprise grade software system from Microsoft and double click all the way to customer satisfaction? The licenses alone are too much for the customer on an ongoing cost basis. I guess we can discuss it during the agile team-building weekend at some remote lake that the team "visionary" has set up. For the sake of fuck.
Like development isn't hard enough. Hire two more developers and lose all of the dead weight. Get a project manager that won't let the trivial shit roll down on us. What the fuck.5
Spent a couple hours writing a new feature yesterday, and finished it only to discover that somebody lazily wrote the global method that my feature was utilizing. Emailed them and told them that I completed the feature and asked them to fix the bad method. Figured that I wouldn't commit my code changes until he fixed his method. He proceeds to fix the method, and then completely redoes the feature I ALREADY TOLD HIM THAT I FINISHED. He removed me from the backlog story that I was assigned to and did the feature the exact same way I did. Motherfucker I already told you that it was done, you just needed to fix your lazy shitty global method. You did twice the work and wasted my time. If you wanted credit for your work, that's fine -- you could've created a new story to fix your method. Now I've wasted hours of my time writing a feature and then reverting the changes because you couldn't follow directions
Worked on a team where every single sprint planning was a useless meeting because we were expected to deliver everything in the backlog every sprint. So what are we really planning?5
Agile Coach: you need to take part in the next quarter planning of the work. Work with your business team to create a healthy backlog. Provide your input to the user stories. It’s a collective effort.
Me: why tf it’s not a collective effort when code breaks and only one dev is trying to fix it while taking in all the heat.
Of course I can’t say that out loud without getting fired.4
Headphones on, noise cancellation enabled, Google play music enabled.
Connect to my remote desktop and open Jira
See ridiculous backlog and get to work
(Panda for views)
Chat apps. What's the idea? Those are basically tools of violence. They give you a possibility to in real-time stop someones work and start demanding service. Now. Immediately.
Usually people send you first email and then they after 10 seconds chat "did you see my email?? read it! serve it! please me!" Usually it's just a small request to document something, review someone else's document. Do it ASAP. If you were coding something, then drop it and do someones job for them instead.
You got a request for me to create some verification case list? Put it into my backlog. I might start doing that in week or two. Or month. In case there's nothing else more important. Since I know that you are working with something that you think is the whole universe, but trust me, I got my own problems already.
But hey, if I don't reply to your chat in a minute, please feel free to walk behind me and start explaining your life. No need to wait even for me to get my headphones off. "Oh you are in conf call? Well, this is just a quick thing blaa blaa..."3
I can't believe this happened. I thought i would never witness this. A coworker dropped the entire production database. And no backups because its the first day, were way past beyond the deadline and no one thought we would need it this soon. Now we manually have to enter the entire backlog. He was supposed to delete just one tables rows. Im amazed by how dumb he is. How much trust we put in that we wouldnt fuck up the database this soon if at all in this way. Im beyond words. I am so glad im leaving this place at the end of the month. Hes so lucky i will never see him again after that.5
Long time no rant from me. Sorry guys, has been a tough time for me.
Little background: I'm an apprentice and as such definitely not a fully trained professional. I'm working in a big company with people who have very let's say interesting ideas what I should be able to do.
This whole disaster begins shortly after I started my apprenticeship. I was offered to choose my first little project. "Something from the backlog, not very challenging and a nice beginner one. It's just about a PoC" ok, le me thinks. I choose to make a weather display.
Basic functionality was provided within the next 3 weeks. My direct boss (let's call him Jo) liked it and talked to his boss (Hugo) about it. Hugo was so excited he called our product manager to get my plugin into our software asap and began to think about where else we could use this.
This is where shit went downhill. Hugo told me it was my task to implement it on a totally different platform and to "host it in azure". I don't know much about azure and I never used it. I told him that I'd need time and some kind of sandbox to try and learn how things work. He promised but nothing ever came through. Not even Jo could do something about this.
They told me I should write this asap because "every customer would LOOOOVE this" and I honestly can't think of a way to meet all their requirements without access to our azure system/ sandbox. (There are a lot of requirements)
Am I wrong? Should I be able to do this? I'm a fucking trainee. I don't know everything.9
Just coded for 12 hours.
One feature is blocked,
2 are ready for testing
And a third needs some development but actually has no task in the backlog,so that one is in limbo.
Tomorrow it will all be done.
So this is my first rant but I have to rant about this because I can’t take it anymore.
So I have a manager that has build the department we are in from an application he built that takes care of department metrics. I work for an ISP for a technical support department that takes care of the metrics and tools that they use to troubleshoot(not to mention that I work mostly with shitty legacy code). When I first got into the team There was no version control, no way to actually measure our work and no actual structure on anything. So when I came in I implemented TFS and GIT, so now we have at least that. The problem is that when my manager decided it would be a good idea to implement agile/ Kanban development in my team, he also decided that a methodology that was proven to work was not enough. So he started adding a bunch of useless and annoying rules on top of that methodology. Some of those rules were for example we don’t use tasks, we use backlog items as tasks and each backlog item has to take minimum of 15 minutes and maximum of 2 days to get completed, if it takes you longer you have to split it into chunks like part A and part B etc. Same thing for features which don’t represent features but represent projects which can’t be greater than 2 weeks and then Epics which can’t be greater than 2 months. But also you can only put in TFS stuff that is related to projects and nothing else. So not all the work you do is accounted in there but yet it will be used for your overall performance at the end of the year. It’s fucking wack and I can’t wait to move out of there, the environment is pretty toxic. It feels like everyone in our team except the one ass licker is just dead inside and no one gives a shit anymore. And that is what happens when you try to make a proven working thing into something “better” when you know nothing about it.2
Two tasks at the top of the backlog that was approved by the scrum master, and pm. We finish them in a few hours. Pm comes out.
Pm: Why are you guys working on those tickets!?!?!
Us: because they are the first things in the list.
Pm: but the client hasn't agreed on the work yet.
Us: then why is it the top of our list!!!
Pm: cause it's important.
We were going through Sprint Planning on Monday. We got through all of the tasks that we knew we had to get done, then we started going through the backlog to see what we could pull forward.
The guy running the meeting (who's not actually a Scrum master, but whatever) get's to a task, reads it aloud, and goes, "That doesn't ring any bells. Brian, it's in your name, it says it's from May, do you know what the status of this is?
Brian reads through it for about 20 seconds before saying, "That date says it's from 2017. I don't think we need it anymore."2
Bless whoever came up with Scrum! Now when the PO requests a change from me, I get to tell him: "please refer to the scrum master and discuss potentially adding your suggestions into the backlog items for the next sprint."1
So you have an organization that flirts with scrum and wants to be agile. You have non-crossfunctional teams who don't know what agile is. You have product owner who doesn't want to do backlog, but instead acts like project manager and asks for statuses and assigns tasks to peple. He wants the teams to find out what needs to be done and fill the backlog themselves - and then raport to him. You have business owers who noone knows who they are. You have project managers, who don't fit the whole scrum hierarchy. These project managers insist calling scrum masters "team leaders". Also these project managers think scrum is silly and don't want anything to do with it. And then you have higher program management that think this whole scum thing is better than sliced bread and everything is going just dandy!
Oh yeah, also highest organization management thinks that we are on the right track. We just need be more agile but less agile and work more efficiently whitout really saying, what the hell are we supposed to do.
Basically every day is like going to the zoo. Without the fun part.5
I need some advice here... This will be a long one, please bear with me.
First, some background:
I'm a senior level developer working in a company that primarily doesn't produce software like most fast paced companies. Lots of legacy code, old processes, etc. It's very slow and bureaucratic to say the least, and much of the management and lead engineering talent subscribes to the very old school way of managing projects (commit up front, fixed budget, deliver or else...), but they let us use agile to run our team, so long as we meet our commitments (!!). We are also largely populated by people who aren't really software engineers but who do software work, so being one myself I'm actually a fish out of water... Our lead engineer is one of these people who doesn't understand software engineering and is very types when it comes to managing a project.
That being said, we have this project we've been working for a while and we've been churning on it for the better part of two years - with multiple changes in mediocre contribution to development along the way (mainly due to development talent being hard to secure from other projects). The application hasn't really been given the chance to have its core architecture developed to be really robust and elegant, in favor of "just making things work" in order to satisfy fake deliverables to give the customer.
This has led us to have to settle for a rickety architecture and sloppy technical debt that we can't take the time to properly fix because it doesn't (in the mind of the lead engineer - who isn't a software engineer mind you) deliver visible value. He's constantly changing his mind on what he wants to see working and functional, he zones out during sprint planning, tries to work stories not on the sprint backlog on the side, and doesn't let our product owner do her job. He's holding us to commitments we made in January and he's not listening when the team says we don't think we can deliver on what's left by the end of the year. He thinks it's reasonable to expect us to deliver and he's brushing us off.
We have a functional product now, but it's not very useful yet and still has some usability issues. It's still missing features, which we're being put under pressure to get implemented (even half-assed) by the end of the year.
Should I stand up for what I know is the right way to write software and push for something more stable sometime next year or settle for a "patch job" that we *might* deliver that will most definitely be buggy and be harder to maintain going forward? I feel like I'm fighting an uphill battle in trying to write good quality code in lieu of faster results and I just can't get behind settling for crap just because.9
Dear Dark Side #2
Open company projects on all screens
Open your hobby project bottom left screen
Code without guilt
Update company backlog4
We are all working our asses off, but the backlog grows and grows.
Now management came up with a really creative, groundbreaking and clever idea: We should work more, so we can get shit done.
I think there may be some jobs vacant in the near future.2
If I had to name one of my weaknesses it would definitely be impatience.
When I'm working on a backlog issue I want it to be done, finished, pronto. In the real world that's ofcourse not always the case, I can't disturb my colleagues with every question or ask for feedback every minute. I also hate it to have to wait for someone else to do something for me if it's blocking me, like when I need to fix something on a server but don't have access or when I somehow don't have permission for something and have to wait for someone to come and fix it. Even worse: Slow programs that fuck me up when I _just a second ago_ figured out how to fix a bug or implement something.
I also have to wait for pull request reviews so I usually end up with a bunch of stacked PRs that all feature small changes but are dependent upon each other because I needed a change for a different change, never more than 2-level stacks though!
Obviously it's a bit childish to lack professional patience, but it's definitely something that I wanted to rant about and think I should grow in.
The most obnoxious company process I've encountered so far is the nonexistent one.
This is what happened at my first professional job. PM and CTO quit after about a year, yet the top honchos were insistent of salvaging what was left of their "enterprise" software suite and putting us through a death march to try and continue development.
No plan, despite having a JIRA board filled with month-old backlog stories. No direction, because the CEO was now head of the project and wasn't in the office about 50% of the time, and our lead dev wasn't willing to take the reigns.
I wouldn't have minded trying a bunch of different things and having them fail. At least then we'd be doing something, you know? But instead we sat around, trying to squeeze any kind of goal from the higher ups, until I finally had enough and found a much better job.
It wasn't enough to convince me to give up software development. But boy, did it sure come close.
Small company, sole engineer. Non-tech management. Increasingly fancy job titles despite working alone most of the time, with the promise of hiring someone (again) I can actually manage soon.
Backlog of projects/tasks is truly a mindfuck, with new things being added each week. This backlog will never ever get done, and nothing matters anyway because the next idea is "the future", all the time.
While I have influence on some aspects of decision making, it usually ends up being what the boss wants. Actively opposed a project because it's just too big of an undertaking, it was forced through anyway. I'm trying to keep the scope manageable as I'm building it now, and it's hard.
"It's the future, we absolutely have to do this. It will be the biggest thing we've ever done."
Boss's excitement then quickly faded since it's actually in development, now nobody really seems to want to know where it's at, or how it will all work. I need to scope it out, with the knowledge that many decisions boss signed off will be questioned when he actually looks at it. We now have even more "exciting" ideas of utter grandeur. Stuff that I can't even begin to comprehend the complexity of, while struggling to keep a self imposed deadline on the current one.
Every single morning we sit on Zoom for a "valuable" "catch-up". This is absolutely perfect for one thing: Completely destroying whatever drive and focus I have going into the day. Unrelated topics, marketing conversations, even more ideas, ideas for ideas sake, small problems blown out of proportion, the list goes on. I recently argued in detail why it should be scrapped or at least be optional to attend. No luck, it's "valuable".
Today a new idea was announced, and we absolutely have to do it ASAP because it can only be better than the current solution. I raise my concerns, saying it's not as easy as you make it out to be, we should properly think about it. Nope! We'll botch something to prove that it works... So you'll base your decision whether it's good on some half ass botch job that nobody really has the mental capacity to actually pay attention to. What a reliable way to measure!
"Our analytics data isn't useful enough to tell us the impact of things we do. We (you) have to fix this." Over the last 2 or so years, I've been pushing for an overhaul and expansion of our data analysis capabilities for exactly this reason. Integrating different data sources into a unified solution so we can easily see what we're doing, etc. Nope, never happened.
The new project idea which is based on wild assumptions is ALWAYS more important than the groundwork.
Now when I mentioned that this is what I wanted to do all along, it got brushed aside. "We don't need to do anything complicated, just fix this, add that, and it's done. It should be an easy thing to do. This is very important for our decision making." Fine, have it your way.
I'm officially burned out. It's so fucking hard to get myself to focus on my work for more than an hour or two. I started a side project, and even that effort is falling victim to my day-job-induced apathy.
I'm tempted to hand in my resignation without another offer on the table. I just need time to rediscover my passion, and go job hunting from that position, instead of the utter desperation of right now.
If you've read through all this rambling, kudos to you!8
You get home from work and one half of your brain goes, "Let's just code a little to catch up on the backlog", and the other half of your brain goes, "No way you psycho, we're off from work and we're not getting paid for this. I'm not helping!"
And that's why you're code sucks when you're not at work!
Grabbed a case off of the backlog, and noticed the estimate was set to 100000 hours.
Time to get a coffee before tackling this task.4
"So.....I see that you're a strong SQL guy.....and this is a data role BUT can you help us clear out our web backlog?"1
So i’m looking through our backlog... and there is one issue called “gain trust”. No specifications whatsoever. Just “gain trust”. Wtf2
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.4
Don't forget to give the developers the opportunity to innovate. Nobody wants to sit and type out the same structures day after day. That's not why we got into this job. We like solving problems. In my current team we set aside some time every sprint to spend on individual innovation. Super useful as it gives us the chance to break out from the standard chugging of the backlog and spend some time trying to solve some of the trickier problems and bringing improvements back to the product that we discovered by messing around with stuff. If you are reading this and you are in charge of a development team, try this out for a sprint or 2.2
My team now does daily mini-standups: what you did, what you will do, what's blocking u
But with this wfh, I feel like slacking more or just seen to have less critical work to do... but not sure if the other guys are just "padding their list" or actually really busy.
So wondering when I have nothing to do for work/no defined deadlines or deliverables... How do you look busy?
I do have a lot of optional tech debt improvement work I could do but basically these are like backlog... And not really fun.6
So we have this really annoying bug in our system that customers keep complaining about. I've explained in detail, multiple times, why the part they think is a bug is not a bug and the workaround they keep asking me to apply doesn't make sense, won't fix the issue, and won't even stick (the system will notice that the record they want me to delete has been removed and it will repopulate itself, by design).
I've told them what we need to do as an actual workaround (change a field on the record) and what we need to do to properly fix the bug (change the default value on the record and give proper controls to change this value through the UI). We've had this conversation at least three times now over a period of several months. There is a user story in the backlog to apply the actual fix, but it just keeps getting deprioritized because these people don't care about bug fixes, only new features, new projects, new new new, shiny shiny new.
Today another developer received yet another report of this bug, and offered the suggested workaround of deleting the record. The nontechnical manager pings everyone to let them know that the correct workaround is to delete the record and to thank the other developer for his amazing detective work. I ping the developer in a private channel to let him know why this workaround doesn't work, and he brushes it off, saying that it's not an issue in this case because nobody will ever try to access the record (which is what would trigger it being regenerated).
A couple hours later, we get a report from support that one of the deleted records has been regenerated, and people are complaining about it.
I missed a half of an important meeting today... because my priority is a task given today that has a deadline today8
As I am now in a leading position in the middle of a agile transition:
has anyone got a source for a project done completely with user stories?
I am searching a real life example with already finished stories an active backlog and a documentation.
I just can't wrap my head around it. When and what do you document? In which Form do you document? How are you writing user stories with more content like diagrams and such?
(we use jira and confluence but just started with stories)
I read some articles on the topic and watched some talks but sill don't get the picture.8
At the product backlog refinement the product owner told us (the devs) how the database model must be designed! He said he knows it best, because he knows all the requirements. 🙈4
I worked a whole year in a company for which I produced 30 software and none of them saw the publication even though they were completed. I was the most productive employee and had a productivity of 428% compared with the other employees.
All because of the constant changes in business strategies.
For a moment I believed to be a pirate ship during a storm. When I was tired of the way they were treating employees, months of backlog payments, unpaid leave or not granted, I quit and I was told to me that I was a bad employee and I was unproductive.
In a month he is left only the designer working. At the moment the company in question is still looking for employees, after more than a year no one wanted to work again. Stupid me.
While I ras looking for another job I did freelance for a month, gaining about five times my earlier pay.
Someone created a category on Trello named Backlog
Can someone explain me what backlog is and what types of cards am i supposed to create in Backlog category7
I hate doing front-end development...
I was hired along with another dev to build a webapp to manage the personnel of this big (2000+) company.
I made the backend and some of the frontend (mainly handling the data movement between the two), but my partner was let go after we delivered a first version because "there was not enough work for both of us".
The backlog is months of work for me and now I have to do everything and it's wearing me down...
I want to quit but it's paying well and I don't want to search for something new.
I hate Jira so much.. I used it on my last workplace and later begun work in a company that does consulting, and of course the first project I was assigned to.. uses Jira. Goddamn it.
I can't understand how they can make it so complicated.. Or maybe it's the organizations? When I want to see what I can work on next I have to look up the backlog, which is at the bottom of multiple sprints. From there I see a list of user story titles, attached to epics and I have to click each one to read the description and see a label "Blocked" or "Requires refinement"... Takes me hours to shift through that shit! Project manager is basically MIA and I have to look at titles, labels, epic links and comments to figure out if I can work on a story, and then I have to split it across multiple tasks, because the story is titled as "as a user I want to read and browse articles from multiple different sources and categorize, filter, mark them as my favorites and...".
Tools like Trello, Clubhouse.io (by ignoring a ton of features) or just sticky notes on a whiteboard are much more efficient tools for workflows.7
How to kill Jira Backlog in one simple step:
1) put '-∞' to Storypoints
(Bottom line: it can be fixed from User Story Map to something normal)
The worst of Agile and Sc(r)um: All those people knowing the right way(™) to do it. Endless discussion about useless tooling: the proper use of the custom workflow in Jira, on when and how to create sub tickets. The hour-less meta-discussions on what should be discussed where and when (what's subject of the backlog refinement, retro, etc), the roles: the PO's, what he should do, cannot, the PM's. Who is allowed to pull a ticket to the sprint or not. How many reviewers need to acknowledge a pull request. To and fro. Pointless, but fought with heart and blood, full of sound and fury, signifying nothing.
And everywhere I hear: "In my previous company, we did Scrum like.. and it worked perfectly!"
Some of you might remember my rants on Mr. Gitmaster, with whom I thought I'd made my peace. Guess what? He's now a team member and turning into Mr. Agile - a more severe reincarnation! As our company starts flogging that dead horse of Agility, he seems to feel strong tailwind. Our team lead would constantly cut his monologues, but he's now on holiday, so we have no escape from the never ending: "In my previous company..."
If it was so great, why didn't you stay?
We are not allowed to pull a ticket to the sprint unless every team member is notified? I don't fucking care. If our software fails on customer's machines and I can fix it, I will do if there is a ticket, if it's in the sprint or not. Screw Scrum, if it is getting in the way of it. You can waste your hours discussing horseshit, I want to sit at my desk, deep in the test-compile loop and ship some fucking code.3
The story of how I knew I did the right thing leaving the start up I was an employee of.
It was a great place to work when I started, we had a plan and we were are working hard to make it. But pretty soon I realised that things weren't 100%. We kept altering the product and focusing on the wrong things. Our backlog grew faster than it was completed.
Pretty soon a launch planned in April was pushed back over and over again, until we finally released in November, and instead of being first on the market we were last.
We pivoted hard and I didn't believe in the new product so I quit.
The last week on the job I was finishing up some stuff and when our PO (who also was a programmer)was deploying the things I had done to production something went wrong. Now I had just integrated *his* new authorization service and I had a hunch it wasn't deployed. But he sent a message over slack with a bunch of code alterations that was the "problem". Along with some passive aggressive words about how I wasn't professional and didn't take ownership of the product.
I only added an error log that asked if the authorization service was deployed, and 10 minutes later he came up and said good job, no mention of what was fixed between now and then.
I have no regrets leaving that place.
Final day on this project, tonight I'll get drunk to forget about the backlog since client didn't hire me longer ( consultant).
I hate leaving unfinished code.
Monday I start my next project, which is refactoring. .Net code to .net core.
Here is to hoping it doesn't rely too much on unsupported 3rd party libraries.
Cheers fellow devs, have a good weekend.
I had a coworker that NEVER restarted his computer or installed updates of any kind. Any time he showed me some code I got distracted by the "new updates are available" popup that was always there in his IDE.
I can't even imagine the backlog of critical security updates that were waiting to be installed when we left after 3 years.3
Due to covid, mgrs decided to fire 10% but could not negotiate schedule increase with internal IT. With no promotions or hikes, few full stacks we have leave.
Now am working with 2 data engg doing cloud java microsvs work while learning. Their first delivery was applauded by their mgr who is under pressure to retain them.
I as arch review their code. No unit tests, print statements all around, shoddy exception handling, variable naming issues. We have Sonar by default in our build. They ignore the report. I ask them about it. Seems mgr told them he is getting a contract person from another team on part time basis to do/fix. I share my confusion.
Mgr calls me up and checks if we can put it as tech debt backlog and deploy to prod !!!1
Uuugh the 3rd of January first working day in my country, I am dreading 2018 already with the backlog of issues I decided not to fix in 2017 as if they'd magically disappear. Hello darkness my old friend...
Spent an entire day clearing the backlog of the previous sprints in JIRA. Now i am seeing jira numbers everywhere :/2
My work desk is ordered chaos. It's an unspectacular white desk.
To the left paper for taking notices... And a collection of notes highly unordered.
In the top left corner of the desk the router.
Middle (front to back): Color sorted post it's with my backlog and all the stuff that I need to keep track off.
Right (front to back): mailboxthingy, post it block, utensilo (made of bamboo)
That's the working desk. Like the "shining knight in armor"....
Next to the working desk is the play desk, a large kitchen table with a 5mm thick black rubber (keep your dirty thoughts for yourself ;)) as insulation and scratch prevention.
There is usually utter chaos.
Banana PI R2, test router, old hardware, hardware storage cabinet, screw and other small part cabinet....
And to the right is a large chest of drawers where I cram everything in that doesn't belong anywhere.
I'm pretty boring I guess.
Except you are kinky for old hardware and lots of weird stuff noone uses nowadays...
Then you're in heaven I guess.2
The project started as a series of individual prototypes. The client the wanted a beta app for a few selected clients, and someone had the great idea of just merging the prototypes into a single app. The attitude of the devs was always "whatever, this will be rebuilt for public release"
Over one year later, and after many different developers touched the project, the client wants it to go live, there was never a rebuild, and there won't be one until a few months after it goes live, and the project is buggier than it ever was.
A rebuild would have been quicker and safer than fixing the huge backlog of bugs, still the client won't accept a rebuild.
A few people already quit over this project and I think I will be the next one to hand in my resignation.
Every one of our sprint "planning" meetings.
We would sit and be told to estimate a bunch of defects we had never seen before. And then we wouldnt actually decide as a team what to commit to because it was assumed that we had to deliver everything in the backlog every sprint. This is what happens when you try to apply scrum to a maintenance team.
When you start a new job and you inherit a steaming pile of shit that NEEDS to integrate with a completely separate application but after repeatedly telling your manager his requests aren’t possible, he denies it and says it is possible.
Some context. They have an old application written in MVC. They want a new application written in react. They want all the old functionality to integrate with the new functionality. I don’t just mean render different views based on the route, I mean they want both applications to integrate seamlessly to create a new application. Not to mention this new application is completely different to the old one and has requirements that aren’t even compatible with the old application.
Also. I got into trouble today for completing the sprint in 2 days and starting on user stories (that were in the sprint, not the backlog). Apparently we’re not allowed to showcase the product until the sprint ends and we go through our retrospective/demo. LMAOOOO
So today we had a pre-sprint-planning meeting where the POs told us about the stories currently in the backlog. They went ahead and "roughly prioritised" some of them. Their priorities were:
- normal (but asap please)
- has to be done this sprint, because the feature has to be in the next release (code freeze after this sprint)
- top priority, because this has to be in the previous release (which was released last friday)
The non-normal stories alone are about twice our normal velocity. Good job guys. Good job.
We often give access to a product owner from the customer on our Jira to keep up a good communication and everyone stays up to date as everything is on the board and not hidden in emails or paper notes on the desk of the guy that is on vacation.
So far, so good
Our customers really like this as they can comment on tickets and they are integrated in the workflow because they can push into the backlog and can review finished tasks.
It is just getting better for everyone so where is the rant?
One project is just a dump of shitty mixed content tickets. But how? They look really neat. There are tickets like "fixes from meeting 20th of may" which are initially well structured with approximately 4 subtle changes to the UI and some explanation and screenshots.
PM says: Good ticket. There you go ticket, into the customer review loop of doom.
20 comments and 13 status changes later. Point 43 from comment 17 is referenced in comment 20 to keep on hold as a third party needs to give feedback, point 7 is still not solved correctly as dev 2 was not aware that it was already discussed and changed in the ticket "Call from 25th of may" where in addition the resolution of points 5-12 were requested with an additional excel file to import.
By now we have the 8th of august and literally 17 of these kind of tickets.
I guess we need to improve the workflow and request a new product owner. But this far I just table flip everytime I get one of these tickets assigned.2
So a Buggy production code caused data discrepency. This is fixed, and now the only task left is cleaning up the data, and this will be in my backlog forever.
High priority Bugs from the legacy system were pushing productive work out of the sprint enough that a 1 year project due in 2 months was sitting on 6 months of backlog of just my work. There are days where having 20+ years at the company is not a bonus. Fortunately I finally got through to the boss that he wouldn't make any ground on the project at this pace and he had the PM step in. Last sprint I worked on the project nearly full time.
You might think that getting your work done super fast is a good idea but it's really not. It takes QA awhile to test your tickets and give feedback. If you clear your sprint board, PMs will add more assignments... Then on top of that extra work, QA will give you feedback from your previous work. You now will be super stressed to get all of this done by the end of the sprint.
It is best to take your time and get it right the first time... I've also learned to make a buffer... which is tickets in my queue I've already completed but did not say I've competed yet. This way I can take extra time on tickets that need TLC and the PM team won't surprise you with backlog tickets.
I just finished my first internship this Friday. During off-boarding, my mentor said that amount of work I did was well above the industry standard, and that recruiters probably wouldn't believe me. He then proceeded to give me a stack of his cards, and said to tell them to give him a call so he could explain. The question I have is, why is it that most of the work that interns do is usually worthless? I mean even if companies hired them so they can get rid of that Jira backlog, that would be great, but talking to my other friends who basically got paid to basically watch Netflix at work, I don't know, it just makes me sad. Plus, this leaves me scared for the future, because what if I end up in an internship like that next summer? How can I tell the difference?4
Happy 1 of August to all Swiss lads on here. Let's celebrate by remembering the backlog of bugs some of us need to get fix by tomorrow.
I think I am going to keep a desktop counter of every time the other team bitches about not having tool x or tool y rather than learning the tools we already have that are perfectly capable of serving the purpose they want. I get that devs should be allowed to have the tools they need to do the job, but at a certain point you're yelling at a cloud to start raining. Especially since we work in a restricted environment and IT's backlog is ridiculous.
Last day before vacation, 6 hours left and all my PBIs are merged to main so I asked the project manager if I could add a Vacation PBI to our backlog :)
But he said: no Im sure we can create some tasks for you!
I thought I posted about this awhile back but I didn't. I'm glad since the story is so much better now.
6 weeks ago: Told I'm going to be on a super fun JAMStack build with lots of sexy animations. Sweet, this will be a fun build!
5 weeks ago: Find out what the timeline on this incredibly ambitious project is. I start raising flags cause everything needs to go PERFECT for this to not blow up and/or turn in to a dumpster fire.
4 weeks ago: Project "kicks off" with a meeting with the client. We find out that they've decided to do another round of revisions on their design comps, but we have what we need for sprint 1. We provide a list of all the assets/information we still need for sprint 1 success.
3 weeks ago: Still waiting on some assets for sprint one, but we're fumbling our way through. Still waiting on the PM to get around to doing their PM job and building out our backlog / gathering requirements for us.
2 weeks ago: Sprint 1's end date comes and goes. Still need assets from the client, I've personally asked them for the same asset 3 different times. Sprint 1 gets extended 1 week.
1 week ago: We deliver sprint 1 page templates, minus the resources we're still waiting for. Get chewed out by the client regarding the pages not looking like their comps (Yeah, no shit sherlock, you never sent us the assets)
This week: Working on Sprint 2 commitments. We have 2x as many page templates to deliver, per developer, as we had the first sprint. Still waiting on Sprint 1 assets. Don't have Sprint 2 assets. Wait, what about the global styles? They still haven't sent those to us yet either.
Requirements? Guess I'll spend valuable dev time tracking those down for myself.
Client? Well, they're pissed off we haven't hit our commitments yet.
Oh well, at least we have a pimple faced, fresh out of college, CS major, with no real development experience rolling on to this cesspool of a project.
Other devs? Well, we're out of fucks to give. Lets just watch this thing burn.
Oh, I forgot to add, we have 17 page templates to deliever between today (2/27) and 3/18. #NoFuckingWay
"Dear TitanLannister : You are in the final year. A lot of shit is happening around u. its now time to make a career and take tough decisions. What would you do?"
CHOICE 1: COMPETITIVE
>>>>background : "a lot of super companies like wallmart, fb, amazon, ms, google,.. etc simply takes a straight coding test for fresher placement. They ask tough bad ass level questions, but with right guidance, a hell ton of dedicated hours of coding, and making it to the top of various coding tests could make you a potential candidate"
>>>>+ve points :
- "You got the teachers and professionals with great experience to guide you"
- "a dream job come true.you can go there and join teams that interests you"
- "it was your first exposure to computer world. maybe you would like doing it again, after 4 years"
>>>> -ve points:
- "You have always been an average 70 percentile guy. The task requires 2000-3000 hours of coding an year. it will be hard and you always grow bored out of this pretty quickly"
- "Even If you did that , you stand a lesser chance because your maths is shitty.There are millions running in this race with brains faster than your IDE"
- "your college will riot with you because they expect 75% attendance"
- "You are virtually out of college placements, in which , even though shitty companies come and offer even shittier 4LPA packages($6000 per annum), would take a tough logical/aptitude based test for which you won't be able to prepare"
CHOICE 2: PROFESSIONAL WORK
>>>>background: "you always wanted to create something , and therefore you started taking android based courses. you have been doing android for over 2 years and today you know a lot of things in android. you might be good in other professional lines like web dev, data analytics, ml,ai, etc too if you give time to that"
>>>>+ve points :
- "you will love doing this, you always did"
- "With the support of a good team, you will always be able to complete tasks and build new things quickly"
- "Start ups might offer you the placement, they always need students with some good exposure"
>>>>-ve points :
- "Every established company which provides interesting dev work takes their first round as coding, and do not considers your extra curricular dev work. So you are placing your all hopes in 1 good start up with super offerings that would somehow be amazed by your average profile and offer you a position"
- "start ups are well, startups and may not offer a job security as strong as est. companies"
- "You are probably not as awesome dev as you think you are. for 2 years, you have only learned the concepts , and not launched more than 1 shitty app and a few open source work"
CHOICE 3: NON CODING
>>>>background: "companies coming in college placements have 1-2 rounds of aptitude,logical reasoning , analysis based questions and other non tech tests. There are also online tests available like elitmus,AMCAT, etc which, when cleared with good marks help receive placements from decent established companies like TCS, infosys, accenture,etc"
>>>>+ve points :
- "you will eventually get placed from college, or online tests"
- "there will be a job security, as most of these companies bonds the person for 2-3 years"
>>>> -ve points:
- "You really don't like this. These companies are low profile consultant/services based companies which would put you in any area: from testing to sales, and job offers are again $5000-6000 per annum at max"
- "Since it includes college, the other factors like your average cgpa and 1 backlog will play an opposing role"
- "Again, you are a 70 percentile avg guy. who knows you might not able to crack even these simple tests"
Ugh... I am fucking confused. Please be me, and help.The things that i wrote about myself are true, but the things that i assumed about super companies, start ups or low profile companies might not be correct, these points comes from my limited knowledge ,terrified and confused brain, after all.
I gave given my last exam (a backlog) and i am finally free! Hope I don't get a back one again :-(
Huh. this feels so weird. I am supposed to work now i guess? Or should do a masters and study more? I have been am average for most of my college life, am not sure if i want to be associated as a master or expert without being one.
And even if i go on with this, should i go for a business degree or a technical degree? Business seems like a popular choice everyone wanna be the top manager earning the real $$, but i have grown past my side passion for business. I am more into the tech side, but again, can someone ever be a master of technology?
And on the whole other end, i have somehow landed in a decent droid dev job where am getting to learn a lot and also earning a decent fresher salary. Should i be leaving it just to get that expert tag? If i spend some years doing work here, i might get enough knowledge to make any kind of mobile app and that's kind of an expert-ness itself,right?
After graduation life is weird (well not completely out of graduation, results are yet to come)1
Honest question: What do managers do in your company?
- Do they still code?
- How many direct reports do they have?
- Are they in charge of the sprint/backlog grooming?
- How frequently do they interact with their direct reports?
- And what's the subject of these interactions?
- what do they do outside of that time?
In my company, managers have 2-5 direct reports, do not code, and mostly talk about career development for 1 hour every other week with their reports. I'm not sure what they do outside of these few hours every week, despite asking multiple times.7
Just finished a backlog item that got rid of redudant code in about 10 classes and almost done with a feature that the marketing people will like
Who knew fridays could be this productive 😎1
Decided to start learning Swift as I became a Mac user back when I was in college (and I'm a Linux fan so win win?).
I went to college for Web design and development but think I should definitely be putting a big focus into app and game development/programming.
I also have a backlog of programming languages I'd like to at least familiarize myself with...
So back to Swift...anyone use it regularly here for app and/or game development?4
Sometimes as an intern I legitimately have no work to do and I feel awful about it. Sitting here twiddling my thumbs makes me feel like I'm doing something wrong. You can only ask for work so much... Trying to find things on our backlog to work on but they're all unfinished/not ready or too verbose / require too much for me to take on.
Mmmmehhhh I don't know what to dooooo3
- the 2 hr meeting called for every day of a week, to prepare for a PPT which is to be presented to a higher up exec within 5 mins.
- the sprint planning meeting, where all the stories of that sprint are already weighted and assigned to the devs, but it still goes for 2 hrs
- the backlog grooming meeting, where instead of looking at the sprint backlog, the current sprint is looked at and discussed.
So I was reading Scrum for my exam all I can see was Meeting.
Product backlog meeting for 15 mins;
Enters to the office 5 mins meeting;
Sprint review meeting for 10mins;
Daily scrum 2 times meetings;
Sprint planning 3 hours of meeting;
Starting the next Sprint 30mins meetings;
Managing releases 45 min meeting;
Sprint Retrospective 45 mins of meeting;
Wtf? Do they do any work there?4
Nooooo.... Why on earth do you do that.
Looking at the sysctl settings someone took a road trip to Google and stackoverflow and just copy pasted every mother fucking stupid bullshit bingo inside it.
Half of this doesn't apply as the kernel version doesn't even support it anymore (for good reasons) or makes sense as these settings have NOTHING not even REMOTELY to do with the servers hw setup.
If you have no fucking clue what you do, ram the keyboard up your arse till you enjoy it.
But stay the fuck away from administration and the fuck away from anything that carries responsibilities.
Joyful task today: unclogging old failing Haproxy setups while being busy with 3 other tasks.
And if you wanna know why they're failing and it needed to happen today... Weeeell....
They restarted. And today they decided to restart so fast people finally noticed it.
Cause yeah. They did that the last fucking years every few hours. Now every 5 minutes.
:@ :@ :@ :@ :@ :@
More talking with manager today. If i wanted to check out the 200+ issue backlog to see if there is anything i can pick up.
I was just laughing. I already do that on a weekly basis. It’s not that i dont want to work!
There was a department. Long time ago their work was somewhat complicated: background checks of businesses, websites, ToSes, assuring agreement compliance, some risk management on top. They started as small 3 people team but over the years they were hiring new employees to catch up with the growing customer base. They were still struggling. Few years back we've integrated 3rd party services to help them and, finally, their backlog was gone!
In January they complained about how much more work they have since the merger so I inquired about which process was troublesome, what was the flow, etc., and it turned out to be very... Tinder-like - the issue was the sheer number of cases:
1. open a case,
2. check results in few windows,
3. if green + green + green, move right.
4. else move left.
It was ridiculous, I wouldn't stand for that. I sat for an hour, made some ghosting scripts that followed same business logic and saved results alongside their actual decisions. Last week I compared the two and there was zero difference so I green-lit it with my boss and pushed to prod.
Oh, the happiness on their faces when they heard the news, the disbelief, the tears of joy!
And then it happened. After 4 years of being cautious not to stir the waters I did it again. Yesterday I accidentally replaced 17 people department with 3 scripts. How was I supposed to know it was *all* they were doing??1
What do you use for performance monitoring on your infrastructure?
My company uses zabbix, OpenNMS and Nagios to monitor different parts of our infrastructure (from shared web hosting to OCCAS to IPTV to FutureVoice to Atlassian servers) but has no real-time performance checks.
I’ve set netdata master with prometheus backlog and grafana dashboards to monitor different metrics, however I am not sure whether any better approach could be done. Any suggestions?2
So , a little update to this : https://devrant.com/rants/3591086/... (since f1973 decided to leave this platform *again* , the comment there would look awkward, but just adding it here for depicting my mental state right now).
Results are out. Those fucking assholes failed me by 1 mark(actually it would be a lot of marks since i got 39/100 and i already had 10/25 from my internal exams, so 29/75). I am pretty sure that if someone had realistically checked this, they would have given atleast 60/75 , because i have never given a better paper than this. I fucking nailed it.
Even if am totally wrong, i would say they didn't made humane evaluation. Final year students usually get 6-7 grace marks because they have careers ahead. If not that , then atleast they would havr considered the fucking corona , in which i went to a physical classroom ,all the way from home to a 25km far bullshity exam center where in the fucking morning, when covid cases were increasing at an alarming rate in india.
But nope. I am a failure for this exam.
So after lots of anger and sadness , i am thinking of some practical solutions. I have 3 options:
1) to give exam next year
2) to drop this paper as i have already completed the minimum no. Of credits required for the degree
3) to ask university for re-evaluation/ re totaling
Let me put forward my thoughts regarding each of these options
For 1) i don't wanna go with this. This was a useless subject for whom i studied at the extreme level to the best of my capabilities. I can't go any further than this
For 3) the my colleagues and parents (and the rebel inside me) is asking for this. But from what i have heard its very risky as they rarely ever increase the marks and usually its just a recounting of marks. Sometimes they even deduct marks , and you still have to reappear again. Plus this will cost me few bucks and will delay my degree by even more time than it already is. I got to be free from exams late, i got the results late , everything has been late for me. I am tired of being the last to feel relieved, for once i wish to hold my degree alongside my other college mates :''(
And that brings me to option #2 this feels bad, after working so hard for a subject , i have to drop this. And i guess this might show up in my degree as well as other important docs too which might cause hinderance in future.
So just sharing this small post here and looking for suggestions. I have to make a decision fast. Its already 5 days past results being declared and i have only 5 more days to decide weather i have to submit the form of re-evaluation or dropping the paper as whole.
So what do you think people? Do dropping a subject from degree effect your career /life in general? And am not just talking about a tech job. Like for eg even schools these days check parents qualifications before giving their children an admission, or other places where shit like this matter. So any honest thoughts on this?6
While logging a boatload of bugs on the code my junior dev checked in, I added a couple of items to our product backlog.
Instead of fixing his bugs, junior dev started pulling things from the backlog. I found this out when he messaged me about the requested search results sorting.
His message was:
"hey, the sorting is going to be harder than I thought. Angular 2 dropped native support of filters. But I did find an MIT licensed npm package that should let me add sorting functionality to our JSON data objects. "
BTW, junior dev has more than 3 years of professional experience in addition to a degree.6
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.
I'm so damn tired of being asked to set up "QC's" to check for data our client is supposed to be sending and alert them when it's considered "past due". Our customers pay us to manage and analyze the data they send us. If they don't send us data, that's their problem. Why all of a sudden is it my job to micromanage these people and remind them how/when to do their job?? I'm having enough trouble juggling all of the shit on our side of customer requests, but now I have to worry about making sure they handle the shit they are responsible for on their side?
Otherwise, if we don't remind them, then they yell at us like we dropped the ball. "Why didn't you tell us we didn't send you that data that we told you we were going to send!?"
But seriously. I get it. It's good customer service. And I'd rather someone alert me if I had a process break that was supposed to be sending data on a regular basis and I didn't realize it wasn't working how I intended. I get it. I'm just venting. I'm honestly more worked up about my ever growing backlog that I am never going to get caught up with at this rate.
Weekend ruined supporting legacy and poorly designed services coupled with poor architecture.
But "no project bandwidth" to refactor said services.
5 hours of data loss should now hopefully inspire a backlog re-shuffle.
Should I just tell my manager that being the most expensive developer on the team, it would be a good idea to just let me do what I'm supposed to be doing and not spending all my time involved in bs meetings that don't need me, other then because I'm part of the team, or fixing issues I didn't cause and have no idea about the app that causes it?
The difference between me figuring it out from scratch and someone else is just im more expensive.... And already have a shitload of backlog from all the other work that I get pulled into...3
Group project at uni, we're learning how to do scrum sprints. So here's a small story about all the ways it can go wrong.
We assign scrum master and product owner roles, what do those do? "We want to do design tho" they say two weeks later.
I end up doing the organization part and structuring the backlog.
"Alright, you guys will be the frontend team, your tasks are X and Y"
One day before the review I ask again
"So, what's the status" (well knowing that they didn't do shit so far)
They start scrambling around, and manage to do like 30% of their tasks at best, I end up doing most of the work for them.
Next week, new sprint, our tutors somehow don't notice that literally 95% of the code has been written by me so far.
"Alright team, hopefully you will do better this time, so and so will be your subteam leader since he knows this stuff"
Some guys start working on independent things without collaborating with each other, sometimes replicating stuff I already did (but obviously worse).
So that's the situation so far, I really would rather kill myself than keep working with these guys, jeeesus1
It's Tuesday and backlog grooming... This feels unnatural. It is not any less boring on Tuesday then a Monday. 😳
Noticing that we have several stories in sprint that are scattered across the backlog, some are at the top, some at the bottom...
Me: I think we should prioritize the backlog.
PO: I agree; When do you think you'll be done?1
I finally have some motivation to write some personal code... on an existing project.
(Work has been too hectic the last few months so don't want to do anymore at home...)
Anyway... I noticed that my Prime Video Tracker app doesn't pick up some of the new Movies now available on Prime, so I did some fixing.
Good News (GN): The search URL is actually static so can goto the same URL for the same search results
GN: The program can filter the movies by a Minimum # of Ratings they have (currently set to 100... use to be 10)
Bad News (BN): The number of movies in the search results is over 5000 (used to be 100-200) so even with this filter, a lot get returned.
GN: the traversal is fully automated
BN: Need to manually look at the descriptions of each and add them the Watchlist
BN: I now have 200 movies on my Watchlist and still going...
So now I have another "Infinite list". Existing ones:
-Blinkist Read List
-Comics (sort of, I have a huge backlog for Cyanide and Happiness)
-Photos that need "post-processing"
I'm pretty sure I'm forgetting some others...
First project at new company ended up shit as clients kept using the backlog to define and refine their business requirements. Did not go to production.
Second project at same company ended up the same way, except it had more infrastructure issues than technical debt (and an asshole for a project manager).
Basically I'm scoring 2 for 2, and totally expecting my next project to be doomed too for a 3 score. Maybe I'll build up enough rep as that guy who dooms projects to just sit on my ass and collect my paycheck while I work on my personal stuff.
I work at a small shop.
Just a few devs and a handful of other people.
Good people. Even before COVID I worked from home a great deal.
But man there was always a lot to do at a small shop with priorities changing based on this customer's need or that one.
Now with COVID things are slowing down a bit and I can see some light at the end of the tunnel of my backlog.
I really would like to do some serious refactoring of an application I wrote, I'm embarrassed everytime I have to fiddle with it ;)
So I am an average final year engg student with
backlog in a subject that i hate and have already failed twice. Apart from that am a decent dev with a okay-ish resume who can code good stuff.
May is about to come and most probably we will be having papers. Should I :
a. continue studying my college subjects because I will have shit falling on me once the papers start and thus that's most important right now ?
b. go out and look for remote internships/jobs because our cash is running out and family needs money ?
c. cry in the corner of my closet because i don't have the balls to make this decision?3
Should you get tasks from the backlog when everything is done in actual Sprint? Or it is a good time to keep learning while waiting for next Sprint?3
Sometimes i feel there are so much gaps in my knowledge... I have been making apps for quite a while, using a lot of apis and system classes/functions , yet there are a lot of things that i haven't explored. what's more there are some things like context, lifecyles, views and recycler adapters, etc that i use in my every app perfectly, but yet i don't completely understand their working in the background.
I feel this backlog is killing me. but again i am already lagging behind the current modern practices. like coroutines are being widely adopted and used now , but i am yet to even understand how they work
Front log and backlog, i am just burdened with so many logs :/1
I’m so fucking bored..
we know there’s lots of requirements coming at some point and we’ll be as busy as it can get, but right now, we’re just sitting on our arses trying to find anything to do..
And working from home is not helping with the boredness..
So...I think NodeJS is cool.
I confess 2 years post college I've decided to learn it. Should've done it sooner.
It's been on my backlog along with AngularJS and EmberJS
The moment a trainer u made your boss hire tells u, that it's far from normal that the devs (me) setup the tfs themselves and add also Backlog items, Testcases etc, because PO and Team leader are thinking TFS is way to technical and an developer only tool...
The biggest distraction in all issue trackers is the hemorrhaging backlog of tickets that will _never_ be done, or aren't important yet.
This is why I just choose not to even bother opening it and let my PM close them out. :-)
Jira on Android 🙄
I had an overview of the backlog, blocked, active issues, could see who works on what and so on ...
Accidentally pressed the back button, returned to the project. Now it's a single big list with only issue type, description and deadline. It's pretty much a guessing game, which feature is open. Their seems to be no way to change that, not even deleting any data.
How did this happen?? Let me change it back!6