|
I have developed arthritis in both hands, and have now gotten dupuytrens contracture badly in both hands.
Slows typing and mouse work down considerably, and causes multiple keyboard key strokes in the the left hand
Thar's only two possibilities: Thar is life out there in the universe which is smarter than we are, or we're the most intelligent life in the universe. Either way, it's a mighty sobering thought. (Porkypine - via Walt Kelly)
|
|
|
|
|
I had surgery for dupuytrens 10 or 15 years ago. Followed by massive physio - an hour a day for 6 weeks or so, then twice a week for another 3 months.
Well worth it! My fingers are still nimble enough for the amount of typing and fine manual work I do, but I am often slowed down by a brain-finger disconnect that doesn't type what I intend. It started with transpositions like ...ino for ...ion, now does some quite off-the-wall substitutions.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
You seemed to indicate one particular "mouse finger". I think I use left click most. That said, it is possible to switch buttons on a mouse (configuration).
Now, a touch screen might also work: it should eliminate any number of mouse clicks (with screen taps, slides, drags)
"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
|
|
|
|
|
Thanks. I forgot the switch thing. I will give it a try.
ed
|
|
|
|
|
Touch and click aren't always equivelant - there are (even MS) apps that just don't work well at all with a touch screen.
Which on a Microsoft App, on a Microsoft Surface, on a Microsoft OS is ... somewhat annoying ...
Can never remember which apps though until I try to use them. Which annoys me even more!
"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!
|
|
|
|
|
That's a design issue. My UWP apps are written with touch in mind; they run on tablets and desk tops. I prefer the tablet / touch experience in this case. Even created my own virtual keyboard that can be split, etc. and prefer it over the "built-in" one (for / in my apps).
"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
|
|
|
|
|
Points to technical drawing instrument (7)
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
DerekT-P wrote: 'nuff said?
Indeed
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
When did RULER have 7 letters?
"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 missed that part
(paper) Trimmer
|
|
|
|
|
... and the "we have a winner" bit a couple of hours ago?
"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!
|
|
|
|
|
well I'm not interested in winning, just I wanna spread a little bit of variety in there ;)
|
|
|
|
|
so I guess a typically micro managing manager that typically always adds tons of comment on reviews...
I am particularly stricken (so far, only read 4 comments so far) by the contrast between 2 comments:
- comment 1: add a private qualifier, normal comment.
- whereas comment 2, line return after curly brace (instead of singe line"
{ a.Dispose(); } " is a mandatory task?!
🤔
|
|
|
|
|
I dunno.
I'd need to see that single line curly brace in context before I get on my high horse and enter a religious war about code style...
Who am I kidding! Of course I don't need context or even an excuse! Curly brackets can only be on a single line as part of a get/set pair of a property. Anything else is an affront to the Gods.
cheers
Chris Maunder
|
|
|
|
|
I allow myself the occasional single line return:
if ( ok ) { return; }
"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
|
|
|
|
|
If I'm feeling particularly daring, I'll even omit the curly brackets.
if (ok) return;
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
No ... did consider it; but that leads to the else.
"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
|
|
|
|
|
Replace it with
=> a.Dispose(); out of spite if it's a function. Especially if you know that function will need to be longer in the future
|
|
|
|
|
it's a one short statement finally block the reviewer wanted to multiline.
have to keep the curly brace for the finally. beside, dispose was an example, it's not dispose, otherwise I would use using
|
|
|
|
|
I am happy we have analyzers for our new code - now just need to get rid of all the old crap.
Stuff like this never hits our code review for new code as the analyzers would flag it as a warning and help the developer fix it. And if it is checked in anyways the CI build will reject it as it is doing a release build set to treat warnings as errors.
I am not saying we are doing perfect code reviews (spend too little time on it) but at least the time we do spend is on the naming, structure, and overall logic of the code - not wasting time on formatting that can be done by tools already available for free.
|
|
|
|
|
|
While I'm not convinced that level of OCD about code formatting is valuable, if done it definitely should be automated and not a human time sink.
Edit: To include autoformat on save by the teams default editor.
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
|
|
|
|
|
Maybe VS can apply corrections on save, but I would personally despise that so never gone looking for it. If needed I just bulk resolve them throughout the code as I am done with the "getting it working" part.
And as the analyzers are simply nuget packages there are no requirements all team members have specific plugins or settings that needs to be coordinated - they do not even need to use the same IDE.
And I must say after working on a code base with formatting kept consistent by analyzers it is nice. Code architecture is of course way more important... which is exactly why the formatting should be left to tools so reviewers are concentrating on the important things instead of just pointing out trivialities like newlines etc.
Sure the tools can definitely still be improved... but for me they have passed the point where they contribute more than they get in the way.
|
|
|
|