skysight-inc/HackerNews huggingface dataset:
Although, I think what you plan to do with the data also makes a big difference. Which probably explains why opinions vary so widely.

For short-lived processes, like typical web applications and command line utilities – that load data from the database, do something with it, and then purge it from memory again – I'm becoming less and less convinced that ORMs are actually a benefit.

On the other hand, if your application plans to map the database data to memory for long periods of time, with the need to keep them in sync, then you're probably going to end up writing something that resembles an ORM anyway, and poorly at that. In this case a good ORM is beneficial.
Apologies. I intended "costs" to mean "costs to consumer".
Slack Integration for Managing Sprint Interruptions
I think git provides a sane level of abstraction.

I don't think it provides the most consistent UI or helpful help, though. Once you move away from "learning git commands" to "learning how git works" and kind of figuring out which parts the commands refer to has helped also. That's still terrible though.
My last git mistake was pretty terrifying. I decided to try and go back to an old commit on a project on my local machine after about a days work. Somehow I ended up making the commit I wanted to revert to a new branch, then somehow tagged that branch with the name of the commit making git get angry and decide that branch wasn't valid. Then continuing in my ignorance I reset to that branch and tried to checkout only to watch my source and resource files vanish one by one. Deciding the commandline had caused enough trouble I returned to a qgit window I had open, all the source files were still there and I could at least save them one by one. Better refresh the qgit window. Oh shit now qgit's mad at me too. Well there goes thousands of lines of code and about 3 months worth of work. Eventually,after reading gits cryptic error messages and a few google searches I figured out how to remove a tag from a branch and properly checkout an old commit. I was really happy when all those source files reappeared.
Database Systems, The Complete Book, any old edition is good enough and will be cheap.

It won't cover all those topics you mention. It will provide the background for understanding them because they all stand in relation to relational databases...you know, the basic theory you mentioned will give you the vocabulary to understand what people are talking about and some background toward understanding the advantages/tradeoffs of non-relational models like graph databases.

The other resource is The Red Book. It's free and online. But...though it covers current trends, most of the papers it contains tend to assume that the reader understands the relational model.
By the time you start to see r/w issues on anything that resembles a modern SSD, you're probably wanting to replace the overall device anyway
Exactly, break them apart while they still can.
The Affordable Care Act mandated use of EMR and heavily funded its adoption. Is there really not one fully implemented open source solution after all that money was spent?

Why does this project exist?
Fine. But most sane people would agree that Makefile generation is not a fun business. Autotools, anyone?

OTOH, generating YAML documents is easy. I already write code that generates YAML documents.

P.S.: POSIX make doesn't support concurrency. So, it's not fair to compare this purely to POSIX make.
BCash is a scammy altcoin
Even if it was true that the extra money paid for pharmacuticals in the US was funding 24hr drive-through pharmacies, that would still be an idiotic system that needs burned to the ground. People who need drive through pharmacies should pay for them. People who want to order things online shouldn't be subsidizing them. Hiding the cost in a pill helps no-one and is obviously sub-optimal.

