skysight-inc/HackerNews huggingface dataset:
Does "proven" here mean the same thing as "no runtime errors"?

I've recently tried out Elm [1] and have come away with a similar perspective on functional programming and static typing. The benefits I noticed are:

- Because of the static typing and strict management of data/state, the compiler is very good at telling you where the errors in your code are.

- If the compiler is happy, there are essentially no runtime errors.

- While I didn't write any tests, unit testing seems like it would be trivial because every function is stateless.

- You're forced to write better code. I find that Elm is pleasantly constraining. It's an opinionated language that forces you into certain design patterns, but they always seemed like the design pattern I should be using anyway.

Overall, I haven't been more impressed by a language since I discovered Ruby a decade ago. If you could do backend development in Elm I would probably try using it as my primary language.

1. If anyone else is interested, I went through the Pragmatic Studio Elm course: https://pragmaticstudio.com/courses/elm. I have no affiliation with them, just thought it was a really well done course and would recommend it to others who want to try out Elm.
The idea of "entropy" always seemed to me as a misrepresentation of the actual underlying principle, given a half-dozen other names in scientific literature. Everything reaches the lowest equilibrium state. It's like pouring water into a glass: eventually, all the waves will be gone and it will all settle into the lowest state on the ground. That doesn't really say anything about "order" at all - from the perspective of the atoms, all the "order" is still there. The "messy" vs "useful" analogy also is poor since you can use more energy to make a completely useless contraption (a "messy state") and construct it in a way such that it degrades into a useful one (a bit of a contrived Rube-Goldberg, but still...). Heck, does throwing water into the air and letting it fall into a pond make it "orderly" against the Second Law? That's what the analogies imply. The more analogies that try to compare the Second Law to common experiences like a dirty room, etc., the less people get an idea of what Joules per Kelvin is supposed to mean when they finally meet it in their chemistry book.
One-Dimensional Linear Hybrid Cellular Automata of Degree Through 500 (1995)
Linear programming Assignment Help
@kelukelugames may be referring to the "anonymous work talk" app: https://us.teamblind.com

Which, it's been reported, is widely used among Uber employees: https://techcrunch.com/2017/02/25/ubersecret/
> Life insurance is a dumb idea.

Not if your beneficiaries depend on you for support that you can no longer provide if you're dead, and if you care about what happens to them.
So you want to build a trolley
Yes. The codebase is best described as a giant pile of hacks.

It's the culture more than the tech that causes this to happen. Every time I offer to refactor I'm told to fix it the fastest way and that's how we've been doing it for 10+years.
I live in switzerland and I have a liebherr fridge and Schulthess washing machines. Mine are new (I moved in 7 years ago), but I know they will last. Everything I've seen while traveling (hotels...) seems super crappy compared to that. I wonder why those brands are not exported more.
How Instagram Changed Before It Had To
I don't claim or believe that the core team is owned by Blockstream. However top contributors like Greg Maxwell, Luke Dashjr and Peter Wuille are Blockstream employees and there's no doubting that they have considerable influence in the team.
I'm in almost the exact same position except possibly worse so as I'm about to be sponsored by the company to stay in Australia on a skilled work visa... So mind numbing and career stifling that I find myself her on HN wayyy more than I probably should be :/
I've mentioned my concerns with the PM and a tech-lead and get told things to the tune of 'well your other colleagues didn't have a problem...'
Been here a month now. Currently trying to build up the courage to write something to the boss but I'm not sure if that's a good idea.
This isn't sustainable, these antics of these companies are basically negating any positive thing you try and do for the environment
Pharmaceuticals, for instance.
For me the old phone would be pretty painful. It's an iPhone 4 with 32 GB storage (max), 960×640 display, 5 megapixel camera, and no LTE. It's got a 32-bit processor with half as many cores as my current phone, running at less than half the clock speed.

