|
That does not exclude each other - it is easy to have both of them.
But: how is the fifth day wasted?
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
🤔
💡
🍻🍷🥃
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
|
|
|
|
|
|
Quote: Technical debt causes bugs and outages, and slows down the pace of development, 60% of engineers said in Stepsize’s report. This results in productivity loss because the engineers are spending more time dealing with issues related to technical debt and not on issues related to development.
Ironically, constantly upgrading to the latest version or worse, replacing the long-in-the-fang technology with the newfangled tech has the same effect or more so.
|
|
|
|
|
It's actually way less than I expected 
|
|
|
|
|
And how much more wasted on following the "cool kids" to the newest hype? Is const correctness still a war-winning thing?
|
|
|
|
|
"Technical debt" is impossible to avoid without a team so large that maintaining a team of sufficient size crushes a project, and then everybody ends up out of work, and the project dies.
0) Write some code with the latest tools.
1) 1 to 2 years later, release the product.
2) You have technical debt, because you can't just willy-nilly keep introdicing new versions of base framework code/libraries without fully regression testing everything you've done up to that point.
Even modular re-usable code can't help you.
Your only possible successful strategy is to make the executable nothing more than a launcher with ALL of the code inside discrete DLLs. That way, you can upgrade the executable, and follow up with upgrading the various DLLs when you have the opportunity. The problem here is that your STILL have technical debt.
It can't be avoided.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I worked on an ever-evolving product that ran 24/7. I finally arranged to have a tiny stub/launcher that never changed and everything else in multiple DLLs that were dynamically loaded as needed and some of them could even be switched out while the program was running. With care, I could add new features, change existing ones and fix bugs by just sending the customer a floppy disk (or sometimes two) with the upgrades to be loaded into a special directory along with new release notes. All the customers could request new features or make suggestions and, if it was an improvement then all the customers would get it. They all loved it because it never stopped. One customer sent me a screen shot from the status/splash screen the showed the program had been running continuously for nearly four years without stoppage - of course, this was running on a closed network (no internet) under Windows 4 when there weren't breaking O/S updates every five minutes!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
But the DLs can't use a newer version of .Net than the exe that uses them. That's the rub. You can't update any of the assemblies until the parent exe has been updated. If there's nothing in the parent exe, regression testing is (theoretically) minimized, and can be mitigated to just assemblies that are updated as they are updated.
However, the act of developing code introduces technical debt.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
There was no .NET back then (in the good ol' days). 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Google’s Android app store is the subject of an antitrust lawsuit brought by 36 states and Washington, D.C. on Wednesday — the latest installment in the ongoing showdown between tech giants and the regulators that seek to bring them to heel. I hope they like Bing, because otherwise they won't be able to search anymore
|
|
|
|
|
Kent Sharkey wrote: and the regulators that seek to bring them to heel.
Good luck with that...
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.
|
|
|
|
|
Last month, Microsoft officially announced Windows 11, which will be offered as a free upgrade to Windows 10 users. I'm sure they're all ready and willing to jump right on that
|
|
|
|
|
Will it run in windows 7 pcs?
I have read several places complaining about the min. requirements in hardware...
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.
|
|
|
|
|
Very true - Intel 8th gen and later[^], and whatever the equivalent for AMD.
Plus I imagine most of the Win7 machines out there don't have a TPM 2.0 chip.
I think the main upgrade path for most is a new machine.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: I think the main upgrade path for most is a new machine.
only IF you want to update.
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.
|
|
|
|
|
This might be a way to keep a forced upgrade at bay. Just keep using a machine that can't support Weleven.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
If you're a Win7 diehard and installed it on new hardware it'll work. OTOH if you're that much of a W7 diehard that you've ignored 8 and 10 are you really going to give a single ![Elephant | [mastadon]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/elephant.gif) about W11? 
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
|
|
|
|
|
Nope!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I am not a diehard because of windows 7, I just don't like to be forced to buy new hardware while everything was working perfectly on my machine.
I definitively ignored win 8 and 8.1 on purpose, because I didn't like it.
I had Win10 for a while in the old PC but it annoyed me so much that I went back to 7.
But although it still works well, there have been a couple of times where I didn't like some reactions while working... So I have bought new hardware.
Logically win 7 can't manage it properly and I am not really willing to invest a huge amount of time trying to tweak things so that it works properly.
I am running Win 10 in the new PC. I will have a fresh start, set everything up and do an image. Once Win 11 gets to SP1 I might consider checking it up, before... I don't think so.
I don't need to have the newest shiny hardware or software just for the sick of it. But once I decide to buy / do something I try to get something actual and with future perspective.
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.
|
|
|
|
|
Researchers have bypassed Microsoft's emergency patch for the PrintNightmare vulnerability to achieve remote code execution and local privilege escalation with the official fix installed. As long as it doesn't break anything
A footnote to @Ravi-Bhavnani's item below
|
|
|
|
|
Hey, cut the criticism; their engineers are working hard at making rounded corners. Get your priorities straight!
|
|
|
|
|
Yeah, well.. As soon as they master the art of the smoothly cut corner - their updates won't keep failing.
|
|
|
|
|
Run > services.msc > Print Spooler > Properties > Stop
> Startup Type > Manual
Easiest way I know of to disable it while still letting you start it up when you actually need it.
|
|
|
|
|
Probably couldn’t hurt to set it to run as an account with few perms as well (IMO)
TTFN - Kent
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
