|
. keep them as short as possible.
. make sure only people required are invited.
. have an agenda.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
u failed to mention if its with a client or a co-worker
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Avoid meetings, stupidity is contageous.
|
|
|
|
|
If the meeting is to arrive at a decision, then have your RACI matrix or equivalent defined before invitations are sent to know who to invite and who will have final decision (R).
Ensure that R knows they are making the decision.
|
|
|
|
|
Same ones that work completely to make in person meetings effective.
...hmmm...oh wait...I forgot those don't exist either.
|
|
|
|
|
Do not invite rabble-rousers.
Make sure the agenda items will be pertinent for all invitees; anything that is not should be kept to a brief (30 second) summary (I despise all-hands meetings because they do not take care to do this)
If agenda items will not/do not pertain to a person, do not invite them.
iow do not waste my time. I enjoy meetings where work gets done, decisions get made, pertinent information gets shared, and therefore camaraderie gets built.
|
|
|
|
|
Cpichols wrote: Do not invite rabble-rousers.
Certainly no point in inviting anyone that is going to point out that the 'new' idea either can't work at all or it would take years to implement. After all reality isn't needed.
|
|
|
|
|
Some meetings are useful and important. Many more aren't.
As with all meetings (remote and otherwise) have an agenda ready beforehand and stick with it. And be uncomfortably brutal with asking yourself and others "Is this meeting necessary?" and behave accordingly.
When the discussions stray off the agenda quickly ask for that to be taken to a discussion afterwards between the parties that actually need to discuss.
Have a clear ending when done and let people escape who need to. Those that want to talk more at that point might be free to do so, I guess.
|
|
|
|
|
Most of this has already been said. But
1. Agenda - and do your best to stick too it.
2. Concise - Not just the agenda but the time. If you scheduled for an hour but only need 42 minutes. STop at 42 minutes.
3. People Management - Those that yell loudest need to be stifled(a bit) and those that are shy need to be encouraged. Get something from them. You invited them to hear their opinion. Get it. and DO NOT let them be overtalked by the loud ones.
To err is human to really elephant it up you need a computer
|
|
|
|
|
Stop having them...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Fewer. It is possible to meet once a week, look at what was done the previous week, what needs to be done the next week, and assign as makes sense.
With rare exception, have team members use ad-hoc communication (e.g. Teams) to communicate directly with only who needs to be involved.
Hire or train your people to act professionally, take ownership of their projects and assignments, take initiative, use their abilities, and just get it done. Don’t hire or keep those whose best effort is to follow a recipe book and unable to use deductive reasoning.
|
|
|
|
|
I literally had a conversation this morning where we hit all four popular things programmers say:
"It works for me"
"It worked a couple days ago"
"Huh"
"The JSON is bad"
|
|
|
|
|
Ah but you missed the important ones!
"Where's the coffee?"
"I need a faster machine"
"Pizza, anybody?"
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Can speak from recent experience that faster machines don't help. They just raise your expectations accordingly.
What? why is it taking 10 seconds? (this used to take 2 minutes) ARGGGGG
To err is human. Fortune favors the monsters.
|
|
|
|
|
But you can never go the other way…
This used to take 43 seconds, now it takes 44 seconds.
why?
Why?
WHY?
|
|
|
|
|
Oh I went the other way, but it cost me a pretty penny. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
"It's not that critical".
"There is a simple workaround".
|
|
|
|
|
"It must be a Dotfuscator error" 
|
|
|
|
|
Did you turn it off and back on again?
|
|
|
|
|
I generally hear a fair amount of cussing.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Why no that's not a bug that's an undocumented feature.
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
Just remember, a feature is a bug with seniority.
|
|
|
|
|
|
"Son of a....."
Stupid Javascript
Stupid Microsoft.
Na.... Stupid me, I fixed it.
|
|
|
|
|
"That's easy. I'll have it done today."
Jeremy Falcon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
The first 3 are spoken daily here!
