skysight-inc/HackerNews huggingface dataset:
From Levine's story this morning:

"If you were...inclined to be critical...you would characterize this as Uber’s underwriters talking up the stock to their investing clients, telling them that there was lots of demand at $45, and then pricing the deal there, while at the same time quietly betting their own money that the stock would fall immediately. They sold stock to their customers while betting against that stock, and then that bet turned out to be correct and they made many millions of dollars on it. I cannot stress enough that that was not the subjective experience of Uber’s bankers, who undoubtedly—for their own careers, for their relationships with investors and issuers, for their reputations as skilled bankers—wanted this deal to go differently. But it kind of is what happened, oops. At least they got the money."
Driving too slow results in more accidents.

Driving too fast results in more fatalities.

It might be nice to decrease both, but I know what I care more about reducing.
Yesterday I got a rejection explicitly because I was "too senior"—for a senior position.

Guess I was too expensive, heh. The tone of the declination was actually super kind.
That's interesting, I stand corrected. TIL that it's actually a heavily disputed topic and much less clear than I painted it, I had quite a different impression before — thanks!
Regurgitating things you can learn from Stack Overflow in 15 minutes does not constitute leadership. You could write all of that stuff in a Wiki and share it with your team and suddenly your “leadership” is a commodity. Now, sure, knowing this stuff is valuable, but it’s not leadership. At best it demonstrates tenure in the particular area.

Leadership is when your team members come to you to solve difficult technical tradeoffs. It’s when you are giving valuable unsolicited feedback because you see problems and want to help the team. Leadership is driving difficult changes that may not be popular but are necessary, and finding a way to sell those changes to the team. It’s taking on work that matters and postponing your own features because the success of the team matters more than the success of your particular project or area.

Leadership is about leading. Not about being able to answer basic questions that anyone with a few years of experience should be able to answer. If your “leadership” is only applicable to one narrow technology, you don’t have leadership. You just have familiarity.
Wait is this place CNN or is it HN?
The 2D rigid body and 2D MPM examples run in real-time, everything else is offline.
The state sets lower limits to what work should be worth, in order to avoid unpleasant social outcomes, such as worker abuse. It also sets a minimum of benefits companies should offer, in order to fulfil their side of the social contract - being allowed to safely do business and have access to capital, workers, etc.

If Uber, or any other company invents a type of work which cannot be compensated according to those rules, then they do not have a viable business and will go bankrupt or be fined out of existence.

In practice, they've managed to find enough loopholes to survive, while making the lives of many of their employees miserable.
As I said somewhere in that thread, I only ever encounter arguments against value-based billing from other contractors/consultants, and not companies. There's probably a psychological topic there to explore but I won't go there. I have nothing to gain by convincing other contractors/consultants, except the feeling that I helped someone escape the hell that is hourly billing.

Yes, it helps to be offering some unique value that can't just be found on Upwork (see excellent posts on this [1] and [2]), but you don't need to be in the 99th percentile to do value-based billing.

I don't know much about the author but they're probably in that 99% whose work you think is commoditized (or at an equilibrium). Clearly this is not true, since they were paid $21k for work that could've been done by a large portion of that 99%.

[1] https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...

[2] https://tomcritchlow.com/2019/04/04/the-strategic-independen...
It's circular logic. They're basically saying that there exists a low enough speed that could have theoretically prevented this. Whether any reasonable person would have been going that speed is another story. Crashes would be a lot less common if vehicles couldn't travel faster than 20mph. Car crashes would cease to exist if vehicles couldn't move at all.
Do you transfer Visa?
Accidents happen at intersections because many drivers are not good at making themselves aware of traffic approaching from multiple directions. At a roundabout drivers only need to look in one direction. They are strictly better than traffic lights for all drivers except those who are not experienced with roundabouts. Those drivers should familiarize themselves with roundabouts.
Yes, "charge accordingly" means different things to different customers.