Not all technologies improve at the same rate, or at a steady rate over time. But the optimal replacement interval of goods on average seems to be decreasing.
How to Create an Effective Wireframe That Will Simplify Your Design Process
Well put. And I'd add that insurance is specifically about transferring risk from people who can't handle it to those who can. (Financial derivatives can easily be used to do it the other way.)

You could also say that gambling is net negative sum, while insurance is net positive sum. The positive part being the long-term economic benefit of people not having their lives harmed or ended by low-frequency, high-expense events.
Uber president Jeff Jones quits, over ‘beliefs and approach to leadership’
Feels like Uber's next fundraising event may be a down round...
Could you link to the probability lectures you're referring to?
The depth of the stack is not a very good metric for code quality.
Which is why the PoW change is being investigated now. If china-coin attacks the bitcoin network, they'll initiate an ermegency PoW change, and make all of their hardware obsolete.
Not necessarily. If you haven't been there for long (and it's not on your resume) it might not even be necessary to mention them directly. It could take a bit of linguistic technique, but if you frame things in such a way that describes what role you were hired for and what role you were given, I don't think anyone could fault you for being dissatisfied.
5A+LD+(+D/2+++W+++Q+)
/r/btc is a forum paid for by people who want to fork bitcoin, and their moderators are paid employees of Roger Ver. You can't believe a word they say.
I'm looking for a React guy. Remote work is fine as long as you're on USA timezone.
I'll be the judge of that.
In my case it wasn't the ice maker itself, but the plumbing leading up to it within the refrigerator. I finally ended up turning off the water supply after my DIY repair broke a second time.
Bored to Tears by a Do-Nothing Dream Job (2015)
I'd go to your boss and respectfully say what you've said here regarding your interview and intentions. "Sir/ma'am I was hired to do job X and I find myself doing job Y. Is job X still a realistic goal here? If so, when do I start? [a date should be the response]. If not, I'll start looking for job X. I don't want to burn the company, so I'll continue to work hard here until I find the job, and I'll keep you posted on the progress."

Some folks might say "no way dude, they'll can you" but I doubt it. I think most bosses would appreciate the honesty. And if they do you wrong, you still have your integrity and that's better than one more paycheck.
Some one will come up with an external adapter that will do the conversion. Generally saw this with the PS/2 <-> usb mouse. usb <-> ethernet etc.
I think the right/wrong is in the apparatus. Gambling is usually repetitive and involves operative conditioning, which can be addictive.

Insurance is too but to a much lesser degree. If I buy fire insurance and my house burns down, I get rewarded (as in operant conditioning). But only punished when my house lasts until I die or sell it.
BU and the new variant of the chinese cabal of bitcoin miners BitcoinEC have a key consensus change implemented in them called 'Emergent Consensus'

Emergent consensus lets miners decide, through force of hash, the block size. This provides for them an incentive such that, as they increase the block-size, it leads to the nodes not being able to be run except with massive connections to the other nodes and miners. The miners that are closer (in bandwidth) to the other nodes, will have more time to retrieve the transaction and block data. Nodes and miners on slower connections will further deplete, as they can't source the data fast enough. This will also mean that communication between miners will favor miners that are closer together.

This means, by design, bitmain will be able to force ALL miners and ALL nodes off of the network, and every node and every miner will be housed in bitmain data-centers. It is a hostile take-over of the bitcoin environment by a chinese company that has all the markings of a state-sponsored action.
"both gambling and insurance are slightly-negative-expectation plays with occasional large payoffs"

When you take in account that personal utility functions aren't linear, insurance and gambling are no longer slightly-negative-expectation, but usually positive.

In other words, if U() is your utility function, U($1M) != 1MU($1). For most people, U($1M) > 1MU($1) and U(-$1M) < 1M*U(-$1).
You skill will not rot if the code base is old and bad, your attitude does. It's just not your conform zone, it's ok to avoid it, but you will learn a lot if you don't. Spend some time to understand the business logic of the legacy code by doing code review, debugging...etc. and see if you can improve it by back porting the new technology, there's always room for that.
Patent lifespan of 20 years maybe was ok in 1886, but it's too long now, when multiple tech revolutions can happen in 20 years.
No, no what? Do you have counterexamples where established businesses don't have to deal or interface with legacy code? If so I want to work at this magical enterprise.

