Funny

Exactly. If Caleb had it in writing that he was going to be paid regardless then the dude had some serious leverage.

Nah, "call me" always means "let's make this a real-time social hierarchy game, because I'm good at exploiting verbal cues and expectations to shove people toward my desired goal."

In my experience "please call me" is more often business speak for "you've really got a problem now" than a statement of weakness. Like they've got too much shit to say to you to fit in an email, and they maybe don't want what they're about to say to be written down

The irony is that, for the job I have now (which I LOVE!) I spent the interview talking about the databases and resources I'd created in the former shit job, and that work got me hired. My new employers treat me like absolute gold.

It's a middle manager whose presence isn't needed in daily stand-ups, as evidenced by the attempted micromanaging. We don't invite those fuckers to stand-ups because they just talk about useless metrics the whole time.

They also may have just not checked to see if everyone was on the call, especially if that meeting has a bunch of people on it.

It does seem probably fake, but being able to set boundaries and say no is definitely a major saving grace of freelance work, even if you have strong reasons to be professional about it.

It does, and it's old, but it's still a good story.

It makes sense if you're in an industry with hotspot flare-ups. I work MSP IT and those morning meeting are the way my team asks for help on pressing issues, or rings the alarm bells on business impacting outages. Additionally, Tier I helpdesk and Tier III projects never communicate, so the SUM is where T1 hears about where projects are at (in case they get the breakfix for that item) and T3 knows how swamped T1 is and what mobile techs are out, and T2 gets a chance to tell us if the flow from T1 and T3 into the "escalation sandwich" is too much. And we genuinely have it down pat to 5-10min.

Don't get me wrong, I've had shitty SUM requirements, but when they're done right, it's better than a state of the union email/Teams message.

I disagree, we're all remote so most of the time we have no idea what's going on with other people. Dailies are basically "Ok where are we? What are we doing?" and we're done in 10-15 minutes. Daily really is one of the most useful meetings for me. We experimented with thread approach but it was horible, no one was reading it and we became desynchronized really quickly

Unfortunately there are many juniors that you give the job of doing A to C, and if you come back a week later they'll report they're still stuck at job A, point 1 and didn't want to message anyone, and is something a senior can fix in 5 minutes. Even worse you message them and they just report everything is ok, they're working on it. Of course they never update the status of the project so you never know if they're stuck or just not updating.

That makes daily meetings necessary so they don't lose the entire week and delay the project. Unfortunately more senior members also get dragged in those meetings. It's a frustrating part of working with mixed teams and a "just let me code" mentality.

Generally true. We have a daily 30m “standup” but mostly it’s just us shooting the shot because we’re all remote, and it’s a way to socialize a bit. It’s pretty much optional but most of us usually show up just to chat a bit.

We do our real meeting on Monday mornings

Here's part 2 for those who don't want to click links.

Nice, Nitter link in case someone prefers: https://nitter.net/BirdRespecter/status/1483897633210974208#m

Fucking awesome lol. Sorry pal, you can’t just “forget I said that” and walk away 🖕

I understood most of those words, and still have very little idea of what is going on. Something to do with coffee?

I have no idea what a prio is, or a blocker in this context.

Depending on the work and the contract, it may be the company burning a bridge. Specialized labour can be both difficult and expensive to find.