skysight-inc/HackerNews huggingface dataset:
I never understood the ORM hate/bashing. It's like the framework fanboy paradigm. "I love framework X, and framework Y sucks!"

They are tools built to help solve a particular problem.

ORMs are great when dealing with CRUD operations on entities and remove the need to write tedious boilerplate code every time. On the other hand, ORMs can be misused and cause all kinds of performance related problems. Most obvious use-case is developers that don't have much experience with databases, and instead of choosing to perform processing of data in the database run-time, they fetch data through the ORM and write poor performing code riddled with business rules in the application layer.

I think it's good to take a step back and understand that the ORM is a tool, which when used for the purpose it was designed for, works well.

Complex joins and queries can still take advantage of an ORM. One example is using materialized or non-materialized views, which can then map to an Object using the ORM to query it.

That way the bulk of the processing is done in the database runtime, and simply accessing the object is done through the ORM.

There's also the separation of concerns. A seasoned developer will opt for creating a well defined schema, and baking business rules into the database layer, because he knows that a well designed, and highly normalized data model will outlive any application where the business rules are housed in the application layer.

All things considered, I do love the ActiveRecord ORM design-pattern. I've worked with hibernate, JPA, and some other ones in the past, but ActiveRecord as employed by Rails and Django, is still my favorite.
I've seen TDD used once really well in a university setting where it was used only for shared libraries/services that could be used by multiple other teams or departments but not on individual (front facing) projects.

Probably because only the best developers on the team worked on the shared services it eliminated the refactoring issue as well as ensuring shared services could be a lot more reliably and safely updated.
I'm guessing because the secretary problem doesn't have this twist:

>Dating is like enterprise sales. When your customer goes for a competing, more compelling product, you’re never told and you don’t get any feedback.
I think he means "because liablities", and then being unable to find a counterparty willing to take a high risk for a small premium.
Ofc China does not want HK to be free. China found out how to get "rich" without losing control. They want exactly the opposite of what makes HK HK. It's just sad that many strong economies feel like they need / want the growth based on chinese consumption and trade and are feeding this undemocratic behemoth.

What is scary is that China is actively promoting expansion by resettling ethnic han chinese.
There's not enough surface area on a car to power it in motion though. With a covered roadway you at least get the extra square footage from the empty space between cars. Still probably not feasible but it gets mildly closer.

On the whole idea powering cars wirelessly while they drive just doesn't work on mass scales. It's going to be massively expensive to build it out.
This was always one of my favorite episode names: https://en.wikipedia.org/wiki/Simpsoncalifragilisticexpiala(...
Anecdotally, the cleanest, most maintainable code I have ever seen at work was the result of a TDD-mandatory project.

Equally anecdotally, that was the most efficient project management I have ever seen at my workplace.

Economically, our branch office was shuttered, and all employees laid off, just a few months after we delivered it, for almost entirely unrelated reasons. As it turns out, the only reason we did the TDD project at all is because our primary contract had not been renewed, and it was a lower-value contract. After it was done, we didn't have enough work left to do. But more importantly, the main office didn't have enough work to do, so they slurped up our dregs, kicked us to the curb, and sold themselves to a bigger company.

Perhaps the lead dev saw the writing on the wall, and wanted to make a showpiece to boost everyone's resumes. Perhaps he foresaw that one of the several companies we might end up with after the diaspora might get maintenance responsibilities, and that person shouldn't hate their former team for writing crappy, unmaintainable code. Doesn't matter. Did it once, and it turned out great.

I still get nostalgic for it sometimes, when I am working in the sloppy mess I am currently assigned to.
The best solution is the complete outlawing of health insurance. It'll take riots for that to happen.
I guess it must be legally valid because a judge said it, but how does that make sense?

One could even argue that the public defender's clients were affected, this impacting him.
It should be a requirement, just like math is. But don't get upset when we're not pumping out software developers any more than we pump out mathematicians.
To be fair to doctors offices, this is in part because some insurance plans (Medicare's the biggest offender, but then again Medicare's the biggest everything) pay doctors below cost for certain procedures. Doctors cope with this by systematically overcharging other patients' insurance companies when they're reasonably sure the patient has already hit their copay for the procedure.

Essentially, health insurance for the poor isn't formally subsidized well enough to make it actually workable, but doctors have professional ethics that disincentivize them from refusing care. So the system has evolved a clumsy, ad-hoc mechanism for wealthy patients to cross-subsidize poorer ones.

American health insurance sucks.
Lack of unemployment insurance makes working for risky companies risky.
On the other hand, they can hardly sell the work to anyone else, so you'd think that some sort of sane compromise could be had.
I love how you say Africans would have been better under benevolent European rule and also say Brits should free themselves from European rule (however good it is), in a single comment.
TestCafe now supports headless Chrome
In terms of connectivity, we deal with a similar problem here at CloudWalk to process payment transactions from POS terminals, where most of them rely on GPRS connections.

