Bingo of Awful IT Processes
-
This post did not contain any content.
Any extra points for hitting the "Finished the feature?" square three times for the same feature?
-
This post did not contain any content.
No requirements = nothing done, all requirements met
-
I've a slight manageable case of ADHD and I tend to obsessively hyperfocus on tasks. It's a good relationship because I get a lot of shit done well, and enjoy my work.
If you start forcing me to plan out my day every day, down to 15 minute increments, my productivity drops by around 60%, because I stop concentrating on getting shit done, and start working to rule. Not because I'm vindictive, but because that's what you asked me to do.
Is that what people mean by time tracker?
I meant just writing down what you did and how long you worked on it during that day.
I'm quite lucky, I just have to basically fill in "8h" every day on the same project and then I'm finished. But other people are forced to be very detailed and it sucks.
-
That depends on your team composition. Decoupling story points and hours means that the points indicate the complexity of the task; each developer might take a different amount of time to deliver that depending on their ability and expertise in that part of the system. The points give you a simple metric to show how much complexity the team have left to deliver, and tasks get assigned to whoever is best placed to deliver them at the time.
-
Story points are evil because they were intended to help teams set achievable goals but are almost never used as such. Once a manager catches wind of this practice, they will bastardize it into a pile of shit most high. Scrum doesn’t prescribe this practice so ditch it. Reject it and move to something only the team members will understand. If you move to relative animal sizes or some shit and you meet your goals, managers can fuck right off.
-
If this were a 5x5, I'd have the free square in the middle be "aI-pOwErEd"
Weirdly, after a certain percentage of useless meetings (that should have been an email) it does become more productive to make the AI "do the job": not because it's actually efficient, but an AI is never interrupted for a pointless meeting for hours.
-
if i fill every space, what do i win?
Return to office mandate and a slice of cold pizza.
-
What’s wrong with a time tracker?
I've worked in once place where I was support (no projects, all work came from and was tracked in tickets). Since everyone had to use the time tracking system anyway, I had to enter 8 hours every day. I was salaried, so no OT or docked pay for time off; I entered the same 5x8 every week, regardless of what or when I worked that week. Pointless.
Another time, I was subcontracting and had to enter time for the same projects for both my employer and the company that hired us. My employer wanted time submitted twice a month, and the hiring company demanded weekly. Tedious.
Two of these three companies were irrationally anal about pre-filling the time sheets, even when the hours were well planned or functionally irrelevant.
Last time I had to track time it was on a shitty spreadsheet that had to be printed out and signed by my boss. I was salaried. There were usually no changes from week to week.
They also had a digital time tracking solution that they just refused to use because that would involve change and change is bad.
-
My project is doing 12 of those. Guess who has another job interview round next Friday?
You're getting job interviews?
-
This post did not contain any content.
This is less awful IT practice and basically just bad development practice.
Working in IT support, you developers are a different breed of users.
-
This is less awful IT practice and basically just bad development practice.
Working in IT support, you developers are a different breed of users.
We clash! While we try to squeeze every last bit out of our hardware and tools, you are trying to keep us in check and not installing random shit because it might make us 0.1% faster
-
This post did not contain any content.
I dont work in IT but minor, minor, minor tweaks in the wording describes basically every job ive ever had.
-
Story points are evil because they were intended to help teams set achievable goals but are almost never used as such. Once a manager catches wind of this practice, they will bastardize it into a pile of shit most high. Scrum doesn’t prescribe this practice so ditch it. Reject it and move to something only the team members will understand. If you move to relative animal sizes or some shit and you meet your goals, managers can fuck right off.
Maybe you need to find a job with better management....
-
You're getting job interviews?
Rarely, but it happens.
But I can't shake off the feeling that in most cases recruiters completely misunderstood or misrepresented requirements for the position to get me to the technical interview stage. Like scheduling me for an interview with a team heavy with functional, big data processing while I barely have any purely functional experience.
Non-technical people doing recruitment work is a scam.
-
This post did not contain any content.
I'm currently one week into a two week period where all of the CEOs and project managers of my company are simultaneously on vacation. It's wonderful, just coding without being bothered.
-
I'm currently one week into a two week period where all of the CEOs and project managers of my company are simultaneously on vacation. It's wonderful, just coding without being bothered.
This. Sometimes it's enough for one person to be OoO and suddenly you can code in silence, work is being done, standups go from 1 hour to 10 minutes. No extra stupid tasks randomly handed out.
I wish that person at my project had at least 3x more paid vacations.
-
We clash! While we try to squeeze every last bit out of our hardware and tools, you are trying to keep us in check and not installing random shit because it might make us 0.1% faster
My best friend is a developer, and I personally have a lot of respect for the work you all do.
One thing I can definitely say is a positive of working with your kind, is that you people don't have printer issues.
I hate printers.
-
Worse than 1 hour standup and 4 hour planning:
1 hour daily standups and 30 minute planning meetings.
I've been on a team that consistently congratulated themselves on how fast and smooth planning is, when none of the stories would have acceptance criteria or real descriptions at the end of the meeting, and then we'd have to spend tons of extra time during daily standup actually figuring out wtf the work was
After a point in your career you either learn the skills and get the experience to understand how to plan projects and end up on those groups writing the definitions, or you remain an IC and just code what was given to you.