According to OP this company has been around for 10+ years. It'd be a miracle if they didn't have legacy code.
Sometimes stop signs are used because of interference with other drivers (check it's safe to checking other drivers), sometimes they refer to pedestrians (check it's safe by checking pedestrians), sometimes they refer to some other kind of danger, for example it could be something like speed bumps. Basically a stop sign is there to tell you to stop (even if it's not really necessary) and watch out for something (without telling you what).

There exist all sorts of signs that actually tell the driver what to watch out for, and make the right of way situation clearer. But in North America, a stop sign is used in most situations.

Four-way stop signs are another form of silliness. They often happen in residential areas where small streets cross. In Europe you'd have 'right before left' rules that only really matter when cars actually meet; in North America you have to come to a complete halt, constantly.

I'm no driver, and am not a big fan of drivers or driving in general. But I kind of understand why drivers are so aggravated here.
Your statement clearly states the essential distinction.

A more concrete way of stating this is: the purpose of gambling is to try to earn an outsized return, while the purpose of insurance is to make you whole in case of loss.
Sounds like it's time to get out then. I don't know how hard that would be as you said you moved cross-country, so you could be anywhere (in the US I'm guessing). Remote work is always handy.
How do you figure that gambling or insurance have negative expected value?
I was hoping for the deconstruction (or reconstruction) of one of the many rendering engines already out there - there's lots to talk about! This doesn't have much meat - reads like an incomplete UML diagram. My experience is mostly porting/profiling/optimizing graphics, not writing entirely new pipelines, but I'll chime in on a couple points:

>> Passes can receive as inputs: [...] The previous Pass outputs in the form of textures in memory (Render Targets)

This feels a bit arbitrarily limited. I find rendering passes more 'graph-like' than a pure linear pipeline. For example, you might render some shadow maps - some of these might be bound to a single camera (e.g. for traditional directional cascading shadow maps fit to the camera frustum), but other shadowmaps could easily be shared between multiple viewpoints (e.g. point light dual paraboloid shadow maps). And even your 'per-camera' shadowmaps might be reused between multiple viewports for e.g. two very similar eye cameras in VR, whereas other parts of your scene will need to be re-rendered wholescale per-eye (unless you start implementing e.g. nVidia's single-pass multi-viewport rendering - how does that fit into this UML diagram?)

And then of course you might have multiple passes reading from the same gbuffer(s) or the scene depth buffer, or even the result of previous frames (temporal anti-aliasing and motion blur), and other things that aren't really per-camera (dynamic light probes for reflections, etc.)

I've also 'fond' memories of bugs from the magic configuration of passes, inferring inputs and outputs from their position in a list. I'd lean strongly towards being completely explicit about inputs and outputs. It's more dumb code, but it'll make things beautifully straightforward to understand, modify, and fix.

>> The basic concept of boiling things down into passes with inputs and outputs that can be managed as data

This has been overkill for every single one of my hobby projects, just more cruft to wade through, a solution searching for a problem. At least one of the more graphically simple professional titles I've worked on didn't even bother with this, and I didn't miss it. That said, the professional rendering code I'm most familiar with (having ported it from D3D9-only to multiple other rendering APIs) did have something similar, and it seemed reasonable enough. If you want to go "crazy" exposing control of rendering passes directly to your artists to tweak with scripts or other UI, it's a reasonable thing to represent. It can also make adding some debug tooling easier (e.g. profiling information about different passes, adding debug views of the outputs of individual stages, etc.)

A nifty graphics study of DOOM: http://www.adriancourreges.com/blog/2016/09/09/doom-2016-gra...
But in some MOS and some fields and some clearances seeking help is career suicide.

This is a truly toxic misnomer - and one that needs to die. As a former CC of one of those types of units, I can tell you that the only way that would happen is if your mental health issue caused a real world problem that created a chance that you could be vulnerable to coercion from a FIA. I've never heard of someone who got read off because they were diagnosed with something - it's always been in conjunction with them doing something illegal or vulnerable to exploit.

If an SCI troop seeks counseling, either through Doc or something like MIL One Source, you will have no issues, even with a diagnosis. Once you've passed through screening, indoc, training and are in the game it would be ridiculous to take someone out cause they got rattled. In fact we always pushed it mental health heavily to all of the other spooks cause there are real mind fucks in playing our games that can get to people.

Second gaping hole is some of the support REMF (I was a REMF so I can use that acronym "proudly") have higher sec clearances than some front line.

In fact, it's most likely that a REMF (read: non 11/18/03) will have a higher clearance. Spot on too with the fact that a lot of non-standard troops are seeing the worst parts of the shit. Aside from SOF, Docs, Spooks and Engineers have been taking the brunt of it the past few years.
You would need to find exchanges that recognized the china-coin tokens. 97% of nodes in the bitcoin network currently enforce the same consensus rules. As soon as bitcoin forks, they will no-longer understand, nor view, the tokens in their forked crypto-coin.
We in North America have been paying the Dolby AC-3 tax for the last 20 years. Dolby successfully weaseled AC-3 as the multi-channel audio encoding standard for MPEG-2 DVDs. This is despite the fact that MPEG-2 already has a multi-channel audio encoding (AAC). DVDs in Europe utilize AAC audio.

Thus every DVD and DVD player sold in N. America has to license AC-3 from Dolby.

The best way to steal from people is to do it without their knowledge.
That is correct, but disability insurance is far more important than life insurance.

If you die, your spouse can marry again, your kids will be able to work at some point and so on, there are no additional costs. If you're disabled, it becomes a massive, long-term, cost burden.
Money doesn't have a linear utility function. The more money you have, the less the next $X are worth.

This means, even for "0 sum" games where there isn't a house taking a cut, gambling will typically have an average net utility loss. You make as much money as you lose, but that's money worth more when you lose it then when you make it (past the first $epsilon).

Insurance on the other hand will typically have a net utility gain despite being a net dollar loss. When you "win", you would otherwise have very little money, so the money is worth a lot of utility. When you lose, you have lots of money so it only costs you a small amount of utility.
There's another, more direct reason: insurance is only supposed to allow you to 'hedge out' risks that you already have, whereas gambling or speculation is unrestricted.

In the case where your house burns down, you're 'rewarded' in the insurance contract, but you should be close to net indifferent (after insurance) over whether your house burned down or not.

That's why we don't let people buy insurance on other people's houses -- it creates a perverse incentive for the insurance purchaser to force a certain outcome.
"..hope I don't get fired for underperforming?..."

What kind of passive language and thinking is that?

Everything is legacy once it is written.

Imagine you, the trailblazer, only having to write new code and not having to maintain the crap you wrote.

The actual problem here is your attitude and way of seeing things. Legacy? Sucks?

Fucking write a better version and show some initiative instead of just hoping of being granted the opportunity to work on "new shit".

Millenials these days.
Insurance doesn't ever really "reward", it just makes whole.
I find it impossible to replace a legacy system without first understanding the legacy system. It's easy to say "X is old" or "X sucks at Y" but keep in mind that applications have a strong survivor bias. Ask yourself, "what does X do that is awesome" or "how has X lived this long" and you'll find a lot of hidden scars and requirements.

Start documenting those requirements and create a plan to map those to technologies that you prefer. Understanding how to successfully migrate platforms is a learned skill, and it's going to become useful again when React is no longer en vogue.
Making value judgements on transactions between consenting parties is a fraught endeavor.
The conjugation of japanese verbs are non negotiable - it has to be there for you to make any sense, and I don't think OP was claiming that you can move(?) how a verb is conjucated - just that the subject and object order doesn't matter (which is correct). The tense of the verb or conjucation of the verb has nothing to do with that.
Have you ever moved from an uncomfortable position and regret it later?
No, after the hard fork has settled Unlimited will simply "be" bitcoin. There's no need to change wallets.

On the other hand if the current "Core" development team prevails with their much more complex "Segwit" soft fork you'll need to create new wallets to use it and you'll have to transfer your bitcoins from your old wallet to it.
Google Rolls Out Chrome 57 to Android After with Exciting New Features
Without the context?
Why is everyone quibbling with him about that. He just wants to express his opinion that the codebase is very bad in a more colorful way than by simply calling it doubleplusbad. Let's just take his word for it and move on.
I think AC-3 patents expires sooner than AAC, right?
I will look into it
The answer to the headline question is in the book "how to lose a million dollars", which I recommend.

The author describes four classes of financial risk-taking
1. Investing
2. Speculating
3. Market making (I think)
4. Gambling

Investing is risking capital with a strong probability of maintaining the principle while receiving a reasonable return.

Gambling is when you have a negative-sum chance at keeping your principle.

As a result, one person with limited information and portfolio diversity could "gamble" on apple stock while another person with more diversity is "investing."

Fundamentally, they're more about information and risk than anything else.
I'm the exact opposite. Back in my 20s I was surrounded by countless distractions: bar-hopping, parties, girls, video games, you name it. Sitting down and applying myself to learning something took tremendous effort.

Now that I'm in my 30s though, I have way more focus. I can easily sit down and work on a project for hours at a time. On top of that, I have way more motivation, because I have a very good idea of what I want in life and I know how to get there.
Well, I don't see any problems with the logic part. Receiving, filtering, transforming, and notifying someone else about incoming messages (would probably do it in a few threads, sending messages between each other).

For the UI part: no wonder, Go, at least currently, is useless for UI's.
I think the basic truth to work off of here is: "Shit got real."

Yes, you can step away, in the figurative and literal sense. In many possible worlds this may even be the best plan, if you have no real agency over the code. And you got lied to. It'd hardly be the first time someone has been convinced that the work would be cooler than it is.

But -- you also have to decide if this is an opportunity in disguise. Stories of folks who gradually build ownership over the creaky "legacy" codebase and polish it up with Sisyphean refactoring, until it shames the "rewrite", are out there, and they're real.

On the other hand, fixing the legacy code may be one of the hardest things you can do in software architecture. There's no sense of joyous freedom to it, just correcting of old mistakes. But if you did that, and published documentation to evidence what you did and how, lots of folks would want you - and not necessarily for the task of fixing their own crusty code.

So there is an opportunity here, if you can find a way to sneak it through the management, which has surely decided on the balance sheet that the code is a "deprecated asset" and will not want to hear about new ideas. In fact, to maintain it you don't want to present anything as a "new" - you have the much harder task of justifying every small change as an opportunity to improve the debuggability - to get the callstack down from 20 deep to 19 deep, to remove a superfluous parameter, to improve turnaround times, to reduce the code size by a few lines, or something similarly miniscule, but which might add up over time into real understanding.
> Whenever I propose a design for something, I'm told to do it the fastest way which is usually a bad hack.

And why do you agree?

One of the differences between professionals and other workers is that professionals are experts in how to do their work. If I tell my doctor to just write me a prescription because I said so, she'll just scoff. I can make requests, but she decides what will happen and how.

Especially if you're already likely to quit this job, then you don't have much to lose by insisting on using best practices. Sure, you have to honor their desire to do things reasonably quickly. But you don't have to keep digging the hole deeper if you feel it is professionally negligent to do so.
Ftrace: trace your kernel functions
So we need a generator of racist random text? Let me fire up TempleOS.