517 karma · joined April 28, 2016
Heck, even actual Biography (non fiction) isn't even judged that way.
Cat Person succeeds because it captures a deeper truth. And boy does that story touch a nerve - a mirror that is hard to look at because of its truth.
"When you feel the urge to write an email, pick up the f*king phone instead. When in 5 years you're being cross-examined you can say 'I don't remember saying that' and you won't be lying, because we're too old to remember things, and I won't have to bill you for the time it takes to read all the f*king emails."
Insured: $50 flat rate, ground or air.
Uninsured:
$848 flat fee (ground service)
$4,394 per hour (helicopter)
:-p
Nothing wrong with that!
> They were so focused on building a nice looking bridge — and meeting deadlines
These are also good things.
To me sounds like the civil engineers started behaving more like software engineers. The independent peer reviewer they hired was not qualified to do the review.
> Louis Berger was not qualified by the Florida Department of Transportation to conduct an independent peer review and failed to perform an adequate review of the FIGG Bridge Engineers design plans and to recognize the significant under-design of the steel reinforcement within the 11/12 node, which was unable to resist the horizontal shear between diagonal 11 and the bridge deck.
This whole business of the engineers ignoring the cracks that the contractors kept needing reassurance about is also insane.
Might as well argue against using windmills to grind wheat.
But I worry that it's vulnerable to bad people.
Got a hefty personal bill coming up, and you're pretty confident your SaaS business will be dead within 6 months but Stripe has no way of knowing based on current numbers?
Thinking of getting a divorce (startup or marital)... maybe time to grab the largest advance possible before your soon-to-be ex(-co-founder) realises?
The problem is that even if only 1% of Stripe's customers might match these kinds of profiles, that same 1% might be taking 20% of the Stripe Capital advances.
https://mergebase.com/doing-git-wrong/2018/03/07/fun-with-gi...
After I wrote that blog post someone told me the reason for the magic is the use of "git merge-base --fork-point" under the hood.
ArrayList list = new ArrayList();
for (int i = 0; i < N; i++) {
list.add(i);
}
It's a neat restructuring of the vector into a SQRT(N) * SQRT(N) arrangement.
Obviously M.2 or NVME or PCIE would be a lot better. But even old SATA still made a huge difference.
I guess partitioning can help, but then isn't it just turning the DB servers into pizzas of master-slave where the Hawaiian slice is master only in Hawaii, and slave everywhere else?
I wasn't a computer person back then. But I quickly learned about SMB file and printer sharing being wide open.
Here is Charles Dickens writing about his own contortions to monetize his work:
There must be a special design to overcome that specially trying mode of publication, and I cannot better express the difficulty and labour of it than by asking you to turn over any two weekly numbers of "A Tale of Two Cities," or "Great Expectations," [...] Notice how patiently and expressly the [serialized novel] has to be planned for presentation in fragments, and yet for afterwards fusing together as an uninterrupted whole.
I think holding onto bugfixes and feature enhancements and letting Patreon subscribers have first dibs on these makes sense.
If student loans became dischargeable through bankruptcy, I imagine that could put pressure on bankruptcy laws in undesirable ways (e.g., the current 7 year period might get extended to 20 years).
I'm not OP, but I gotta say whenever I've faced questions like these in my career, I find I'm not actually being asked any questions at all, I'm being accused of lying, and it's time to walk.
Granted this is quite the esoteric edge case... at least for now. ;-)
Fortunately a copyright takedown request is not a typical scenario, but it does happen, even with "immutable" repositories like maven-central.
Even if evil.com gets you to register and present your key, they cannot forward it to mysite.com. Even if they go to all the trouble to completely mitm you and the site looks identical to mysite.com, they cannot get the emails or get it to send money.
This is because evil.com cannot pretend to be you when they interact with mysite.com no matter what you've given them.
It's going to be hard to trick me into thinking I've logged into my gmail if none of my emails are there!
Unless they somehow convince you to put your yubikey in the mail and physically send it to them...
These in particular jump out:
- Risk profiles for diverse users can be very different:
Any discussion of the pros and cons of disclosure should take into account that risk profiles vary drastically. Taking this argument to the extreme, the question arises: "Is it OK to put 100m people at risk of inconvenience if I can reduce the risk of death for 5 people?"
- Ultimately a patch must be published. If a corresponding vulnerability disclosure does not also go out this leads to information asymmetry between attackers and defenders:
People in the offensive business can build infrastructure that helps them rapidly analyze patches and get the information they need out of them. Defenders, mostly due to organizational and not technical reasons, can not do this.
- The incentives inherent to the software development lifecycle are out of alignment with the incentives of writing secure code:
By the time the security flaws in the newly-shipped features become evident, [the software manager responsible] is four steps in the career ladder and two companies away from the risk they created.
So it certainly helped me. And just based on how thorough and insane the test suite is, I think I'm in good hands. Not perfect hands - but definitely a million times better than anything I would have come up with on my own.
The test suite made my parser blow up many times, and for each blow up I got to make a conscious decision in my bugfix: how do I want to handle this?
(I decided to let the 10,000 depth nested {{{{{{{{{{{{{{{{{{"key","value"}}}}}}}}}}}}}}}}}}} guy blow up even though it is legal. Yes, I'm too lazy to implement my own stack.) :-)
Do you just go with what the browser or client locale says? (User lives in Canada but their laptop is set to Turkish locale).
Go with the locale tied to the geo location of the user instead? (User above stubbornly enters all amounts using Norwegian conventions after completing high school in Norway).
If it's important, a confirmation page presented to the user and formatted in their presumed locale can help a lot.
In that case wouldn't he simply have to divulge that fact early on in the decision-making process? "Guys, maybe I should recuse myself on this decision since I'm in a bit of a conflict..."
I suspect either due-diligence caught it and decided to live with it after some negotiation, or they missed it - oops!
I'll use JavaScript numeric literals here as my translation medium (ironic!):
Norway locale parses it to: 1001
USA locale parses it to: 1.001
France locale parses it to: NaN
https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/ind...