My parents never advertised their tailor shop, it was all "word-of-mouth" business. After the pricing jack-up, every customer got charged what my mother felt they could pay (with a very loose regard for consistency and some allowance for negotiation).

I used to think that was sketchy. It wasn't until much later that I realized that B2B enterprise sales people do that stuff ALL THE TIME even with their onerous kpi's, forecasting and fiscal quarter expectations!
Let's dissect.

- Same OS, server: you likely control all the processes in it anyway, no untrusted code.

- Different OSes in different VMs, server: they likely run different versions of Linux kernel, libc, and shared libraries anyway. They don't share the page caches for code they load from disk.

- Browser with multiple tabs, consumer device: likely they might share common JS library code on the browser cache level. The untrusted code must not be native anyway, and won't load native shared libraries from disk.

- Running untrusted native code on a consumer device: well, all bets are off if you run it under your own account; loading another copy of msvcrt.dll code is inconsequential compared to the threat of it being a trojan or a virus. If you fire up a VM, see above.
> > Unix time is the number of seconds since 1 January 1970 00:00:00 UTC

> Think of seconds in terms of some physical phenomena, like how many times a certain atom trapped in a crystal lattice vibrates and you see that doesn't depend on the calendar

Unix time is NOT the number of physical seconds since 1970 UTC. It's the number of Unix Seconds since 1970. Every day has 86400 Unix Seconds. Some UTC days have more than 86400 physical days. Unix time cannot represent the seconds beyond 23:59:59 on a UTC day, but otherwise attempts to match UTC.
In high school I was working at the local used CD store and when this broke I saw tons of CD's came in with green marker on them. Not to mention the hundreds of people I had to explain (in some detail) how a CD actually works and how this was total rubbish.

For some of these people, it was if they just discovered Santa Claus wasn't real.
The search for "Go" is actually quite inaccurate due to the verb "go" and the game "go". You can see most of the peaks have top stories related to non-language uses of the word.

It seems the effect of other meanings is way less exaggerated for Rust in comparison.
Seems you're the only person that tried actually going to the website, where this message is prominently displayed.
Kind of ugly, but that's easy to fix. Great project given that services like Mint are just data vacuums.
The article makes no attempt to answer the question in the thread title.

Tldr: woman wears headphones a lot because they have a noisy office, noisy apartment and ear buds help her sleep. Thats it. It's a non article.
Who are you dropping this for?
You are mathematically correct, it is impossible to prove that, even the case with the third pilot is not a contra-example because it probably was not the exact same issue.
Usually the first step is to correct from what ever the local clock at the observatory said to actual UTC.

Then you convert from UTC to TAI.

And then you convert from TAI to the arrival time at the solar barycenter, removing the geometric light travel time to Earth (or more precisely the observatory) as well as the gravitational effects of Sun, Jupiter and Earth.
They should move it from house to house and make it an occasion to invite the next neighbors to dinner :)
> This suggests to me that to make roads safer, we might want to design them so that drivers feel they need to drive slower and more safely. Narrow the lanes where they are too wide

anecdote about the opposite happening:

There is the I90 tunnel in Seattle which I use very often. Some passages have 2 lanes, super narrow, no shoulder, nothing. Looks like this: https://goo.gl/maps/DzvhWZAoD5AkRVwA9

You won't believe how fast people are going through that. Also, almost every time I get tailgated and I'm frankly amazed there hasn't been any major accidents in that tunnel considering how close people are driving (no following distance). Just yesterday I was tailgated by somebody on their phone (I could see the screen reflected in his face while he was texting). I don't want to imagine how an accident would look like in that tunnel. Honestly, a fender bender can become catastrophic before you realize what happened.

