We just need to change one field into an array, so that users can be linked to more than one location.
We estimate around 400 hours work.
We estimate around 400 hours work-
In order to analyze the problem, inform stakeholders and a allow for a brief period for outlining the next potential steps to be decided by the steering committee. Once there, we can talk about allocating developer hours to enabling the resolution and it’s required upgraded dependencies. See my previous estimate sent 2/7/2018.
Oh the flashbacks… Do you work in healthcare or banking?
AR application development.
Good lord it’s everywhere. Get the flamethrowers…
Sounds like job security to me.
Jokes on them I charge by the hour
I was about to say. Rejoice! If this is a client these are billable hours
yea, but it stops being fun when they say it’s a bug and it’s always supposed to work like that.
Then it’s a valuable lesson in writing your client contracts and your work change order templates.
If you bid per project you need to have clear milestones and sign-offs. If you bill per hour then it’s not issue.
I pretend I do not see it
You’d think this is stupid but this has surprisingly worked on more than one occasion for me.
Lmao power move
3 years and $5m down the drain for something we just got in production this year.
Could have been worse?
Thats what end of life-ing your products is for 😎
How about end of life-ing your client?
😎
deleted by creator
“When you do things the right way, people won’t be sure you’ve done anything at all.”
That’s why you get everything in writing. No change without detailed description of what you’re doing and a written reply stating that yes, this is what they want. Otherwise you’ll be in a constant refactoring treadmill.
I’m working for a big company and our end-user has a lot of ideas of what features he wants. The only issue is that he changes his mind at the end of each sprint or in the middle of it. I am happy he has ideas for making the work more efficient because at the end of the day that’s the major point of our work, but he can’t lock down a deliverable. We have a business admin that’s supposed to work out the actual work we need to do but this end user both won’t take no for an answer for his idea and won’t stick to his own script. I’d describe it less as a feature creep and more as a bunch of lateral moves and shifting goalposts that doesn’t always amount to something better than the first interation yet it’s still somehow a major blocker. Not only that but the big picture ideas get lost in his own plans and it becomes all about the small things he didnt articulate when I present the work.
It’s getting pretty frustrating.
Solid change control. I’ve seen so many project come undone through lack of change control. You can only develop with stable requirements and changes to requirements should come with a cost. Without it it’s basically offering unlimited development forever, often on fixed fee contracts too.
deleted by creator
This literally happened in my meeting last week. Top position development manager was complaining the existing thing was shit. Basically means we have to build a new thing from scratch. And guess what? The deadline is 12 Sep.
If you think it was shit why did you let them do what they did in the past?
I just had to rewrite all my code for 3rd time in a row and I am the customer. Ughhhh
Twitter API user found.
I mean I am the one causing myself to have to rewrite my code. I am developing a VR Theme Park.
Jokes on you, I like refactoring code.
Refactoring is healthy for code.
This is a good thing!
Bro that’s just Tuesday
It’s a good thing I’m a hobbyist so that I can avoi- hmm, now that I think about it this feature could be really cool and shouldn’t take too long to implement…
2am me: why the fuck this doesn’t work anymore!!!
Spouse at 7:00 AM: “Why do only some of the house lights work and there’s no hot water?”
Me: “You know that quick fix I was working on last night. Well, umm, one thing led to another aaaand… Umm… Just so you know, your phone is using mobile data because the wifi is out.”
Composition helps a little at least
My favorite thing was having to rewrite an enormous amount of code to support a new feature because the original architect originally wrote an enormous amount of code in anticipation of supporting a new feature like it.
And you’ll have to do documentation and everything and then they won’t even use it.
