|
Because they can?
Some people will use technology regardless of there being a simpler solution.
"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!
|
|
|
|
|
I used to sit at the desk next to my team leader. If he wanted something from me he would always send an email.
|
|
|
|
|
Probably not the reason in this particular instance, but Teams now will create a summary of what was said during a Teams call. Not 100% accurate, but still helpful to get all the note down from what was said....
|
|
|
|
|
and then Teams will delete it....
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
That seems to depend very much on the license you have. Looks like you need something like 'Teams Premium'... but I'm lost in the license jungle
|
|
|
|
|
On some level it is easier to collaborate sitting at your own desk. It allows everyone to see the primary screen but the ones not sharing can reference other things, sql tables, vs solutions, google, chatgpt. You can't really do that sharing one desk and pc.
That said, it does seem silly to not just lean back and ask your neighbor a question.
So I guess there are times when either one is more productive than the other.
P.S. Most of us are lazy and don't want to get up.
Jack of all trades, master of none, though often times better than master of one.
|
|
|
|
|
Agreed.
My teammate and I sit 1.3m apart and prefer to collaborate via screen share (no headsets, though. too much echo)
40+ year old eyeballs also are at play… and our furniture setup really does not work for two people unless you standup. (back to your lazy point)
|
|
|
|
|
Quote: 40+ year old eyeballs also are at play
Exactly because of this reason, I prefer to make a teams meeting (of course speaking directly) with my teammate sitting 2m from me and sharing the screens
|
|
|
|
|
More than ten years ago, had heard from a colleague that her mother at home, once called her on mobile, to find out where exactly she was at home; not a big house, but just too lazy to search around.
|
|
|
|
|
Before video conferencing apps with screen share, they still did it with phones, even when desks butted against each other!
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
|
Reminds me of when the company decided to switch to team approach to everything. Out manager called me to his offce to tell me he wanted me to be a team leader. I told him we didn't have any real teams. He asked what I meant?
I told him that real teams have cheerleaders, so could I interview cheerleaders and design their unifoms?
H decided that I was unsuitable as a team leader, whch was my whole point.
CQ de W5ALT
Walt Fair, Jr.PhD P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Dr.Walt Fair, PE wrote: team approach
I just had another one of these episodes today. After an hour on a remote, the teammate got their problem solved and I got further behind!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
My back, neck and eyes (I have to use 125% magnification) really favor doing things from my own desk rather than crowding aroung the single monitor of a coworker.
Add the fact that I can cross-reference with my code an my documentation when asked a question, trather than going back to my desk, seraching and returning (or yelling from one side of the office to the other)... yeah I do prefer teams meetings unless we are brainstorming or just aligning.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
Waxing cynical... it's pretty dang smart if you ask me.
The corpora-spyware definitely looks at teams activity for MSFT to sell your employer a metric on how hard you work (or don't).
|
|
|
|
|
Can you please suggest me a free VS tool which generates code documentation like that:
private int CalcBid(HandCards hand, int player)
|
|
|
|
|
|
Seems the community edition is free all others paid.
"Ten men in the country could buy the world and ten million can’t buy enough to eat." Will Rogers
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
Thank you.
Looks good but does not catch my return value?
public List<PlayingCard> GetHandTrumpCards(int TrumpCardID)
{
var lopc = new List<PlayingCard>();
foreach (PlayingCard card in Cards)
{
if ((int)card.CardType == TrumpCardID | (int)card.CardValue == 2 | (int)card.CardValue == 3)
{
lopc.Add(card);
}
}
return lopc;
}
|
|
|
|
|
Check what config options it has.
|
|
|
|
|
Probably not an options thing.
It just does not fill the return section.
The GhostDoc Comment editor shows:
Quote:
public List<playingcard> GetHandTrumpCards(
int TrumpCardID
)
Parameters
TrumpCardIDType: Int32
The trump card identifier.
Return Value
|
|
|
|
|
The return value is not uniquely named. A method may have several return statements, and the values may be expressions, possibly different expression for each of several returns.
The tool could of course create a list of all return statements. The same that you can obtain by a string search. I am not sure how useful that would be.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Do you say it works only for
return value;
|
|
|
|
|
I never used this tool, but OP presents an example where it doesn't catch his 'return lopc;', leaving only
in the 'documentation'.
I am one of those who likes to get out of here as soon as the job is done; I detest the 'single exit point' style that could increase the block nesting level by half a dozen or more. In other words: Some methods can have half a dozen or more return statements.
You might want to have them all listed above the method prototype; I think it messes it up. With several exits, the reason for leading to that exit is frequently far more essential than the exit value - especially if it is in the class of 'success' or 'failure'! Seeing four 'return failure' and two 'return success' in the documentation is not really informative. Seeing 'return lopc' makes very little sense until you have studied the actual code, seeing how lopc is built, but then you hardly need the documentation telling that lopc is returned!
If you use the template for filling in a brief explanation of what it takes to succeed, or in this case, what is the semantics of the subset of cards returned: Fine. I assume it applies to all the return statements, if there are several.
Also, those insisting on 'single exit point' must refrain from coding any exception that might propagate out of the method. That would be an exit not through that 'single exit point', so trusting that you can catch everything immediately before your single 'return' is fooling yourself.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|