kmontrose

11 ms·

1.
by kmontrose 10mo ago
This rebuttal is... poor, I guess? Not disingenuous or anything, but lots of wishful thinking and (for lack of a better term) "inside baseball"-objections. Like sure H3 might be a byproduct of other mining on the Moon, but the ha
2.
by kmontrose 11mo ago
YoY sales are down while other automakers are up, Q3 might be an artifact of EV incentives expiring. Iirc other manufactures also saw an increase in EV sales in Q3.
3.
by kmontrose 2y ago
The Stack Exchange TOS ( https://stackoverflow.com/legal/terms-of-service/public ) doesn't assign ownership - posters retain copyright, SO gets a non-exclusive license to it, and everybody else gets it under
4.
by kmontrose 3y ago
I don't know that I've ever heard such a violent "woosh" as the goalposts were moved. Going from "obviously happened, consistent with evidence" to "the problem is the way it was discussed in private"
5.
by kmontrose 3y ago
> This, is damning evidence regardless of any of that. Nothing remotely like this was being presented by mainstream newsmedia, perhaps because nothing remotely like it was being presented to them by the scientists they talked to. There w
6.
by kmontrose 4y ago
The Old New Thing: https://devblogs.microsoft.com/oldnewthing/ Been reading it for years, lots of little interesting insights into current and historical quirks in Windows and related systems.
7.
by kmontrose 6y ago
Only became a problem in combination with other missteps (or constraints, like dev needing to be routable). Which is what makes this kind of stuff so insidious.
8.
by kmontrose 6y ago
It's this. Discovery, immediate mitigation, deeper mitigation, general notice, notifying effected users - all these can happen pretty quickly once the ball is rolling. Once you're dealing with "the law" in any capacity
9.
by kmontrose 6y ago
The breach itself was announced shortly after it was discovered: https://stackoverflow.blog/2019/05/16/security-update/ And affected users were notified once identified, which was shortly after the annou
10.
by kmontrose 8y ago
The House has already passed a couple bills funding the government, in whole or in part[1]. They haven't been taken up in the Senate. One of the bills passed this week: https://www.congress.gov/bill/116th-congress
11.
Stack Overflow Gives Back 2016(stackoverflow.blog)
4 points by kmontrose 10y ago|0 comments
12.
by kmontrose 10y ago
There's a pretty strong connection between the numbers the tool has and market rates - it's not like the numbers are pushed top down, they come from actually participating in the hiring market. The calculator normally gets a few r
13.
by kmontrose 12y ago
You also install runtimes once for other languages. GOPATH isn't awful, but it's something more than "just source" as claimed in the article; which is my point. Go is simple, but not as simple as claimed.
14.
by kmontrose 12y ago
My point is that `go generate` requires more than just source, and thus isn't "simpler" in the manner claimed in the article. I'm not judging the existence of `go generate` or it's merits relative to some other envi
15.
by kmontrose 12y ago
And? Presumably some of these packages get updated, handed off, or are collaborative in the first place. Re-generating is part of continuing development.
16.
by kmontrose 12y ago
This oversells golang's simplicity I think. Not a lot, but enough to rub me the wrong way a tiny bit. --- > Go programs are built from just their source, which includes all the information needed to fully build the program. Still h
17.
by kmontrose 12y ago
Something of an in joke I suppose, but design thought it was funny enough to leave as is.
18.
by kmontrose 12y ago
Localization probably kills that, since this is displayed to users a not-insignificant amount of the time. "9" is pretty well universal (I know, not strictly, but for software Arabic numerals are kind of assumed knowledge); "
19.
by kmontrose 12y ago
Such as? App compat's out (ie. "Run this program in compatibility mode for"), too many libraries. They'd never get an accurate enough list of affected programs. They can't change the reported OS name, too many apps
20.
Jil: Version 2.x, Dynamic Serialization, and More(kevinmontrose.com)
2 points by kmontrose 12y ago|0 comments
21.
by kmontrose 12y ago
It doesn't even cover C#, just C++ and Java. C# has it's flaws certainly, but it's a baffling omission.
22.
by kmontrose 12y ago
After thinking on this for a while, I personally doubt the license applies. Most importantly, it applies to the software (ie. the Perl script; or a compiled version of it) not the "name" or "invention" of Markdown. To o
23.
by kmontrose 12y ago
There's a real difference between consumer and enterprise grade SSDs. For comparison, for a while we nearly had a 1 to 1 dev to killed (consumer) SSD in work machines (see: http://blog.codinghorror.com/the-hot-crazy-sol
24.
by kmontrose 12y ago
That's a straight copy/paste from the Stack Overflow codebase (Helpers\SqlMapper.cs:332 at time of writing, if you care). Now the typos and snark are out there for everyone to see.
25.
by kmontrose 13y ago
New DNS records propagating.
26.
by kmontrose 13y ago
You could go grab the copy we put on internet archive a few weeks ago. https://archive.org/details/stackexchange Pretty sure we'll have this worked out with our provider before you can finish downloading though.
27.
by kmontrose 13y ago
David means a single primary, there's a read-only replica for in DC failover and a read-only replica in our other DC for "New York is getting hit by another hurricane"-failover. A few services hit the read replicas instead of
28.
by kmontrose 13y ago
The most common reason for someone going remote (that I'm aware of) is starting a family. New York's great, but spacious it is not. I can think of 3 devs who have gone remote, and 2 devs (including myself) who have moved to NYC s
29.
by kmontrose 13y ago
Technically we use Newtonsoft and Jil, Jil replacing Newtonsoft as we become increasingly confident in it. I wouldn't suggest anyone use Jil in a production role unless you're at Stack Overflow. It's too untested at the mome
30.
by kmontrose 13y ago
Stack Exchange has one database per-site, so Stack Overflow gets on, Super User gets one, Server Fault gets one, and so on. The schema for these is the same. There are a few wrinkles. There is one "network wide" database which h

More ›