Now if you mean 'narrowing' roads then probably yeah. Take a wide-ass lane and suddenly make it narrow (so that people using it every day are 'surprised' and they're more careful) and I could agree with you.
This is going further & further OT, but hey - I didn't start it!

What you need is a motivating factor. Vim is almost guaranteed to be there on any Linux/BSD/Mac shell environment, which motivates people in those environments to learn it even if they learn no other editor.

Beyond such environments, like on any desktop GUI, what'd motivate you to try GUI Vim? For Emacs, I can say the integration between any set of tools you can imagine could be a motivation.

The reason Emacs users don't particularly appreciate IDE's is that Emacs' integration of code editor, compiler output, debugger control makes the development cycle extremely fast. Add any 1 more use to that. File explorer? Emacs dired. Process monitor? Emacs proced. Interactive shells? Emacs integrates Unix shell, Python sessions, anything interactive actually.

You will get all your work done in Emacs, just using editor operations! Go to the source code for a compiler error? Hit "Enter" or click on the error in the compile window. Go to the source code being debugged? Stepping in the debugger automatically opens the file at the right line number. Found the bug? The code is already there ready to be fixed; switch to the compile window & compile. Find a file in a directory? Do a text search in its dired window. Rename all files beginning with foo to begin with bar instead? Do a search-replace.

Emacs also scales way better than any desktop editor or Vim, whether it is opening GB-sized log files, or binary files viewed/edited in hexadecimal. Before long, you start managing your to-do's using org-mode, and doing all your Git operations in the insanely featureful Magit interface.

The list gets longer and longer every release. And many Linux shell environments support the same basic keyboard short-cuts (Ctrl-A to go to beginning of line, Ctrl-E to go to the end, Ctrl-R to search in the shell history), and also provide light-weight Emacs clones like 'zile', 'mg' for editing-only use in the terminal.
> It'd be another Go with generics, or Elixir-native, or Swift with uglier syntax.

I just want to point out that the Swift package management situation is currently bad. SPM (https://github.com/apple/swift-package-manager) can't be used within Xcode, and is basically not used for anything outside of server-side swift / Linux.

It also doesn't look like SPM will be integrated with Xcode this WWDC, so you're stuck with CocoaPods or Carthage.

I'm really jealous of cargo. And RLS (Swift LSP doesn't really work well because it doesn't know about your dependencies - back to the package manager issue).
I don't think it's speed enforcement in most cases. It's usually people not wanting to deal with changing lanes to deal with the slowest traffic.

For a while I would come up across a large number of vehicles inexplicably stacked in the left lane, with a huge gap on the right lane. Younger me would zoom up the gap and inevitably find a semi truck and someone passing it very slowly, and the left lane would close ranks because they thought I was a dick. Older me just stays in the left lane.

edit: I'll move to the right when it's so obviously clear that I won't have to move back to the left. But it's really tedious to be weaving across the road with regularity to maintain a strict adherence to the keep right law.
I wouldn't be surprised if someone told me 10-15% of our bugs were because of Eng/PM misunderstanding this.
How I actually avoided spell-check before publishing a post
Your example is a trick question that will catch some real humans.
>revamping hundreds of street corners to slow down turning cars

This is probably the biggest one. Lots of pedestrians and get hit by people turning right who can't see them until the last second because of other things on the street corner (like people waiting to cross in the other direction).
120 MPH probably exceeds the the speed of reaction time for most drivers. A not-that-tightly packed group of cars going 120 MPH with a single blowout could have devastating effects. There simply isn't enough road to having a following distance big enough. Not to mention there would be entire classes of vehicles not able to safely travel (or travel at all) at such a speed such as semi-trucks.
>for a second week you're just robbing from competing films and the theaters themselves.

Which is absolutely the point
I use very simple code- multiprocessing wrapped around s3.download_file and see gigabit+ throughput with a single core.
> Apparently (according wiktionary) the reconstructed vulgar latin word of origin, *linguaticum, was neutral.

When the transition from 3 gender to 2 happened, neuter words had to be "assigned" to one gender or another. Sometimes this was just arbitrary, other times conditioned by phonology or semantics.

The same phenomenon occurred when Sanskrit's 3 gender system gave way to the dual gender system of the new-Indo-Aryan languages like Hindi. In that case, most neuter words became masculine because they were often already phonologically similar to masculine words in the accusative case.
FWIW: sr.ht is pretty cool, has a nice no-nonsense UI, and the build system is really simple and powerful. It's not "done" but it works and is going in the right direction. It's a very nice corner of the Internet. I've been using it for personal repos and I'm really happy.
Who knows, maybe they were enjoying one of those formerly secure jobs that was either automated out of existence or ruined by "clever" companies through loopholes like not offering job contracts.
>ignore advice about maximizing negative space.

I think it's a spectrum. On one end there are Windows 10 UWP applications which have absurd amounts of negative space, while on the other end there's e.g. Plasma with its claustrophobic, crowded UI. Both result in terrible UX (although, to be fair, UWP is much worse), so the sweet point in somewhere in the middle of that spectrum.
f before the quote though
>Also, changing the wake word requires a full restart, which says "firmware" to me.

Well to me it says "static variable".
Its a natural consequence of wanting to inflate your position when you have little to no personal authority on the matter, and essentially stealing 'authority' by supporting what amounts to an angry mob on the internet. "One person thinks this" has never really been a valuable commodity, unless that one person has some kind of name recognition.
(I'm a co-author of the blog post)

I generally agree re: trope, but it's useful because I'm not sure the core idea is widely understood outside security circles. Many people assume that containers provide a strong isolation boundary, and while a break-out is not trivial, providing more isolation in some cases is important, as you allude.

While one option is certainly to provide a locked down policy, monitor the flow of kernel CVEs, and patch constantly, this may not be feasible for many organizations if a) they lack the technical expertise or b) don't know the workloads they're running a priori and can't apply a fixed policy.

So different container runtimes are about providing additional tools for defense-in-depth. (VMs are fantastic tool for this, but it's also nice to have tools that play well in containerized infrastructure other than custom security policies.) None of these tools will be perfect of course, hopefully they can make it easier to improve on the status quo.

Re: contained.af, this is a great example of the workloads problem. If you have a known workload where you can essentially disable all capabilities and access to system resources (e.g. no network), there are many options for securing that workload. They aren't all generalizable.
I don't have any reference material/tutorials, but my major breakthrough with Vim was when I understood that normal mode is the norm. Anytime you're not entering text, be in normal mode. Remap jk or jj to escape. Get in the habit of typing it whenever you're done adding text. Use hjkl for movement instead of the arrow keys. Learn the f,t, and o commands.

http://cloudhead.io/2010/04/24/staying-the-hell-out-of-inser...
Tesla’s trumpeted solar shingles are a flop
I think gvand means that these users are training the AI models to eventually provide a similar level of service offline. The "cluelessness" is just a value judgment of the users.
Physics simulation is a very active computer graphics research topic (see e.g. the SIGGRAPH conference). The goal in computer graphics research will not be to have an exact result, but to have a visually plausible (and pleasing) result as fast as possible.
It's really sad thinking how kids these days totally miss the wonder of the early internet.

And before that, the wonder of bulletin board systems. I got my first modem in 1985!
1. Do some research and look for a good book on python, or possibly a MOOC/set of videos.

2. Follow the content, make sure you understand the concepts. Don't just read the material, it's recommended to code what you're reading so you spend time understanding what you're coding.

3. Solve some exercises.

4. Once you've covered the fundamentals, go and start off with a project. Start with a small project, then create bigger ones.

Essentially, cover the fundamentals and understand them, then go ahead with a project. The real learning is in the projects you'll build as you'll find gaps in your knowledge that you'll cover on the way. But it's good to study the fundamentals so you have a starting point and aren't completely lost.

There are a lot of good books for an introduction to Python, "Automate the boring stuff"[1], "Think Python"[2], and many more. These two are actually available for free online. Someone here can probably recommend some better books or you can look up other recommendations online.

EDIT: formatting

[1] https://automatetheboringstuff.com/

[2] https://greenteapress.com/wp/think-python-2e/
Sell value not cost.
Fox has channels in India - https://en.wikipedia.org/wiki/Fox_(Indian_TV_channel), UK and Ireland https://en.wikipedia.org/wiki/Fox_(UK_and_Ireland), and many other countries - https://en.wikipedia.org/wiki/Fox_Networks_Group#Internation...
Awesome, thanks. I need to dig into this a little and just run a few demos / labs. This makes sense though. I really like your comments on this thread too (https://news.ycombinator.com/item?id=16976392).
The headline is entirely correct, and I don't understand your claim otherwise. No one is arguing that Morgan Stanley overpriced the IPO on purpose. They knew they had a dog on their hands and opened a short position in hopes of propping it up (though it didn't hurt to know that failing to do so would mean big profits).
Unix time is based on a hard calculation of UTC seconds, minutes, hours, days, and years. So UTC jumping causes a discontinuity in Unix time.

Im pretty sure the second graph is mislabeled (the UTC second after 23:59:60 should be 00:00:00), but Unix time takes 23:59:60 to mean the same as 00:00:00. So 23:59:60.5 is also the same as 00:00:00.5, and so on. If you parsed the Unix time into a readable timestamp, it would tell you it's the first second of the next day for two seconds.
OTOH, during the 70s drunk driving, heavy smoking, not using seatbelts and a whole host of other very dangerous activities were socially acceptable.
Developers who have great insurance coverage at their current job and require it at their next job aren't candidates for startups like mine. We don't have health insurance for employees - it's just too expensive for all but the very well-funded startups.

For this reason, experienced developers from other countries which have universal healthcare coverage and low cost of living, such as many Eastern European Countries, are very attractive to many startups.
Some additional resources:

Efficient Market Hypothesis[0]:
"The efficient-market hypothesis was developed by Eugene Fama who argued that stocks always trade at their fair value, making it impossible for investors to either purchase undervalued stocks or sell stocks for inflated prices. As such, it should be impossible to outperform the overall market through expert stock selection or market timing, and that the only way an investor can possibly obtain higher returns is by chance or by purchasing riskier investments."

Investment theory of party competition [1]:
"[...] if voters cannot bear the cost of becoming informed about public affairs they have little hope of successfully supervising government."

[0] https://en.wikipedia.org/wiki/Efficient-market_hypothesis

[1] https://en.wikipedia.org/wiki/Investment_theory_of_party_com...
Sure, because the other 80% of engineers have to clean up after the 20%.
I am from Brazil, that for some reason unknown to me went along USA speed limits.

I started driving more or less recently and my town has several speedtraps, and they make me unsafer, becuase I am not used to driving a lot yet, I tend to respect speed limit all times, because I don't know where the speedtraps are, this has some consequences:

1. LOTS of honking when I am 5kph slower than the limit...

2. Because of the point 1, I tend to stick to the limit, this mean I am often looking at my speedometer instead of the road, and almost crashed because of this more than once.

3. Often I am overtaken in ridiculously crazy ways, like people overtaking in the opposite direction lane, or during corners, or more than once motorbikes overtaking me using the gutter, passing between my car and the sidewalk.

4. Also a couple times I almost crashed on the rear of experienced drivers that were speeding and I don't noticed, andwent along with the flow, only for them to suddenly slam on brakes right before the speedtraps (only to just as suddenly accelerate again right after them).

5. Often lanes end with strange speed discrepancies, sometimes in unsafe situations, for example there is a one-way road in my town that is in a steep hill that has a curve toward the right, often the left lane is full of people trying to overtake the entire right lane that is following speed limit, and the railings on the outer side of that curve are full of marks of people grinding on them.

I've seen once a group of 10 or so cars that were speeding slightly try to overtake a car that was following speed limit only for the first one of the group to crash on the rear of a bus that was on a bus stop when he tried to overtake from the right side (the other 9 or so cars squeezed themselves between the crash and the cars that stopped on the left lane while braking... lots of screeching).