thesmallestcat

> the controversy arising

Could you be more specific? Are you talking about a Hacker News thread or something else?

You shouldn't have replied. You and the other guy are both out of your gourds, and you don't understand how crazy you look.

I sort of doubt that. In practice, it seems to incentivize influencing policy to drive up healthcare costs, with little regard for patient outcomes.

Before the tire fire that is rvm became "standard", it was normal to just download the version you needed and build it from source. There's nothing forcing us to use crappy, obscure tools like rvm and rbenv. And I agree with you on all points.

Forget public healthcare, I'd gladly live in Canada for this protection!

Great advice! I'd venture that managing large files is an unsolved problem. It's a hack in most version control systems, and uploading/downloading files from a host, even S3, is a slow, serial process. Same for checksumming. Network speeds have more than caught up, and large files are a frequent process bottleneck. Something that makes it easy to manage and consume large files could be a big deal. It probably would require a new application protocol, maybe even a new filesystem similar to XFS.

Static website generators.

> Traditionally, there are two ways to study a page like this:

> 1. Type out every line of code

> 2. Copy+paste the code from their website, maybe play around and make small changes

Um... wut? How about:

3. Read the code. Think.

If you're reading programming books as practice, and think you're supposed to copy the code examples to learn, you're doing it wrong. If you need eval() to figure out what's going on, you need to spend more time practicing the basics, then step up to the book.

uMatrix is your friend.

I think it's sort of like first-class flying. There's no logistical reason for not boarding the plane rear-to-front, but you can get people to pay for the privilege of being first, so why not? Non-Prime customers are second priority, and expected fulfillment is adjusted accordingly.

It's destructive, and Amazon can get away with being a crap book store now. I've ordered many thousands of dollars worth of computing books from them over the years. In the past six months, and especially the past couple months, "new" books come with massive creases, scuffs, and dents. Or a bad print with hard-to-read text. A copy you'd never buy in person, or B&N would knock something off the price because of the damage. When you paid $80+ for the book, it sucks.

I haven't been returning the books for two reasons: When you get ten books in the mail and eight of them are damaged, and some of them are immediately useful, are you really going to go through Amazon's return process for all of them, photograph each one, package, ship, etc.? Second, I just know that if I do this, it will contribute to some poor schmuck losing his job at a fulfillment center, or some LAZR driver getting taken off their route, because DATA-DRIVEN.

Now I just order used books, sadly most of the vendors are on Amazon so I can't really take my business elsewhere. At least I don't feel quite as ripped off when my "Like New" book arrives in "Good" condition. Even sweeter, those vendors don't sit on my order for a week for funsies like Amazon does if you resist their PRIME offering.

Has anybody else been receiving damaged "new" books from Amazon lately?

This is a known footgun of promises. But if you are using async/await, uncaught error in the promise chain is the same as uncaught error inline.

As a fallback. I like LISPs as much as the next guy/gal, but editing the AST by default is too low-level. The importance of paredit is a language smell in my opinion, not something to aspire to.

This is like saying running for exercise is a waste of time because you could be driving instead. It's not about knowing a particular sort algorithm. It's about the discipline of solving performance problems in the small. Knowing how quicksort works isn't that helpful. Being accustomed to the thought processes that led to the development of quicksort is important in any non-trivial programming activity. I'm not writing Google-scale services, but I regularly encounter algorithm design problems on the job, and they're never the exact algorithm you studied for some white board exam. I think the author is approaching algorithm study with the wrong attitude.

They destroyed the XPI/XUL platform and thousands of hours of work that went into those extensions. Now Firefox is a much worse version of Chrome, no reason to use it except for dubious ideology preferring Mozilla. Sacrificing the one network effect that kept Firefox relevant was a brilliant move.

Smoke signals here, can't trust the postman either.

There's a good chance somebody on the other end's going to run your program without really vetting it. Especially if you include a convenient "test runner." Not a bad attack vector, just get your alias past the first screen and you might get arbitrary execution inside their firewall on a host with access keys and the like.

Any, really.

That's a sad way to think about life. Back of the envelope math says I can be pretty happy with way less than that, different standards and all I suppose.

I've had similar experience finding on-site work in a healthy market as I have as a remote worker. I don't think parent's advice is sound, claiming that software eng. is a dead-end path for most, with a five year fuse. Clearly if you're not excellent or willing to move to a city with jobs in your industry, you're going to be in for a rough time. Not specific to software eng.

Let us know how a passport.js hiring filter works out long-term.

Few if any of the 300 applicants were overqualified for that garbage opportunity. Can you describe on how they were overqualified? List a bunch of certs and techs? Good programmers aren't fighting over scraps for underpaid government positions working with JBOSS, they get snapped up immediately when they hit the market. Five years to saturation? Yea right.

Readers who just deleted emacs in despair should keep in mind that parent is hiring for Danish government position, not exactly the hotbed of software development or skills demand.

I think there have even been studies that correlate all protein intake (regardless of source) inversely with longevity, so I try not to get too worked up about not having a meal with a lot of it. Beans, lentils, peanuts, etc. have a decent amount of protein, but even bread has protein and nowadays it's not hard to find high fiber, high protein bread. I love meat so this is all difficult, and I hope to eat less over time. I think it's a balance between the short-term benefits of protein (energy, muscle) and the long term effects of high protein consumption (tough on your organs).

Protein is good, but not too much from meat:

https://www.ncbi.nlm.nih.gov/pubmed/27479196

> CONCLUSIONS AND RELEVANCE:

> High animal protein intake was positively associated with cardiovascular mortality and high plant protein intake was inversely associated with all-cause and cardiovascular mortality, especially among individuals with at least 1 lifestyle risk factor. Substitution of plant protein for animal protein, especially that from processed red meat, was associated with lower mortality, suggesting the importance of protein source.

Shady gatherings in Ibiza, visits to BSDM clubs, and here I am rebasing commits.

Not only that, but [some film] last summer smashed box office records. Yes, it's the most popular film ever.

This is exactly the attitude I'm talking about. Employees take risks too. Time has its own opportunity cost risk. and it's felt more by employees slaving away at company initiatives than by the ones who dream up those plans. If I've wasted my time as a business owner, I have only myself to blame. As an employee, there's a real risk of wasted time and the accompanying loss of worthwhile pursuits.

The other obvious risk is that of unexpectedly losing your job. By and large, employees are not financially independent and are at the mercy of their employers. Ownership has the intel and leverage to plan a graceful fall for themselves. Employees are typically terminated with zero notice, while it's a faux pas for an employee to do the same.

Another risk is that an employee will find real conflict with an employer, and stare down the barrel of a well-funded legal team. People have had their lives destroyed by it.

Most people aren't getting equity at all. Of those who get equity, it's meaningless. The lion's share of profits go to ownership or shareholders.

I'm talking about uneven share of profits. Ownership takes it all. We are paid the minimum possible in most cases.

I wouldn't fault any employee for slacking off, because almost everybody is underpaid, has no real share of ownership, no loyalty... it's an adversarial relationship of the employers' making.