HN user
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.
Which, per the article, you can appeal to a real judge.
From the article: yes, you do. Compare the SEC's actions to a simple traffic ticket: a police officer gives you a ticket with a pre-set fine. This is like an SEC officer giving you a fine for some infraction. You can argue it out for a bit if you like, just like you can argue a ticket with the desk Sargeant (not that people do that). Age you do that, you can take it to court.
The only difference is that the experts at the SEC that you have to go through are called "administrative judges". It's kind of like a cop being called an "officer" even though they aren't like an armed forces officer at all.
For everyone who's hated bosses that determine success by number of lines of code: the "damning" part here is that the teams don't have good metrics for success. There's not a hint from the article that the teams aren't effective or that they are in any wasteful.
Not even remotely a technical site; is just an ad for a service, and doesn't belong on HN.
I live in a town that has some decent hills between my house and downtown. With an ebike, it's easy to and from downtown. But with an ordinary bike I would rarely get into downtown
Uninformed bullshit session that's not really tech related. And no, we're not about to have a nuclear war with China!
Wow, the presenter really likes the "dump a bazillion facts" style of punditry, even when the reality is more nuanced. As a single example, at 11:36, the presenter talks about lockdowns and compares the US "lockdown" (1 year) against the Chinese one (3+ years) and also compares the covid payouts (6k/person US, $500/person China). Not mentioned, though, is that China had a sort of "split" lockdown: if your city had no covid, you just got plenty of tests but no particular restrictions. If your city was locked down, you had to stay in place, but would be fed. Also not mentioned is that the US also had a multi-level covid relief: we paid companies to continue to hire people (my own company did that, paying our support staff 100% of their regular earnings even though they mostly weren't coming in), making the actual compares more difficult. And of course, the cost of living in China is substantially less than America.
So, lots of rambling bullshit, ending up with a pretty lame conclusion.
The source for the graph is just "NASA", without even a hint of a proper attribute. The link to the sciencedirect paper is a nifty and super geeky description of a continuous effort to extract more and better information from one of the many, many datasets NASA has on wildfires.
Without a proper citation, climate change denier is denying climate change in a way that doesn't have enough data to challenge. Given that Bjorn is supposed to be an actual scientist, they should know better.
Great use of "quotes". That will "convince" me for sure!
Snarky summery: "If me and my fellow "skeptics" keep adding "quote marks" and arguing about everything long enough, surely this time people will listen to us complain about every single aspect of the Covid response."
Weirdly, it doesn't handle unique placenames. So if I say my mom is from Huntertown, where do people think she's from?
No answer, and it won't even try. That's because there's only one Huntertown.
Raspberry PI 4 price: $35 Orange PI 5 price: lots more.
Is it ever news that a more expensive computer is also more powerful?
My own take: I only see people worrying about the "unforseen side effects" when its conservative people worrying about liberal concepts.
Are there any takes on the gross energy inefficiency of mega-churches? The political downsides to allowing single corporations to own mulitple radio and TV stations? The waste of super-profiling internet users in order to (slowly) serve ads?
Nope, never. It's always an "analysis" showing that some generally liberal-oriented thing is bad.
Darn straight! I've had my Leaf for years, and apart from trying the quick-charge at the dealers when I got it, I've only ever charged at home from an ordinary outlet in the garage.
That means zero time at gas stations, and also zero time with oil changes. The car's been in for a quick firmware update once and the tires have also been replaced.
Historically, when the email protocol was first made [RFC 561](https://www.rfc-editor.org/rfc/rfc561) in 1973 personal computers were rare and very low power. At the time, hardly anyone owned a computer on their own.
That said, might be cool, but good luck getting most apps to accept something without an @ as an email address
You'll need to be more explicit about what you think "Phone OTP" is and what you think "refuse" means.
Phone as in, "the OTP requires a cell phone with yet another buggy authenticatoin app"? Or phone as in "can support SMS"? Or phone as in "phone must support touch-tone"? Phone as in "the user must be able to hear and speak?"
"Refuse" as in, "I'm in the unpopulated area of Washington state and I have no phone signal"? Or refuse as in "I'm not using my personal device for work"? Or rfuse as in "I don't use smart phones because I want to live in the moment"?
Why not just rename [Haystack Mountain](https://usabynumbers.com/mountains-in-connecticut/) in Connecticut (USA) to K2?
That way climbing K2 will be as easy as a car ride!