Re: Does it really matter..
That was more about being able to sign an NDA with MS whil4e working at Google. Shortly later a away around that was found and the MVC award continued.
> guy that answered all the .Net questions
Not all, but a lot.
532 publicly visible posts • joined 19 May 2012
> This sounds like a feature created by an overly eager intern.
No. Because this has a completely reasonable use case. A page is loading (eg. for images below the fold) when the user navigates to another page; at this point those resouces outstanding for the first page will not be needed.
Just opening lots of HTTP/1 sockets has its own problems, and cancellations by the client (close the socket) allowed similar DDOS attacks. The difference is the HTTP/1 attacks have had a couple of decades in which defences and mitigations have been built up.
And if you look at Process Explorer (SysInternals) you'll see a different number again.
Short version: there are some choices made about what counts as a process's CPU time (eg. how Windows uses the currently executing thread's stack for interrupt handlers).
Also Task Manager rounds to integers, so a lot of cases where a thread uses (say) 0.1% CPU in an interval round to zero, but across 10 threads that adds up.
> TLDR - I couldn't get to the end of the article.
Read first couple of paragraphs. Lack of capitalisation and grammar was a barrier. But the tone coming over as if written by someone who has found, and wants to publicise, their latest conspiracy means it is not worth my time.
If you want to use an article to support your position then reference something that is well written in something close to proper English and makes its points calmly,
Addt6ional (that I remembered later: it has been a while since this was operationally significant).
On 32bit Windows the large address aware flag was not sufficient to get the additional user mode address space (it was sufficient on 64bit windows). 32bit Windows also required a boot.ini flag to tell the kernel to use only 1GB of address space.
This restriction on the kernel could cause problems itself (including performance) so should be thoroughly tested first.
> An individual application would only get access to 3GB of that - unless compiled with a Large Address Aware linker switch to indicate that they could cope with the full address space.
Correction: 2GB unless compiled with the large address aware flag, which got you as much as the OS would provide to a 32bit process. Which was 3GB on 32but OSs. When running on a 64bit OS an executable compiled with the large address aware flag will get 4GB.
The difference is because the top half (normally) or top 1GB of the process address space is overlaid with the kernel's address space on 32bit versions of Windows. 64bit Windows (which became generally available with Server 2003: XP 64bit being a variation of 2003 and causing confusion with service pack numbers following 2003 rather than XP 32bit).
Ie. to maximise the available address space for 32bit processes you need a 64bit OS, rather than more RAM.
For that, everybody must be in the SAME office.
(And that means any business leaders that splits teams over offices making any claims about being in the office for easy communications are at the normal level of "business leaders".)
> It's reasonable to assume that heating/cooling a home is less efficient per person than heating/cooling an office.
Visit more offices. The number with poorly fitting windows letting in drafts... or windows open because no-one can switch off the heating....
I suspect most offices are pretty poor.
What would you suggest instead?
If you have a crash that is 1. only in production (a re-create a production isn't necessarily a re-create in test) , 2. existing diagnostics (logs etc.) don't provide any information beyond it crashed then what else to do?
> We should move one monitoring systems to a different DC
No, you should be running in more than one DC, or at least more than one AZ in the DC.
A different DC will have its own set of vulnerabilities to an outage. As long as you are in a single AZ you will go down with that AZ.
On a more ephemeral note (break out the incense) the software vendor also claimed the font had a more "humanist" touch as it had to "induce trust."
Missed understanding error. "Humanist" typefaces have an oblique axis to the letter forms (eg. the crossbar in an "e" is not horizontal and aligns with the weight variation in the stokes).
(I'll get my coat: it has The Elements of Typographic Style in the pocket.)
This is common across a lot of apps (including browsers and Visual Studio).
Other apps do something of their own (eg. VS Code does rectangle select).
As this is, for Windows, the most common function of the middle button it is off the article completely fails to mention it.
By that metric I've already doomed myself for the year...
One PR: +45k LoC and -5.5MLoC!
Reduced the build time in our CI agent from >60min (and often timing out) to <2min. But for the "LoC" only metrics is never going to look good.
(I hate tooling the accumulates more and more generated code that will never be run...).
> The question is can you actually set up a Github account without providing a phone number even though its not necessary for 2fa?
I'm pretty sure I've never given GitHub my phone number, and do have 2FA set up (TOTP).
Yes, you could use a burner phone, but you would need to configure the account to use that phone (or transfer TOTP app settings to that phone)
I do have Chrome installed. Mostly for testing/validation.
My web browsing I do in Vivaldi (with lots of customisation).
Just because you need a tool for supporting others does not mean you are restricted to that tool. After all a "pro" understands the difference between optimising my workflows and helping someone else.,
Where is the option to upvote multiple times?
This 150%:.If the org is over multiple locations you're not meeting face to face anyway. So the one possible benefit of being in the office is lost,
(Since first lock down, now averaging well under 1 day per year in office and I continue to completely not miss it.)
Definition of legal tender is the some (or at least close enough).
Which involves payment of a debt, not just any payment. Eg. doesn't apply when getting a sarnie at M&S for lunch.
It would apply to settling a restaurant bill however. And it is also only applies when providing the exact payment (can't ask for change).
(At the danger of opening the can of worms...)
(which, as many people don't realise, are also promissory notes)
This depends on the jurisdiction and issurer.
Eg. Scottish banknotes are promissory notes (which is part of why they are not legal tender anywhere), whereas Bank of England banknotes are not (and are legal tender outside Scotland).
 This has little practical meaning, "legal tender" is only meaningful in some narrow classes of debt payment.
 There are no bank notes that are legal tender in Scotland.
> In most cases the cause of this type of outage is caused managerial incompetance.
Largely lead by political incompetence.
"Cut 33% of managers" made positive headlines, but they cut too many useful ones. Since then productivity - based on positive patient outcomes - per staff member has fallen steadily. Basically there is no ability to improve the way things are done (font line staff are too busy being frontline staff to fix things).
And then the massive drop in capital expenditure meant there is no budget for anything than "what's the cheapest" despite that being the more expensive option in the medium to long term.
Be glad you not using Slack as well then.
Current memory use: Teams 255MB & Slack is 325MB.
Given Slack's more limited functionality it seems like Teams is not the worst.
IMHO: Teams is OK at everything. While Zoom maybe good for video conf it is not that much better that it is worth switching tools; Same for Slack and chat. They are all tools I use, whether I like them or not they do generally work (Teams is not really any worse overall in this regard).
What is really annoying is that professionals in IT get so attached to things that are tools simply because that is what they are used to, and are unwilling to be objective in that "I like" is not relevant. You use the tools you need to use to solve the problem in an effective way.
Equally, of course, any admin who insists that it is kept inhouse, despite no data centre (small business) or offsite secondary (small business), that they'll cover whenever (24x7) should anything happen.
Not every organisation has the resources to run systems with that kind of reliability the business needs.
If Rackspace has had this service for 10 years, and this is the first outage that would be better that 99.5% availability. I suspect it goes back longer than that. Can you match that with a repurposed desktop machine under a desk in an office (or maybe there is a cupboard if you're really lucky).
Yes, many commentators here have the luxury of being part of a significant IT organisation, but that is a minority of organisations.
Only those who think "agile means no design" think "code is self commenting": they've never worked on a system with some "proper" business requirements where the only sensible reaction is "WTF", but you still have the implement them.
To quote Refactoring:
Don’t worry, we aren’t saying that people shouldn’t write comments. In our olfactory analogy, comments aren’t a bad smell; indeed they are a sweet smell. The reason we mention comments here is that comments are often used as a deodorant. It’s surprising how often you look at thickly commented code and notice that the comments are there because the code is bad.
And then expands on this, including that extracting the code into multiple functions, even if they need long names (naming sections of code really helps, languages with local functions are particularly useful here), significantly reduces – but does not eliminate – the need for comments.
It is seems to be almost universally missed when USB-PD discussions come up that the engineers who put together the specifications might have thought about these things.
Eg. USB-PD does not use 5V for power (beyond the lowest powers). In the latest spec it can be up to 48V.
Of course no-name cheap cables might not be built to spec, but that is not a USB specification problem, that is a problem with people who just get the cheapest and then moan about quality.
and change them periodically to protect the database server from brute force attacks and dictionary attacks, which any IT pro worth their name will have been doing already
This goes against best practice, and only helps if your password later appears in password lists: which is won't if it was good enough in the first place (20+ chards from random password generator) and not reuse.
Just repeating this bad advice makes me question the source.
Indeed. Use VS Code to write markdown, it includes preview support... and extensions can extend that. Which, while a similar download, has a lot of other abilities.
On which topic, from the article
It uses Markdown, which is a sort of lowest-common-denominator markup language.
Assuming a decent Markdown variant (ie. Common Mark compatible) and a couple of extensions (TeX support, and diagrams, via Mermain.js) you've got a tool that can produce better results than most work processors.
All of these thermal power cycles are theoretically 100% efficient, i
No they're not. All heat engines are have an upper efficiency limit of (derived from second law of thermodynamics)
where Tin is the input temperature and Tout is the output temperature, both in absolute units.
this is why power stations need cooling towers: to reduce Tout and thus give a big ration (Tin tends to be limited by available materials: superheated liquids tend to be highly corrosive).
> Most people
Be careful generalising. My experience is most people do a full replacement every 4+ years (with maybe a GPB replacement between). My previous experience of such small upgrades has been they don't offer enough of a boost to be worth the hassle.
Simpler upgrades (more RAM, updating GPU) still would cost more than your price range (certainly anything in the last decade) to be sufficient to not have done when the machine was built.
Better to build well now with the assumption of a new build after a good lifetime taking the best balance of performance and price for new major components now with the expectation of a good 5+ years usage.