Our network issues are nearly 6 times higher (~3.5%) due to GPRS, and we solved the duplication problem with an approach involving both client and server side.

Clients would always ensure that all the information sent by the server was successfully received. If something goes wrong, instead of retrying (sending the payment again), the client sends just the transaction UUID to the server, and the server might either respond with: A. the corresponding response for the transaction or B. not found.

In the scenario A, the POS terminal managed to properly send all the information to the server but failed to receive the response.

In the scenario B, the POS terminal didn't even manage to properly send the information to the server, so the POS can safely retry.
You're choosing to focus on superficial similarities (checkpoints!) and completely ignoring the wildly different contexts that Hong Kong and the West Bank, a place that I was standing in literally one week ago, exist in.

-Political relations are a function of wealth. If Palestine were a wealthy and economically developed nation with a large number of international connections do you think their relationship with Israel would be quite the same?

-Do you think not having a military/international recognition is the same for a faux city-state and for an occupied territory??

-Have you considered how living in a shithole and being denied economic opportunity due to not being able to travel freely might be just a tiny bit different from being mildly inconvenienced when leaving the financial capital of Asia for a developing country (yes, mainland China is very much a developing country) with a fifth of your GDP/capita?
@amitmathew Thank you for sharing this!
I am a kind of an adult who doesn't have stuff to do on lunch. Not only am I eating lunch, but I plan activities like what you mention to times outside of work. At most I'll add in a visit to the post office. If I have to cash a cheque, that's a Saturday morning.
I.e. where the smallest segment of their market goes.

I have your same problem. But I don't think it's a problem for them.
Wait, what about canada's maple syrup is militarized?
Hi all! I'm the person who made this. If you'd care to share your thoughts, I plan on watching this thread closely today. :)
Well, exactly the same problem applies to hydrogen-fuelled cars – almost all hydrogen production is still done using steam-reforming of fossil fuels, leaving CO2 as a byproduct. It might be possible to ramp up more carbon-neutral methods of production, but you face the same problem with electricity, so…
Sounds so cool, what are the major milestones that you plan to reach with Minoca OS 0.4?
100% of the loss does not end up in the road surface mostly it's radiated into space.

As a sanity check at highway speeds it takes ~30HP to maintain speed or a loss of 10HP or 7.5kw over ~60m (distance from one front bumper to next) x ~4m approximate width of a lane = 30w/meter which is a non issue. Lower speeds need less power, but can have more cars.

Further, not every car needs 100% power as batteries are still a thing, this is just for the subset of long distance traffic. And if you limit things to say 75% of a cars power demand that's still 4x the range.
It's fair if it's the strategy as envisioned by the company's leadership. Employees of that company not sharing that vision does not change that. If anything, the employees should bear some culpability for working in support of that vision, even if they don't agree with it.
Group 1 is mostly women and group 2 is mostly men.

At least in my experience.
Yep, everybody is paying for them whether or not they're into sports http://investigations.blog.ajc.com/2016/09/12/report-tax-fre...
> It would be great if there was a means for people to sell technology like this to their employers.

There is, you can quit and offer to build/sell/license the solution to your previous employer. Of course this would mean incurring (potentially) substantial risk, that you might lose your salary, they might not be interested, they might sue you, etc.
Witchcraft and Radioactivity right?
Actual link: http://fd.fabiensanglard.net/doom3/pdfs/johnc-interviews.pdf...

And it's press interviewing Carmack, not job interviews conducted by him.
It's probably a mistake, because as much as I like Foundation, it has some issues.

For starters, most of its themes have already been stolen by other works / franchises. How many kids are going to accuse Asimov of ripping of Coruscant when they see Trantor?

And it reads much like a tightly-written Dune. We all know how that turned out.
Should also be stated that a significant amount of energy is lost in carrying electricity over distances (over power lines and while at rest in batteries), which is not the case for H2.
That's fair, though it does seem like a fair number of people at Mozilla don't actually know what their reporting chain is nowadays yet alone who needs to approve any expense.
sure, if you assume that everything can fail, then it doesnt help to store the list of messages you've seen

but if you can persist a monotonic sequence number, thats gets you pretty far. we use tcp all the time even though its has no magic answer to distributed consensus (and uses a super-weak checksum). 2pc doesnt guarantee progress and/or consistency either and its pretty effective.
I wonder how likely it is you'll get a good discussion about the pros and cons of reusable packaging when you start off by calling people hypocrites?
It's worth noting that the next major Kafka release (0.11, out soon) will include exactly once semantics! With basically no configuration and no code changes for the user. Perhaps even more noteworthy is this feature is built on top of a new transactions feature [0]. With this release, you'll be able to atomically write to multiple topics.

