|
Taking advantage of a short break when I knew that my computer wouldn't be busy, I manually started an installation of Windows 10, Build 1803, also referred to as the Redstone 4 or Spring 2018 Creators Update. The result, Redstone Reverted, illustrates the discoveries I've made in my first day using the upgraded OS. I am both astonished and disappointed that the installation program for such a mature operating system still exhibits such amateurish behaviors as reverting carefully crafted user settings that should be in the user hive of the Windows Registry, and off limits to operating system upgrade programs.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Hmmmm
Try closing your left eye and then perform a "Right-Blink" to see the new context menu. You should check if the missing menu items were moved there.
Your missing out on all the good stuff! Check out the new Eye Control Text-To-Speech[^].
Btw, take off your glasses, it's hard for Cortana to read your eyes with those things on.
Best Wishes,
-David Delaune
|
|
|
|
|
Though I marked the message as a rant, the scope of said rant is quite limited. The Microsoft upgrade groups needs to write robust, customer focused installation scripts that respect users' carefully crafted settings. Windows is 33 years old; it's past time they grew up.
On the whole, I am happy so far with Redstone, and I never had any of the problems with its immediate predecessor (Fall Creators Update) that drew so much attention from the trade press.
I thought you might be joking about the Eye-Control Text-To-Speech, but I see that it's a thing. Unfortunately, a quirk in the way my eyes work, for which the medical term is [^]Nystagmus, would almost certainly render such technology anti-productive for me. I have also confirmed that a "right-blink" produces exactly the same context menu in my installation.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Just came home from a live event where a Canadian gentleman was playing with his rhythm group.
It was ultimate!
Felt like I was on cloud number nine!
No matter how many times I see him performing it always gets better and better.
|
|
|
|
|
You didn't get his name or his group's name?
|
|
|
|
|
Marc Clifton wrote: You didn't get his name or his group's name?
Shhh....it's a secret.
|
|
|
|
|
In that noise? No chance. He did mention the guitarist's name a few times though. Keith something...
|
|
|
|
|
I dont rate Bieber that highly.
|
|
|
|
|
Seen him quite a lot. It always feels like I'm back in the Summer, sometime just before 1970.
This space for rent
|
|
|
|
|
Yep, the same guy. For some reason he's just like wine, gets better every year...
|
|
|
|
|
How to limit code bloat from patterns? You want to read a connection string from your file, but you end up with two interfaces, two concrete implementations, one template, and one native driver dependency? If we make a plan and put our money and resources together, couldn't we just forbid patterns, and lock up Martin Fowler?
|
|
|
|
|
KISS - patterns are useful but not always practical.
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
Maybe you will like Anti-Patterns better
|
|
|
|
|
This is what I hate about patterns: because it worked in "Situation A", it's easy to assume it will work in "Situation B"; and with a bit of hammering on the sharp corners, it does. So it starts to be seen as a "universal solution" and forced to work for "Situation C", and D, and ... even when it patently is ridiculous because it works. Very shortly, it becomes a "software religion" and any criticism of it is tantamount to heresy in the eyes of the faithful. A bit like owning a new iPhone ...
This isn't specific to patterns, or even new: if you have a big enough hammer, everything looks like a nail.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If you have a big enough hammer, everything IS a nail.
|
|
|
|
|
ventureaaron wrote: If you have a big enough hammer, everything IS a nail.
My new response in design meetings, from now on! Where would you like your case of beer shipped?
vuolsi così colà dove si puote
ciò che si vuole, e più non dimandare
--The answer to Minos and any question of "Why are we doing it this way?"
|
|
|
|
|
Keep it. Sounds like you may need it for your design meetings.
|
|
|
|
|
|
Cue Michael Jackson.
Software Zen: delete this;
|
|
|
|
|
Don't add anything that doesn't add value; and no, the fact that a pattern exist does not mean it must be applied in every situation.
Any extra code adds complexity and hence costs. Keep it to a minimum.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
|
Patterns were created as compensation for a language (Java) that cripples you from doing things intelligently. Then patterns were used to compensate for stupid programmers so they could at least write intelligent boiler plate code. But that mostly fails. Then patterns were glommed onto by the likes of Microsoft in their Enterprise.Patterns fiasco, and you know how dead and ancient that is.
So, here's the mantra for 2018: throw out your old patterns and simply do what you know is right.
|
|
|
|
|
Switch to C++. The C++ community doesn't do patterns to any significant extent.
|
|
|
|
|
Why stop with Martin Fowler? Why not lock up the whole Gang of Four, in separate prisons, for the rest of their natural lives.
I use patterns when they are appropriate, but I've never spent much time deciding which pattern to apply to a given situation. This is not at all the same as avoidance of wheel reinvention. Whenever possible, I assemble new projects from existing tested library routines and modules. Some of these may happen to implement a pattern, but I'm not slavish about that. For example, I have several C# class libraries that contain classes that implement the Singleton pattern, but they are special cases that truly merit such treatment.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Tomaž Štih wrote: lock up Martin Fowler?
yes
|
|
|
|