Andrei Warkentin Profile picture
Sep 18, 2020 21 tweets 3 min read Read on X
I've been a corp citizen for 15 years now. I've learned that most meetings really can and should be an email.
1:1 meetings are good - they are the quickest way to sort out any kind of a question, discussion or argument. If you send an email, and the reply comes back with more questions than you had statements - time for a call. Don't play email tag.
Status meetings are also good, but must have an agenda. When you need to quickly communicate across a group what has been done, and you don't care about a paper trail, meetings == great.
Scheduling meetings are also okay, but you must have an agenda and concrete list of tasks. Either folks in your meeting know what they should be doing, and this is about communicating to others, or *you* know what others should be doing. Spread/assign the tasks and get out.
Here's what meetings are awful for - figuring out what to do. The committee. This is where all the memes are for. This is real. There is no action, no accountability. or ownership. Most won't speak up, but some will gladly provide counterpoints to any tangible proposals.
The solution is simple. Split a problem into subtasks, and empower the owners to make and document decisions. Have others provide written feedback. Only meet if necessary to resolve differences, and try to stick to 1:1 or as small of a group as necessary to address a concern.
Any meeting longer than an hour is probably not going to get anywhere. Stick to 45 minutes. People get tired. Most join meetings very tired already.
Any meeting with more than 3 agenda items is not going to get anywhere. I once was in a meeting with 15 agenda items and 60 minutes. 3 minutes per discussion point?
Any meeting with more than 3-5 people is usually extremely generic and shallow in terms of subject coverage -> a waste of time.
The worst are the 20+ meetings. A meeting where everyone except for two folks is silent and that seems to go on forever. These are usually some kind of planning or worse, planning to plan meetings.
Another bad variety is the "external update" meeting. This is close to "planning" variety. 20+ and a shallow slide deck that gets monotonously read out. If you're really unlucky, you'll have one or two folks continuously interrupting as well, so you'll never see the end.
I mean, I have eyes. Send me the deck. Send me your PPT notes. This isn't an audiobook. If I have questions, I'll have time to think and formulate these. And I bet I can skim over your deck faster than you can read one slide.
Useless and bad meetings are a real productivity killer. Personally, two bad meetings and I'm done. I'll feel frustrated and completely drained, I won't be able to go deep into a problem that day.
Pro tip: don't attend optional meetings. If you someone needs you to be there, you won't be optional. If organizing, stick to the smallest set of people necessary to be productive. This is almost never more than 3-4 people.
Pro tip 2: don't attend meetings that have unclear agenda or an agenda that doesn't seem to correlate to anything you're doing. If organizing a meeting, it should be obvious to everybody why they are there.
Pro tip 3: don't waste your time. If you a meeting is a waste of time, get out or just don't join again.
Pro tip 4: delegate. There comes a time in every engineer's life when he or she starts getting brought into discussions, and it feels refreshing, but don't let that get into your head. Use your time wisely, and let others step in if they are more appropriate. Don't be a funnel!
Pro tip 5: send slide decks ahead.
Pro tip 6: don't *ever* read-off slides. Summarize or highlight the most important point or outcome.
Pro tip 7: no animations. Always allow your audience to see the full content of the slide.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Andrei Warkentin

Andrei Warkentin Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @WhatAintInside

Oct 12, 2020
So back in 2019 OCTO was hosting an internal CTO ambassadors conference where I got an interesting request to put together a fun demo around Pi 3. Now remember that during VMworld 2018 in Vegas ESXi on Pi didn't exist yet...
In our OCTO Arm booth in Vegas folks kinda dared to make it happen, and we did... in just a few months we had a demo at VMworld 2018 in BCN of ESXi booting on Pi 3, IIRC with USB support (net, storage and HID)
...but there were no VMs: no GIC and barely any left-over RAM. I was scratching my head on how to make any Pi demo interesting. First I settled on cooking up a hybrid image that could boot Photon OS or ESXi, all from UEFI, to show the power of the UEFI fw and standards.
Read 19 tweets
Oct 12, 2020
Doom with @esxi_arm is much better with sound
Shown with the @NXP FRWY (LS1046A-based).
Audigy is plugged into an m.2 Key E to PCIe extender.
Read 8 tweets
Oct 6, 2020
@esxi_arm Yup! Getting firmware working and polished is a massive massive undertaking. One that I and a very special set of folks from around the world have been driving over the course of a few years now. All as a side act.
@esxi_arm It all started in 2016, when Microsoft put out Windows 10 IoT for Pi 2/3 and released the sources to their TianoCore modifications github.com/ms-iot/RPi-UEFI
@esxi_arm In 2017, Ard Biesheuvel separately developed an early port of 64-bit UEFI support. And this one had PSCI (via TF-A, then called ATF).

workofard.com/2017/02/uefi-o…
Read 26 tweets
Oct 6, 2020
Any massive launch today - developer.arm.com/architectures/….
This is truly massive. Extending the "power of boring" beyond servers to other footprints.
SystemReady SR is what used to be called ServerReady.
Read 8 tweets
Oct 4, 2020
It's 2020 and Linux NFS client still can't locally remap UIDs to remote ones without messing with a server you may have no control over.
With CIFS? Easy.

//10.0.1.4/Public /qnap/Public cifs credentials=/home/andreiw/cifscreds,uid=andreiw 0 0
Note that this has nothing to do with CIFS. Nothing at all. But it speaks volumes about the developer investment in supporting NFS vs CIFS clients in Linux.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(