[0] https://cwiki.apache.org/confluence/display/KAFKA/KIP-98+-+E...
A lot of good answers here. A few straightforward ones:

- Because healthcare providers negotiate different rates with providers, so the "list price" differs by your provider and plan.

- Because your personal cost is unknown to the doctor, as it would depend on factors between you and your insurance company (like deductible met), coverage types, etc.

Now, these are both solvable problems. And I agree with the sentiment of other posters here that it's predatory that medicine is one of the few fields where you simply don't know how much something will cost until you get the invoice.
If the chinese economy continues to grow faster than america's (not a given), at some point we may need to onshore those jobs again.
> I've also seen people mangle well-factored but untestable code in the process of writing tests, which can be a tragedy when dealing with a legacy codebase that was written with insufficient testing but is otherwise well-designed.

Have you read Michael Feathers' Working Effectively with Legacy Code? [0]

In his definition of legacy code it is any such code that has no test coverage. It's a black box. There are errors in it somewhere. It works for some inputs. However you cannot quantify either of those things just by "inhabiting the mind of the original developers." The only way to work effectively with that code base in order to extend it, maintain it, or modify it is to bring it under test.

This is far more difficult than it sounds with legacy code than with greenfield TDD for the aforementioned reasons: there are unquantified errors and underspecified behaviours. You can't possibly do it in one sweeping effort and so the strategy is to accept that tests are useful and to add them with each change, first, before making that change and using the test to prove the change is correct.

Slowly, over time, your legacy code base surfaces little islands of well tested code.

You have to be deliberate and careful. You have to think about what you're doing.

This is a much different experience than writing greenfield code. TDD is effortless and drives you towards the answer in this case.

[0] https://www.amazon.com/Working-Effectively-Legacy-Michael-Fe...
...a few Mylar balloons would do the trick and would definitely cause a major BES line to relay.
Show HN: Railcar – a container runtime in rust
0 indexed! :)
While I understand where you're coming from, and I agree with you to some extent, it's not really that simple.

While the majority of exploits we currently see in the wild are things I think the "defective lock" analogy works well for, there's a subset of attacks that would be equivalent to cutting the lock with bolt cutters.

In those cases, there are specially crafted tools that aren't exploiting a defective lock, they're destroying the basic premise that let the lock work.

I'd say that RowHammer fits that description pretty aptly. It's a cyberweapon. It's not an exploit.

It's so much of a weapon that (as far as I know, someone please correct me if I'm out of date!) there's still no known mitigation strategy that completely solves the problem. We have lots of partial mitigations, but nothing surefire yet.

So... it's both. We certainly have lots of defective locks, but we also have some very nasty tools that exploit some fundamental premises of our tech in clearly malicious ways, and were absolutely designed and implemented to do exactly that.
Programming the Amazon Echo to Speak with a Boston Accent
I find this creepy and weird. How could you possibly tell the love of your life (if and when you found that person) that they were nothing more than a toy in your little data harvesting exercise.
Exactly, should've used ML.
The article asserts that the problem fixed by the legislation is noise regulations that end up requiring wider supersonic engines to meet, which increase drag and cost of operation.

> So, any new legislation only needs to target lifting the over mainland restrictions

Which the legislation does...

> but you can't legislate-away the enormous costs involved in building and operating supersonic aircraft.

To the extent the costs result from legislative mandates, and are not inherent in building supersonic aircraft, you obviously can.
Even with that I still don't give doctors an excuse. There are a bunch messed up incentives there too. Such as doctors recommending more expensive drugs, or giving me coupons to buy said drug. I'm assuming there's money exchanging hands there too. Not sure if it's with doctors directly.

But the end result is that I simply cannot 100% trust any advice I'm given.
Interesting article, but in the context of serious process and scientific methods, the rape statistics quoted in the article is the exact opposite. The "1 in 5 US women is estimated to be raped before age 25" comes from a single study where they did a voluntary survey in one US university campus. It reflecting of the set of students during that year on that campus that decided to answer that survey. The national average today could be 1 in 5, it could be much more or much less.
There's also a race condition in there when you receive the duplicate before publish_and_commit is done doing its thing -
assuming they're not actually serializing all messages through a single thread like the pseudocode implies.

What they've done is shift the point of failure from something less reliable (client's network) to something more reliable (their rocksdb approach) - reducing duplicates but not guaranteeing exactly once processing.
Having a single pool doesn't kill the 'actuarial' part. Fixing premiums by law does. As does the fact that health insurance is more "prepaid medical care" than "insurance".
Hi, don't mean to interrupt anyone, just wanted to ask: why hasn't anyone made the common lisp hyperspec a prettier, more navigable and tooling friendly yet?
https://en.wikipedia.org/wiki/Rational_ignorance

https://en.wikipedia.org/wiki/Opportunity_cost