Similarly, if you really wanted to subsidize pharmaceuticals for the rest of the world (and I'm not convinced you actually do) then again, hiding the cost in the pills, is a silly way to do it.

If on the other hand, you wanted to charge as much as you could get away with, and could pay off politicians in order to be allowed to take advantage of sick customers to line your own pockets then putting that in the cost would make perfect sense.
Just to give someone who doesn't live in these markets some idea of how volatile they are

> Goldman Sachs Group Inc. demanded some clients set aside collateral equal to 100 percent of the value of their trades, people familiar with the investments said last week. The guidelines are inclusive of other margin requirements such as Options Clearing Corp.’s 44 percent, required to clear contracts traded at Cboe, and the 47 percent CME is demanding.

> Interactive Brokers Group Inc., which has said it handled 53 percent of the first day’s trading in Cboe’s bitcoin futures, will require a margin of 50 percent for long investments, and about 240 percent for short selling, based on current rates

For a more typical futures contract like say wheat, its common to have to put up 5 to 15% margin. SO there isn't alot of leverage that you can get from these, which is almost certainly a good thing:)
Nothing about detached heads?
It is theoretically possible, as there are just a few moving parts ( 2 tweets worth ): https://twitter.com/ribasushi/status/939954274569785344

Whether it is feasible... the amount of calculations around secp256k1 is likely practically prohibitive for pencil/paper.
We added a $25 sun shade/hood type thing around it and the problem went away. Made the screen easier to see as well!
My analogy would be he is welding them shut.
I like the phrase "local-first" software.

It's been happening for a while:

https://qbix.com/blog/index.php/2017/12/power-to-the-people/
also https://github.com/keredson/DKO
I just assumed it's taboo since it's

1) almost never voiced by proponents of income equality despite being a very good example of extreme income inequality

2) frowned upon as a discussion point any time I've seen it
mentioned

3) and apparently it's frowned upon on HN as well since it ended up flagged down and hidden

I believe that fits the definition of "taboo" pretty well.
There are fundamentals: aggregate demand for money laundering and currency control evasion.
> Switching to DSL is not a realistic option when most of the country has broadband.

DSL is broadband. I've been using DSL for over 17 years (and, while away from home, using combinations of cable & satellite), and I watch plenty of TV & listen to plenty of music on it. It really does work great for me.
Assuming you mean legal judgement, I don't see why they'd be especially resistant. If the coins are held at an exchange then they are as reachable securities held that way. If they are in cold storage they are as reachable as a negotiable instrument (e.g. bearer bonds) or chattels for that matter (e.g. gold coins).

The case of H. Beatty Chadwick is also worth keeping in mind (spent 14 years in jail in contempt of court because he claimed that he had lost all his money right before a divorce and the court didn't believe him.)
Senators do a lot of underhanded stuff.

But, in this case, if it were put to a vote, probably the senator's constituents in Montana would want him to do exactly what he's doing?
I always fight for people really learning git, because that's when it finally starts to get good. And I always tell people that git is not the tool that everybody should use. Most people just need a simple data storage with diff management, like Dropbox or SVN.

But even after nearly 10 years, the pressure from the aint-nobody-got-time-for-that crowd is still there. I really, really hope that the git devs don't feel pushed to simplify and therefore depower git. Thinking turning VIM into the Windows text editor.
> it's about the laws that limit competition

In some cases it's not laws but simple entrenched ownership. If Google wants to run fiber on existing poles, they run into blockades by the pole owners or lawsuits by competitors who don't even own the poles but who can find a technicality about getting permission from the pole owner. The old 'possession is 9/10ths' factor.
The ACA reduced the rate of price rises, so it can't possibly be the cause of the price rises.
So he didn't increase the risk to the patient in any way, however small?

That is, a patient who gets signed upon and one who doesn't following the exact same procedure for the rest are at an identical risk?
I find the only people who find Git to be confusing or frustrating are the ones that try to adopt complex workflows. I've taught marketing and creatives to use Git with no issues.
>>no real reason

There is a very real and obvious reason. Thanks to the ("Affordable" Care Act, aka Obamacare), insurance companies have a captive audience of citizens (but interestingly, not illegal aliens) who MUST purchase their insurance product under threat of fine/imprisonment. There is no incentive to lower prices in this arrangement, and the insurance companies are immune from the pressures of a true competitive marketplace. The insurance marketplace is the equivalent of a prison commissary.
Not sure where the miscommunication is, but it looks like one of us is really bad at understanding English :)

Either way, I’m not a fan of the bro-mentality places(jobs/conferences) and I absolutely love conferences which make it nice for people (of any gender, orientation, race, culture, language) to attend.
Adopted a git GUI years ago and haven't looked back. I get looks sometimes, but I can't help but gloat when I can stage and unstage individual lines in less than a second.

