rsclient

FYI: At Microsoft, in Windows, the job might be PM or TPM, but the people aren't. A person is expected to be able to switch their focus from one to the other.

At least, that's what we PMs were told when Microsoft Windows rejiggered their PM roles

I literally had a dev manager say it to my face! "I guess you were a mediocre programmer or you wouldn't have become a PM"!

No, you aren't doing that kind of high-level design. For example, I was the PM for the "connect to Wi-Fi via a QR code" feature in Windows (you're welcome!). As PM, my job was to :

- demonstrate that this was "thing" people would want to do - demonstrate that it slotted into the existing feature set (the existing Windows camera already reads QR codes, so we just had to use their existing hoooks) - do a quick evaluation of the WIFI: protocol (which, BTW, sucks; it's one of the worst standards I've ever seen) - do an evaluation of the overall market (like, what do other operating systems do)

There was also some discussions with the Windows Wi-Fi team for how to store the connection data since it wasn't a perfect fit for the our existing connection store, plus a security evaluation. You won't do anything about caches or streaming except that they will naturally fall out of your spec.

You'll learn a ton about writing convincing documents, how to find users and partners, tracking schedules, and stuff

When I moved to Microsoft 15+ years ago, I went from being a developer (for 20+ years) to a PM. 9/10, would recommend. But also know that it's a very different skill set that you'll need to learn.

The simplest example of this: as a programmer, when your boss says to code a feature, you code it. But as a PM, you have to get a team to make it.

A PM's job is to figure out what the feature really is, and how complex or configurable it should be, and what the target audience is, and how you'll measure success. It also involves making sure that you feature works well with other features, and that your team is moving in the same direction as the rest of your company.

Be prepared, BTW, for the constant assumption that you became a PM because you couldn't hack it :-)

Among other problems: the variables est and estTime are both mis-named. The correct name for "the time in New York" is Eastern Time.

Depending on the time of year, Eastern Time will either match "Eastern Standard Time" or "Eastern Daylight Time". Forcing the time to always be "Eastern Standard Time" means that the times will be offset by an hour from the user's expectation about half of the year.

Arizona Exception: if you're in the boundaries of Arizona, you might need to correctly specify whether you mean a "Standard" time or a time which switches based on Daylight Savings. Different places in the boundaries of Arizona work differently.

What is it about computer people that they see a flood of open, free, engaging material about computers, and think, "I should put up an artificial road block so that fewer people read my writing".

Not high tech.

The blog post presents exactly one side of the issue, "what happens if a lawyer alleges child abuse knowing it to be untrue in order to extract a settlement". But it doesn't even hint that there's another side: what is one parent is actually engaged in child abuse, and the other parent is trying to protect their kids from it".

Incorrect. The maintainer isn't ignoring anything; they are considering the request and deliberately rejecting it because of their preferred style guide.

Things to not do include: randomly picking medicine "X", have it hyped up by a weird republican hype machine, and then bitterly complain when the unwarranted, evidence-free hype is denounced for being unwarranted and evidence free.

Phrased differently: Ivermectin was picked up by the republican hype machine, pretty much at random. The medical community, seeing a lot of absolute hucksters pitch a whacky treatment, fought back with mockery and derision. As it turns out, the medical community was right.

If you have 1024 people each of whom make 8 trades (and win/loss is 50/50), 4 of those thousand will succeed with every trade.

Given that, survivorship bias is 100% the right answer. If you have a "gut feel" that something else is going on, chances are your gut feel is wrong.

I used to program many different terminals, back when they were a thing.

A classic terminal only has a screen full of memory: it does have extra memory that would allow it to scroll backwards.

The ESC [ S command (CSI itself can only be used if you are sure the line to the terminal is 8-bit clean, and as a third-party developer, I could not guarantee that) scrolls the scrolling region. The scrolling region is either the entire screen, or it's just a couple of line at the bottom. A scrolling region is used so the use can have a scrolling place to type commands and Aldo have a non-scrolling area to display data.

Flagged as being obviously fraudulent.

I don't need to read any vaccine-denying, COVID-deny9ng crap.

Makes me wonder what the opposite point of view is. I've been in many set of ongoing meetings where the point of the meeting is to herd cats: us insiders know what the work is, but there's new incoming people who need to be brought up to speed, and there's a constant struggle to make sure that key people continuously recognize the priority of what we're doing.

We also all need to know what the current blockers are and whether they are being dealt with effectively and whether we need to drop to plan B.

All legal stuff is expensive. Source: was an expert witness, and made a nice sum.

SEC type stuff is guaranteed to be pricy because it's bound to be complicated, and require specialists.