https://en.wikipedia.org/wiki/The_Market_for_Lemons
I do think there's a lot of value in teaching logic and algorithms as a system for thought. Coding might be a more direct way to get to it than, say, calculus, which is what is generally used.

But teaching kids java and databases is probably not the right approach, and is definitely only happening because Oracle wants to stay relevant.
> Your saving rate is going to be higher on 50k/year in eastern Europe than 100k SF salary.

Yeah, except that the going rate for a good junior developer in SV is about $150k (Google, Facebook) and in Romania it's $20k. I recently moved away from Romania because while I could find a job in Western Europe paying more than $100k, there was no way to find something in Romania (or remote) paying even 30% of that. And not for lack of trying.

Also, $300k a year in SV is much more achievable than $100k in Romania or Bulgaria, and with that sort of money you start caring about other stuff than housing (luxury goods, exotic vacations, investments etc.) whose stuff doesn't depend on location.
This book http://rob.conery.io/2016/07/03/imposters-handbook/ is written specifically with you in mind.
I have very mixed experience with print-on-demand too. Bought a Microsoft Press book that turned out to be printed on demand... the print quality is bad (looks like a printer set to thrifty "save toner" mode). Together with their choice of a rather anemic font for the text, it's just not nice to read at all. The bad legibility really impacts the joy of reading it.
I suspect that their degree of extreme nationlism is inversely related to the amount of time and # of family members who are here.

That's why a few other members say their anecdotal evidence hasn't seen that much extreme pride - I suspect the people they are talking about have spent 5-10 years here at least, and arrived here in the late 90's-early 2000's when China was still weak and not as rich.

Try talking to new grads and mid-late 20's who are here, who arrived here when China became rich. They are very very prideful. You won't see it if you're an obvious American dude; they will not show their colors.

Obviously you do not encourage westernization by blocking them off. The US strategy is probably to encourage them to be here to gradually acclimate them to western liberalism over time, where they can go back eventually as the ruling elite and gradually shift attitudes in their country.
That's the caveat I mention in my second paragraph.

But yes, if the tests are well-designed and built with actual real-world experience, I do treat them like real client code. Someone looking to use the library should be able to read the unit tests and have a pretty good idea what code they need to write and what pitfalls they'll encounter. And when the library is redesigned or refactored, the tests are first-class citizens; they aren't mindlessly updated to fit the new code, they're considered alongside other client code as something that may or may not have to change but ideally wouldn't.
Google Is Still Mostly White Guys, So They Hired a New VP of Diversity
The bill shows they asked for $X, but the doctor already has a negotiated agreement with the insurance company that says they will accept $Y for the service.

Additionally, if you inform the office you are paying the bill yourself (without insurance) they usually give you a discounted price somewhere between $X and $Y.

In other words, almost nobody is paying the list price of $X. It's not really a meaningful number.

(And, as others have pointed out, the weak US dental insurance market means that actually dentists are pretty up-front about pricing in my experience.)
I wonder how they partition by "messageID" they use to ensure that the de-duplication happens on the same worker. I would imagine that this affects their ability to add more brokers in the future.

Perhaps they expect a 1:1 mapping of RocksDB, partition, and de-duplication worker.
> Going on 150 dates and not finding a single match tells me that you are shooting outside of your league.

Total nonsense attitude. You should never feel "outside of your league" for many reasons, particularly since you never know who you are compatible with. Don't be afraid to aim high in a partner.
Also -- here is a good moral thermometer:

"PS: I will not open-source the code since it could be used to hurt people, but I might share it if you ask nicely."

If you write code for fun (not commercially owned IP), and you are not willing to share it because 'it could hurt people', you might want to re-evaluate if you should write it in the first place.
Thew criticisms leveled at the Thought Leadership industry are valid, I think. I am much more skeptical that blogs, magazines, and small publications are the solution, or even a solution to this problem.

Gone unmentioned is the massive technical change in communication, and its effect on the actual way in which humans absorb and communicate ideas. I would look to the process of "going viral" as a literal embodiment of the problem. Things which are easily transmissible can achieve that critical mass to self-sustain. The Thought Leadership industry recognizes and exploits it, while the countermanding vaccine of rationality, criticality, and analysis is much harder to pass on.
I'm an Airbnb host who has been doing it for close to 6 months now. I'm currently renting out a studio apartment unit (around 550 sq feet) with an annualized rental yield close to 10% (one reason the yield is so high is because I bought the place 3-4 years ago while it was still under construction).

Airbnb is relatively straight forward. Check-in and check-out can be done via a key drop (typically the mailbox with a combination lock). The main thing you have to worry about is cleaning up after every guest... some guests don't know how to clean up after themselves. Get second hand furniture to save costs.

I really recommend that you try it. The business model behind Airbnb is quite brilliant.