• Home
  • Blog
  • Projects
  • Bookshelf
  • About

Jabs and Fluff: On CTO Office Hours






If your technology organization is anything like ours (and it might not be), you'll find that the recurring CTO Office Hours meet is usually a waste of time.

The questions submitted (either live or ahead of time) are a mix of jabs and fluff.

The jabs are usually pointed questions, that never get a sufficient answer during the meeting and the asker usually is asked to follow up directly via DMs that they usually never actually do.

The fluff are the questions like "When will we get better coffee in the office?", they somehow become the questions that get the most direct and to the point answers.

TL;DR: Just skip the meets!



Tags:

Loading...

Published 📅:
Last modified 📝:

Related Posts

micropost

Tip: Secrets for Cloudflare Workers

Published:

Tip: GitHub Created Date Filtering

Published:

Link: Next.js Is Infuriating

Published:

Dependabot Hell

Published:

Link: What the hell is going on right now?

Published:

Recipe: Horchata Protein Latte

Published:

Zombie Retros

Published:

Link: How I build software quickly

Published:

Vacation (and streaks)

Published:

Polish is Important

Published:

<Blank> Driven Development

Published:

All Documentation Should Be Dated

Published:

Adding Microposts

Published:

Service Monitors and Observability

Published:

Leveraging service monitors properly to improve service observability.

Being Unopinionated

Published:

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

Stop Snacking

Published:

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published:

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

← Back to all posts
Hot Take
micropost
Share this post on Bluesky
See discussion on Bluesky
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....