I think anyone who uses the CLI is either trying too hard or hasn't realized the beauty of a git GUI.

Takeaways:

- My commit time is usually much faster than coworkers, with higher accuracy (less frequent accidental commits, etc.)

- I don't remember the last time I made an irreversible change to the repo, or had an "oh shit" moment. And that's despite using some interesting git features.

- Staging individual files, folders, lines of code, or hunks is easy. Makes maintaining multiple trains of though / addressing bugs while working on other code a non-issue.

- It's easy to keep files uncommitted for long periods of time intentionally, without slowing down my workflow.

- It's much easier to get an overview of the changes I'm making.
Spain, and its the same thing as the user from france. They cannot charge you any extra fee for using cards or any payment method.
People keep saying this, and it's totally untrue. Because of tax, there's a fixed percentage of every country's GDP that must be transacted in that country's currency. It's 100% false that "fiat currencies aren't backed by anything".

If I owned all the currency of the country you reside in, you would have no choice but to trade with me. If you don't buy any currency from me, you won't be able to pay your taxes and you'll go to jail.
Most of the abstraction is fine. The staging area model is a total mess though. The way that staging interacts with other commands (e.g. stash) is constantly surprising.
> Places that regularly get snow don't really ever take 3 days to clear it, there is capacity to clear it continuously.

With all due respect that's a load of hooey. Northern towns generally have capacity to clear a normal winter's snow. On the other hand, we have gotten well above a normal winter.

First, the snow event can last a couple of days. Even after the large amount of snow gets done, winds can exceed 30 mph with gusts above 50mph. This makes any sort of travel a non-starter. Worse are the storms that start with a sleet / light rain (early and late winter) and then freeze before the actual snows show up.

After the event, you are faced with moving the snow. Late winter storms are fairly brutal if the ditches are already filled with snow. This assumes you can get people to all the emergency equipment in a timely manner. This also assumes the budget is holding for all the overtime.

You can easily be stuck in your residence for 3 days and sometimes a week. Hope the power company is on the ball because that's a load of fun in itself. The 96 storm in ND had people stuck for a week if you were anywhere off the main route. Never mind the damage to the power grid and the setup for the 97 flood.
This is a typical China behavior: lie to WTO about how open its economy is, then openly disregard the repriprocity with other countries and block foreign companies from competing.

Thank goodness other countries are waking up:

"The United States, European Union and Japan vowed on Tuesday to work together to fight market-distorting trade practices and policies that have fueled excess production capacity, naming several key features of China’s economic system."

https://www.reuters.com/article/us-trade-wto/u-s-eu-japan-sl...

"US formally opposes China market economy status at WTO"

https://www.cnbc.com/2017/11/30/us-formally-opposes-china-ma...

"TRUMP STARTS NEW WAR AGAINST CHINA OVER 'ECONOMIC AGGRESSION'"

http://www.newsweek.com/trump-starts-new-war-against-china-o...
If you haven't pushed, it's as easy as resetting the branch to the last good commit. If you have pushed, well, it's the same, then push -f, and then making sure that all your teammates pull the fixed branch. If that's a situation you regularly find yourself in, protecting master from direct pushes and only doing PRs is a good solution (GitHub, BitBucket and GitLab all have tooling for this).
An Interview with the guy who sold two pizzas for 10,000 BTC
Secure scuttlebutt is a totally decentralized append-only "blockchain" with a single writer, that is replicated by various peers who want to get the latest posts. Their mantra is "no global singletons".

https://scuttlebot.io/

Scuttlebutt is very good, but it would be cool to generalize it to the multiple-writers situation. Then we could have one standard for decentralized data streams and even currency tokens, without global networks:

