PM: I want a status report
ME: Here you go (sending email)
PM: I want more status (!?)
ME: Ok (adding some random bullshit)
PM: Perfect, thank you!

Monday Status Report:
Production: Fucked,
Dev: Super Fucked,
Deliverables due today: Extra Fucked,
Phone: Ultra Fucked (rant brought to you today by Chrome ext),
Car 1: Mega Fucked,
Car 2: Slightly Fucked,
Jeep: Completely Fucked,
House: Copiously Fucked,
Today: FUCK

Got this status from another dev:

"Other than the fact that nothing's working, everything's going great!"

Yes yes yes
Let's spend countless hours writing painful spaghetti that generates a financial report, extend that spaghetti for specs, then not bother to check the amounts or status. or where it says the money went. Nope, checking non-unique names is totally good enough. We're so good at this. Ten points to the legendaries.

Let's also make the object factories not create the objects correctly, and make sure that report includes entries for orders that don't include any actual payments. Oh, their status? "Ready to send" of course! Let's send that totally valid $0.00 to nobody!

Oh, but Root. Root, root, root. You can't ADD payments to this. no no no. if you do, it'll break specs everywhere else that uses that factory! Shame on you for suggesting it.

Pssh, now you want to make a payment just for this report? Why would you do that? Our best devs have been working on this for years! What could you possibly know that they don't? No, they're perfect. Don't touch them. Just make them better, okay? No take, only throw!

Manager: "Hi Almond, how is X going?"

Almond: "...I don't know, Bob is in charge of that."

Manager: "Ok. Do you know the status of Y at all?"

Almond: "Not sure, isn't that Bob's responsibility too?"

Manager: "Well, yeah, but I never seem to be able to get a good answer out of him. Find out on both fronts and let me know ASAP please"

...sure, I know how this goes. I'll stop all the dev work I'm doing, do your job for you, talk to the lazy bonehead that never bothers doing anything, report back that he's done sod all (or still "in a requirements gathering phase" as he puts it), be asked "why is he taking so long", have a bit more back and forth, then decide we'll just leave him be as actually trying to get him to do any work is going to be too much like hassle 😒

1. Start ur day posting Good morning in #general thread.
2. Say Hello Team in the project group (slack).
3. Have a standup call with the entire team and discuss what everyone would be doing.
4. Evening 6 pm go on another call with the team explaining what you did for the day.
5. Time tracking software should always be on, so we can monitor your keystrokes.
6. Track time on Clickup tasks, as well as move them to appropriate tabs indicating their status.
7. Before u log off, post a detailed report on the group chat about what you did for the day.

Surely, this will increase productivity of the team, right?

devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.

It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...

'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'

... the company aimed to increase collaboration between the 2 worlds, and make development more agile.

The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!

PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!

YOU STUPID APPLICATION MANAGER STOP PROLONGING THIS MEETING FOR THE LOVE OF GOD this is a daily scrum not a status report you solid twat stop asking when something will be done when it hasn't even been worked on yet

Dev: "I'll start working on the thing today, might take a day or two to finish development"
Twat: "Will it be ready for testing tmorrow"
D: "Maybe by late tomorrow? If all goes well"
T: "So it'll be tested by tomorrow"
D: "Uhhhh wait"
T: "It'll be done by tomorrow"
D: "But"

GODDAMNIT MAN HE'LL TELL YOU TOMORROW IF IT'S DONE OR NOT AND IF IT CAN BE TESTED I want to punch you so hard in the face with a spiked mallet covered in wasp stingers and hello kitty juice to excacerbate your diabetes you filthy piece of excrement waiting to be smeared across the pavement with my boot

*At the daily status meeting*
Manager: I don’t have anything to table or anything I want to ask about. I honestly don’t know what the point of this meeting even is.

*Throughout every other living breathing moment of time*
Manager: Hey, I had an idea
Manager: Hey, I wanted to get your thoughts on something
Manager: Hey, what do you think about…
Manager: Hey, what are you currently working on?
Manager: Do you think you could just *sneak* in this new feature request and have it to me by EOD?
Manager: Hey, I just sent you an email
The email: Hey I think I found a bug, it’s with image alignment in Microsoft Word and it’s pretty breaking to my productivity report. Do you think you could take a look right now? Thoughts?

Please tell me something wrong with me, and whole world is working like that! It can't be right! Or could it, and I'm just one sad fuck who don't know shit?

So... We've got:
1. Jira reporting (agile style with cards and shit)
2. Task timers (via application integrated to Jira in order to count how much time we spent on a task)
3. End of the day email reporting with description of what we have done today (Jira is not enough?)
4. Daily morning meetings with a team leader to report what we're gonna do today
5. Git merge code reviews for each finished component (that lasts for hours)
6. Weekly status meetings
7. Working hours reporting with a fucking fingerprint

And on top of all of that, the developer is the one who just writes the code - team leader decides how this code is gonna look, what will be written first and what last, what libraries will be used and so on...

So one of my clients had a different company do a penetrationtest on one of my older projects.

So before hand I checked the old project and upgraded a few things on the server. And I thought to myself lets leave something open and see if they will find it.

So I left jquery 1.11.3 in it with a known xss vulnerability in it. Even chrome gives a warning about this issue if you open the audit tab.

Well first round they found that the site was not using a csrf token. And yeah when I build it 8 years ago to my knowledge that was not really a thing yet.

And who is going to make a fake version of this questionair with 200 questions about their farm and then send it to our server again. That's not going to help any hacker because everything that is entered gets checked on the farm again by an inspector. But well csrf is indeed considered the norm so I took an hour out of my day to build one. Because all the ones I found where to complicated for my taste. And added a little extra love by banning any ip that fails the csrf check.

Submitted the new version and asked if I could get a report on what they checked on. Now today few weeks later after hearing nothing yet. I send my client an email asking for the status.

I get a reaction. Everything is perfect now, good job!

In Dutch they said "goed gedaan" but that's like what I say to my puppy when he pisses outside and not in the house. But that might just be me. Not knowing what to do with remarks like that. I'm doing what I'm getting paid for. Saying, good job, your so great, keep up the good work. Are not things I need to hear. It's my job to do it right. I think it feels a bit like somebody clapping for you because you can walk. I'm getting off topic xD

But the xss vulnerability is still there unnoticed, and I still have no report on what they checked. So I have like zero trust in this penetration test.

And after the first round I already mentioned to the security guy in my clients company and my daily contact that they missed things. But they do not seem to care.

Another thing to check of their to do list and reducing their workload. Who cares if it's done well it's no longer their responsibility.

2018 disclaimer: if you can't walk not trying to offend you and I would applaud for you if you could suddenly walk again.

Here's some of my favorite quotes from "The Mythical Man-Month":

"The bearing of a child takes nine months no matter how many women are assigned".

"The management question ... is not whether to build a pilot system and throw it away. You will do that. The only question is whether to plan in advance to build a throwaway, or to promise to deliver the throwaway to customers."

"I once knew a boss who invariably picked up the phone to give orders before the end of the first paragraph in a status report. That response is guaranteed to squelch full disclosure."

I think I have made a big mistake. I posted a freelancer project to a FB group. I was trying to be very careful and vet people closely so there would be less chance of fraud. The guy I gave the work, and a deposit, to was either very, very, very good at constructing a bulletproof social media profile con game or he's just too busy to get back to me on a status report I asked for two days ago. :(

Send me status report.

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

Knowing that being asked to help the PM with his Client Project Status Report on a Friday evening means a) it's late, b) he has no idea what has happened since the last one and c) you'll be writing it all anyway.

Repeat each week for the rest of eternity