|
Sander Rossel wrote: I have to use the Azure cloud at work
IMHO, that's not professional. I would rewrite that as "I am required to use the Azure cloud at work".
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: IMHO
Well, I'm glad it's a humble opinion, because it's incorrect.
I think almost everyone here is well aware that verbosity is not a sign of professionalism.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Verbosity depens on which verbs (and nouns, and adjectives) are used. If they are of "current buzzword" kind, they could signify "professionalism".
Noone would arrest you today for using the term "agile" in statements where it could just as well have been left out. Same with "open source". Same with a lot of buzzwords. They contribute nothing to the informtion value, except telling that the author knows which are the current buzzwords.
Also, an important aspect of professionalism is precision. If you tell that "I am required to" use a given tool, then there is an explicitly stated requirement. If you tell "I must" use some tool, it could be that anything else is too slow on given hardware, that your colleagues are not familiar with other tools, that alternatives are too expensive, ... it could be anything, maybe formal and maybe not. If there is a stated requirement (from the customer, or from the management) to use a given tool, then that is essential. You can't blur it, smear it out, by reducing it to a diffuse "must".
|
|
|
|
|
Well put. 
/ravi
|
|
|
|
|
If you say "I have to use whatever", then it is clear that it is imposed on you by a higher power.
Verbosity for the sake of it is not a sign of professionalism; it's a sign of self-importance.
Clear, precise language is professional; trying to sound cool or important isn't.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I have to use the Azure cloud at work
I am required to use the Azure cloud at work
To me, both suggest a sense of disgust in being made/forced to use Azure against one's wishes. 
Whereas "...we're using Azure cloud at work" is as neutral a statement as can be, IMNSHO...but the tone of voice used when saying this out loud would indicate what you think of that situation. That might be lost when written down, but that could be a good thing...
|
|
|
|
|
dandy72 wrote: To me, both suggest a sense of disgust in being made/forced to use Azure against one's wishes.
/ravi
|
|
|
|
|
|
When I read could of instead of could've, I relegate the writer to moron status, which is then hard for them to overcome.
|
|
|
|
|
I turn the grammar checker off in Word. Its recommendations are worthless, especially since they are inappropriate for most of the technical documentation I write.
I also tend to disable the spell check, since most of the time I'm correct and it's not. It also tends to false-positive far too many things - filenames, proper names of all kinds, program symbols, and so on.
Software Zen: delete this;
|
|
|
|
|
Have you checked which version of English is driving the spelling/grammar checkers? If you're right to be blaming it on a US vs UK difference I'm wondering if you ended up with the American rules turned on by mistake. If so:
Options - Language - Office authoring languages and proofing. Change from English (United States) to English (United Kingdom).
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
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
There are other considerations whereby, aside for nuance of source (internal vs. external) they are just not interchangeable.
- I do not have to go to work vs. I do not must go to work ?
- What about a context such as "Must I?" vs. "Do I have to?", both of which are suggesting an external source.
Other breakage of these rules could be constructed but I prefer, if at all possible, writing as I speak (excessive commas and all).
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I admit that I haven't read through all of the replies so if someone else has made the same comment as I am about to make, then I apologise.
Look at almost any of the RFC for the Internet standards (sorry, memory has gone it's something like IETF). They start with a section about the use of words like SHOULD, CAN and MUST. It is a good staring point.
Re your samples
"I have to use the Azure cloud at work" , I agree; but for
"I must work out more often" I'd have suggested
"I ought to work out more often" or
"I should work out more often" to indicate that it is something that the general consensus is that there is pressure on you to do it but you can refuse.
|
|
|
|
|
There is a reason why these terms are explicitly defined (in its own RFC, if my memory is right): The terms can be understood in different ways, but in this context, this RFC, they have this meaning: ...
Sort of a "YMMV" declaration.
|
|
|
|
|
|
I have Word Professional Plus 2016. I don't know if these instructions will be similar or not for your version.
To use English (United Kingdom) instead of English (United States)
1) Open Word.
2) Click on File tab.
3) Select Options (bottom option on left menu bar).
4) Select Language (left menu bar).
5) Use drop-down list to "add additional editing language" and select "English (United Kingdom)".
6) Click Add.
7) In the Choose Editing Languages group, select English (United States).
8) Click Remove.
9) Click OK to exit.
To stop having only this particular rule checked:
1) I can't find it.
2) Just turn off grammar checking instead 
Bond
Keep all things a simple as possible, but no simpler. -said someone, somewhere
|
|
|
|
|
So I was complaining a while back that VS2019 didn't automatically open the "Output" window when I start a build, even with the "Show Output When Build Starts" option checked.
Well, they finally fixed that.
[^]
Of course, the update was 1.27GB or something like that, hahaha.
|
|
|
|
|
|
Marc Clifton wrote: Of course, the update was 1.27GB or something like that, hahaha.
Microsoft fixed an issue you were experiencing, perhaps you should be a little less critical and enjoy this once in a lifetime moment 
|
|
|
|
|
Sander Rossel wrote: perhaps you should be a little less critical and enjoy this once in a lifetime moment
The thought did cross my mind. 
|
|
|
|
|
Marc Clifton wrote: Sander Rossel wrote: perhaps you should be a little less critical and enjoy this once in a lifetime moment
The thought did cross my mind.
Yeah 'fixed' something, but can see their heart isn't in it: no new icons!
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
I just downloaded it on Monday so already have the fix. I waited because I knew the initial release would be buggy.
|
|
|
|
|
ugh.
What I don't like is it switches to the error panel whenever anything important happens, but that doesn't show you output from pre-build steps very well so i find myself constantly clicking back to output after compile.
Real programmers use butterflies
|
|
|
|
|
I hate the error panel. Problems are listed in more-or-less random order. At least with the Output window I have a chance of identifying the real problem.
Software Zen: delete this;
|
|
|
|
|
But the output in the Error List view is sortable. Just click on one of the column headers and it will sort into the order of data in the specified column. I've only goy VS2015 and VS2017; so it might be something that is no longer available in VS2019. If they have dropped it, remember the MS design philosophy "Redmond knows best".
Of course, my coding is always perfect, so the Error List is always empty 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
