Hacker News new | ask | show | jobs
by itissid 1204 days ago
For most people(junior and midlevel), there are two kinds of meetings: 1. Where you seek to get some information that is non trivial to ask on slack or at a water-cooler. 2. You are asked to contribute information that you already have.

Everything else that requires thinking and is a follow up, i.e. you can delay it(probably on slack of lunch or 1:1).

Also always try recording a meeting(minute big ones or voice record with consent to go over later). Forgetting and misremembering the facts a day or week later is probable.

3 comments

>Also always try recording a meeting(minute big ones or voice record with consent to go over later). Forgetting and misremembering the facts a day or week later is probable.

And if you or someone didn't take minutes or record it, followup with the participants in an email memorializing what you took away from the meeting and correct you if you misunderstood or forgot/left anything out. Sadly this is a bit of CYA (Covering Your Ass) but can help when questions like "who choose to go with that solution route and why?" arise weeks or months later.

"That's a really interesting idea. Hmmm, it's worth checking out. I'm really busy working on [hyper duct work over modulator], so gimme a few days to try some things. I'll get back to you, whatever I find. Thanks for speaking up!"

Always praise the suggestion. Diplomacy beats correctness in such situations.

Most often, whoever is in charge of the schedule will push back for you. Can't risk the deadline every time someone has a goofy idea.

I feel like this is culture dependent. In my country and workplace, praising like this would uncanny.
> You are asked to contribute information that you already have.

Just ask me the things you want to know over chat or email. 90% of the time I have to look something up. Do you want to sit and watch me as I poke around for answers? Or do you want me to recite answers that I'm 70% confident on and then try acting on that?