485 karma · joined September 15, 2010
- Everything about rust enforcing correctness catches lots of bugs
- Using a high-level API means I can easily hand-check things in a repl
- In addition to tests, I required a full “demo notebook” with any PR — I should be able to read through it and confirm that all the functionality I wanted has actually been implemented
If the philosophy is (and it should be) “loc is free”, it’s worth thinking about how we can make LLMs produce more loc to give us additional comfort with correctness. Language choice is very much a way.
Patients First
Important, not Immediate
Learners before Masters
Together, not Alone
Progress before Perfection
Adaptable, not Comfortable
https://en.wikipedia.org/wiki/Leech_lattice https://en.wikipedia.org/wiki/Monstrous_moonshine http://motls.blogspot.com/2015/03/umbral-moonshine-and-golay...
If you have a company that is doing genuinely interesting AI work, it's likely that they are somehow on the forefront of research, pushing existing tools to do things that they can only barely do. If you find yourself in an AI role (typically only some roles actually do AI, of course -- systems need to stay up, great UIs need to be built, etc.), I would guess that you'll need to familiarize yourself with their particular toolsets and methods rather than assuming that there are universally correct things to go learn.
One Christmas, we were talking about how difficult it is to assess the accuracy of an algorithm when you only get a few tries because running it is expensive; he promptly told us about his experience with this problem, which he encountered driving plutonium nuggets across Richland, Washington. After the video from the ACM conference on personal workstations got published here, I learned for the first time he'd been fired from MIT three times for insubordination, and I never got a chance to ask him what the story there was...
Oh! And he actually made a physical turing machine good enough to do fairly sophisticated computations on. It ended up in my father's intro CS class at Princeton for many years.
And HN will of course appreciate one of his favorite one-liners:
Did you know that 49 is the lowest number that can be expressed as the square of 7 in only one way?
Fare you the hell well, Gramps.
As to stodginess, I'd say there's a big difference between personal/small commercial lines and the big ticket enterprise-type stuff -- the underwriting process goes from something data-driven to something relationship-driven very quickly indeed. The bigger the commercial line, the more likely it's all about who throws the best yacht parties (reinsurance in particular suffers from this massively).
Crowdsourced insurance is indeed a terrible idea, though you could imagine 'web of trust' insurance that almost made sense -- say my ten thousand best friends and I know that we're all great actuarial risks, perhaps because we have some kind of information on which it's illegal to select (that we're all in the same gym, say). We could then try to write ourselves health insurance for cheap, because our plan would select only us gym members. You can sort of make it work, as long as you're prepared to make the regulators hate you.
Which is the real problem, of course -- most people buy insurance because they have to, not because they want to. Auto insurance that wouldn't pass muster with the police, or home insurance that wouldn't satisfy the bank holding your mortgage, doesn't solve the problem.
Do good problems exist? Sure. A web-based Managing General Agency, for instance, could do very well for itself, but the expressed ideas in this section are pretty terrible.
>>> print ftfy.fix_text(u'ordinal indicator º to o in addresses.')
ordinal indicator o to o in addresses.
>>> print ftfy.fix_text(u'ordinal indicator º to o in addresses.',normalization='NFC')
ordinal indicator º to o in addresses.That said, if you have examples where ftfy fails in any language, please submit them! We want this tool to work well, because anything that we can't fix will cause us to have egg on our faces with a customer someday...
[1]No peeking: how many format options in Excel's "Save As" dialog, excluding Excel formats, produce a document from which Unicode can be recreated accurately?
http://blog.lumino.so/2011/11/07/enron-evil-versus-football/
Just look at all that orange at the top of the first image: that's traders talking to each other about trades. Energy trading is what the company was about, not the tiny internet company that they may have spawned or the HR department. Those people don't deserve to have had their reputations ruined by the fraudulent hedge fund blowup and C-suite malfeasance, but that doesn't mean their parochial views are the correct overall view.
In general a real market is imperfect in any case where firms make profit above their cost of capital -- i.e. most of it -- since perfect competition is supposed to drive profits to zero everywhere. The employees of a firm making profits certainly can be paid more without imperiling production, since the profits could simply be reduced.
Almost throughout, Hazlett makes exactly this (very common, for those with a political axe to grind) fallacy, supposing implicitly everywhere that no company is profitable despite the fact that we are manifestly not living in that world.
Of course, CEO's shouldn't be paid that much in the first place (I do tend to think in almost all cases that the bad a poor CEO can do outweighs by several times the good a good CEO can), which would tend to lessen the value of severance packages overall. But if any Fortune 500 CEO deserves anything close to their current compensation package, spending only $10mm to fire one sooner rather than later is an excellent deal.
Is some actual reporting. He's an individual day trader, not an institutional trader of any kind. So I'd say you're pretty right.