https://github.com/Qbix/architecture/wiki/Internet-2.0
We SSH onto a server to do work and it seems we just make folders wherever for our individual projects. They do (nightly, I think) backups which is sort of a rudimentary version control. And while I'm told it exists, it seems the "dev" version of their website isn't used, so they just kind of add in their changes live; definitely a risky environment. They've had a small team for a while and most of their applications could run relatively in isolation from others, so they could get away with it, but they're looking to grow so I'm trying to push this stuff.
I would add ICLR as number 3 for machine learning.
I've been thinking about this recently as it pertains to changes in my own life... I've been training myself to be less addicted (in the general sense), and I've noticed several aspects of my 'personality' flip like a switch, in terms of preparedness to deal with uncertainty, fitting extroversion or introversion to the context, sticking up for myself but being more pragmatic in other ways.

You might (probably correctly) say I'm coming out of a depression through my own CBT interventions, though I'm pretty sure I was already on an initial upward trend because of positive environmental changes, so chicken/egg.

What you mentioned about anxiety triggered a lot of associations with Sapolsky's writing on stress (Why Zebras Don't Get Ulcers etc), and how bodily aspects interleave with personality tendencies... I do wonder sometimes if a very 'Cartesian' view of personality is problematic pragmatically and philosophically. I.e., 'I'm just an introvert' can be reached by a bad diet or untreated psychiatric symptoms or low social status or just plain old preferring fewer social contacts, and so it's difficult to really /do/ anything with that conception of onself.
I recently had one of those holy-crap-what-did-I-just-do-I-lost-everything moments... But then realized that my scrollback had a list of files and my IDEs (PhpStorm and WebStorm) both kept _local_ revision histories and I was able to restore everything I had done.
I think you should be able to do something like this with

git filter-branch

This won't be a terribly fun exercise, and could be very painful if your history contains a lot of merges. (should be easier with the cactus/rebase development model)

And of course everyone will have to hard-reset to the new branch.

I should mention I'm far from an expert on this. I've only ever used git filter branch on a handful of commits, and only based on examples provided by kind internet people. I certainly haven't done anything nearly as far-reaching as you're about to embark on.
Yeah. It's hard to tell how much we are seeing these reviews because people want to see Intel get passed vs. because Intel is actually getting passed.

Are there any rest that chips released, actual chips, where the different foundries can say "look here's 1kb of sram on an actual chip, with this basic adder circuit, and this is how much area it takes and this is how much energy it consumes on our latest process"?

Actual performance doesn't always match the spec sheet, it's hard to get a true comparison unless you've got circuits from each foundry.
Here's a solid "pro":

http://nakamotoinstitute.org/mempool/

Some highlights:

The Bitcoin Central Bank's Perfect Monetary Policy

Hyperbitcoinization

Speculative Attack
Most of our users are outside of the US where nonfree solutions are simply not in the cards financially.

In the US, we are seeing adoption in practices that can't afford expensive EMRs and in those that want to truly customize their system.

Also, Meaningful Use/HITECH is not ACA.
Burgers and fries don't require clinical trials.
Carnivorous marsupial alive and well after being presumed extinct for 100 years
I think "mainstay" is a bit of a reach.

I love C# and I frequently have a need for high perf. However, unless you need that high perf, don't use Span<T>. Make your code more readable instead.
Can a high schooler get published in AI?
I am currently working on a research project in Ai specifically- NLP and machine learning. Is there any chance of being published as a high school student or will it be an automatic flag for publishers?
I think it is fair to say that "I told you so" is always about self-validation.
Micro Fortresses and the Software Defined Perimeter
I am 18 if that makes a difference.
I recently did something like that—I think I did a reset of the repo and lost all of my changes. Was able to piece it back together using local history. Took me another 20 minutes, but at least all of my data was there.
I admit to using this at least once a week.
I like the idea of stored procedures. I get some of the value they bring. However, the few times I've been on projects where sprocs where the primary focus of logic/truth/app... it was always a pain.

