:thumbsup: Protecting developers by managing up and out instead of down is the hallmark of the best managers. It sounds like yours are fortunate. Robust Services Core | Software Techniques for Lemmings | Articles The fox knows many things, but the hedgehog knows one big thing.

You prototype with a trivial example; when that that works, you throw the kitchen sink at it; not before. "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

Kent Sharkey wrote: "actionable units of productivity" must actually mean something to you. Perhaps it is only understandable after mastering CEOing in an 8 year college setting. Our Forgotten Astronomy | Object Oriented Programming with C++

20 years ago I contracted at a company that used "the office package that everyone legendarily hates" - anyway, so they had all of these user forums for all of their different company supported groups. Now mind you, fb is fb to mine data. Microsoft wants to be able to mine what companies are doing. You think there is some other reason why they want companies to go to the cloud and 365? Hmm. Anyway, after announcement after announcement of awards to assorted groups: single moms, mixed this, mixed that. It doesn't really matter. We're talking 100s of thousands of dollars - some engineer commented, "Can we get some money for training and research?" and was told, "Get on the train or find another place...." Company does not exist any more. Microsoft made it's money with the OS and Office. I live in the embedded world and we are on Windows embedded. Not for much longer. FML. 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.

Yeah, my quote was going to be... "Researchers determine the sky is blue & grass is green." Headline: IT workers are spending majority of their time on tasks that don’t contribute to key business outcomes So it has always been, so it will always be. :laugh: Oh, I'm kidding, of course. Management will fix it. :laugh: :laugh: :laugh: :laugh: :laugh:

Kent Sharkey wrote: Satisfied employees perform better? Mind blown. Looking at how things really are in many places... it is like: common sense, sadly not that common. M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

Use Zoom instead? Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius

Hi, it's very cool that so many young, promising people are interested in this topic. I will tell you from my experience that you should always be interested in such questions from your mentors or supervisors. But if there is no one else to ask my advice to you, turn to professionals like these ms project assignments. While I was studying and gaining this knowledge, I used their services many times, it helped a lot in my professional development.

A simpler method is simply don't open hundreds of tabs. (I type this while I have a tab open to every link in today's CodeProject email. :))

. "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

What's worse? Ignorance or Indifference? I don't know and I don't care... :rolleyes: M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

It doesn't really sound like you're disagreeing, just explaining things differently, or thinking about other documentation. We're developers and I assume the documentation Richard is referring to is documentation for us, developers. I'm also assuming he's not talking about comments in code, because he'd call them comments and not documentation. Mircea Neacsu wrote: I think the OP was talking about design documentation, or the lack of thereof. It should explain the whys and tell little about the hows. Presumably the purpose of the system and the design don't change that often as to make it constantly obsolete. That would be my following two points: - How does this application fit in the landscape (is it stand-alone, does it depend on other services, do other services depend on this one)? - Does it depend on any in-house packages and if yes, where can I find those packages and how do I update them? Those two points would also answer Richard's question of "[...] how it works, how the data flows through the different layers and what components do what." You're a bit more detailed, I think, wanting to know how an application is build in terms of interfaces, base classes, etc. which could be a useful addition if this isn't directly clear from the code. For example: "For process X we're using IImporters and every client has their own implementation of IImporter which can be found in ... and depends on ... and is chosen/instantiated as follows ..." Overall, I'm not very concerned with the why of the system. It's here and people use it for one reason or another, that's a given. Knowing globally what it does can help in finding and debugging functionality, but it's not a requirement. That changes when you're tasked with thinking about how to make the program better and more useful for your customers, but that's not usually the task of a programmer and I wouldn't want to find it in the documentation that's supposed to help me run, debug and change a system. Mircea Neacsu wrote: What you seem to refer to, is what I call "user manual": how to get the code, where are the passwords and so on. These are the nitty-gritty details that are very helpful but don't explain why the system was designed in a certain way nor how it was implemented. Depends on your point of view. If a user asks for a user manual, they don't want the code and they're not even allowed to secrets. A software user manual, to

Thank you so much for your answer.. lmoelleb wrote: The first suspicious thing I see is you call an async method SendMsgAsync() without waiting for it. This means your Main method can execute the code following myprog.sendMsg() before the message is put on the network. You was right, I was able to make it run by putting a Thread.Sleep(5000) after myprog.sendMsg(),is not optimal but it work for now. lmoelleb wrote: You should make your Main async as well and await the async calls - then it will not terminate before completion (and you will also see any errors). You might also when googling find advise to call .Result or .Wait. Those are excellent advise for people who like to debug why there software occasionally hangs after they make a completely unrelated change. Sure you can use them if you know how it really works under the hood - but that is not a good topic for a beginner. I gonna check this. Thank you so much for your help!

Where do you put docs and stuff? On the Q drive, under their respective folders. Ewww. Okay, we put them on our IDP (which happens to be the Q drive)