* The 'developers' weren't allowed to write the sprocs. We were at the biz meetings, but the DB guys were hardly ever there - their meetings were separate for some reason, but because devs were at the meetings, the devs were the ones who also were the face of the project. When the project was behind, we caught it in the neck, even if we were bottlenecked waiting for the DB team to write their logic and expose it to us.

* The DB team was always fewer people, juggling more projects, and other things like system uptime, maintenance, backups, etc.

* The sprocs were never part of version control or part of any source code that we could ever see as part of normal development. They typically weren't subject to any unit testing process.

The answer to all of this is mostly human management, structuring resources differently, coming up with different processes, etc. But any of those things would have changed the power dynamic, which seemed to be the purposes in those environments. Hey, I can write a stored procedure too - let me write them, and if a DB wants to 'review' them - or really, anyone on the team - please review and let's hammer it out and make it better. But roadblocking projects until the DB guys can 'get around' to writing our mission critical procs is just silly.

One other 'weird' division I saw a few places was this "developers can never have access to production systems - that violates XYZ" (a regulation, or some 'law' that was never produced, etc). I asked what the core issue was, and it was "you can't just have developers going on to production and just making changes on live systems - that's ... (against our policy, etc)". This was particularly challenging in a situation where a critical bug only happened on one production system, and we weren't allowed to replicate the database to another system, nor was anyone with any knowledge of the deployed code allowed to get on to the production system to even see if what was deployed was what we'd developed. But... this was still "our problem". Yet... the DBA in this case was "allowed" to get on the system and hand-write new triggers and sprocs to 'fix' our problem, all without documenting/testing his code, nor committing the code to any repo for us to even have visibility in to the data manipulation he was doing to 'fix' the problem we supposedly cause but couldn't investigate.

Again, I know this isn't a problem specifically with stored procedures. When sprocs have been promoted as the primary interface, however, it's usually been a political/power grab more than a technical benefit. And yes, again, I know there are technical advantages in some cases, but usually not enough to outweigh the drawbacks I've encountered.
Git bfg should do the job, it works well for that and to remove files with secrets... or really anything you want to pretend never existed in your repo :)

https://rtyley.github.io/bfg-repo-cleaner/
psst

(most money is spent marketing the drug, not developing it)

(marketing includes bribing doctors and healthcare systems to prescribe it)
To be fair, the performance of a Confluence installation depends a lot on what hardware it is on. I've seen Confluence installations that take 20 seconds to load the page to make a new wiki page because they found a really ancient server with hardly any ram to run it on. That happens a lot because a lot of people think it is a low-priority, low-traffic service, then they assume Confluence sux anyway...
I stubbornly stuck with Mercurial for a long time because of the complexity of git's UI. But when one moves beyond a few developers, the available tooling and extensive ecosystem for git makes it inevitable.
Have you looked at git-filter-branch?

The BFG program in this guide [0] seems reasonably close to #2. I don't know if you would need to manually trigger garbage collection in the remote repo, or how you'd do that.

https://help.github.com/articles/removing-sensitive-data-fro...
lhopki01's point is that we suspect you are talking about USA in your post, where the GP was talking about the UK, which has a much healthier market for high-speed internet.

To be fair this might not be obvious, if you missed the context of the thread and unless you are familiar with "Southern Railways".
A git off my lawn moment: Every time I see someone complaining because they have to dive into the reflog to fix their own mistake, all I can hear is "I was operating my table saw without using a push stick and can't understand why I lost a thumb".

Friends don't let friends (especially those who don't learn how to use their tools) rewrite shared git history. If you don't understand rebase, amends, etc can do to your (and everyone else's) repo, DON'T DO IT.
Glad you figured it out! Having that much work on a single branch is a process smell in itself, ideally you would have found a way to get that code into the repo before it became that large (break down the work into smaller chunks, hide behind feature flags if needed, etc.). Beyond what you just described, reviewing that much work is nearly impossible to do correctly.

At the very least, if you are going to have a long lived branch, make granular commits and push to a remote repo frequently. That will give you a distributed backup strategy.