skysight-inc/HackerNews huggingface dataset:
So previously there was a new syscall to replace /dev/urandom in cases where it can't be accessed, and now there's one to replace /dev/shm?

I know there are good practical reasons for both changes, but it seems like sandboxing is throwing the baby out with the bathwater a little bit. ;P
Even if it's not bad planning, the business is the more appropriate party to bear the risk of unexpected slow times than the employee. The employee has already reserved the time in her schedule because she's been told that she will be working then. Even if it turns out her works is not needed, she should be paid for those hours.
I think you're going to be a little disappointed. Most of the Arab world isn't super different from lower class Mexican towns. Not a whole lot of culture going on, really. Just a lot of unemployed dudes hanging around doing not much.

Anyway, you can simply book a flight to Jordan, or easily get a visa to Qatar. It's not dangerous or anything. Go for it.
Adopting HTTPS is very important for the Web, but the lack of HTTPS in this case is just a red herring. The real problem is that it's way too easy to exploit systems through the web browser. If the entire Web switched to HTTPS, government attackers would just find another way to deliver their exploits besides injection into plain text websites. Working on solving this problem is just as essential as transitioning to HTTPS.
This is a very common misunderstanding in this thread, so I will answer it here once. The portfolio is worth a penny on the dollar because it is a mix of quarter debts, dime debts, and "not even worth a 1/1000th of a penny" debts, and the mix is known to be skewed towards crap. If the mix were known to be largely collectible debts, it would have been priced near 30 cents or more. The portfolio has been worked and the easily collectible debts - working phone numbers, responsible debtors with capability to pay - has been collected already.

Even calling people to offer terms isn't profitable at 1/1200th of a $250 AT&T receivable and much of the portfolio is physically incapable of paying the two cents! The collector is hoping to get literally three in a hundred to pick up the phone and take an offer of $150, the bulk of which goes to labor to call them.
Ok, I can agree that we shouldn't design notation around their limitations. And I do like what they do in SICM. But, I'm just trying to root for the point up-thread:

>It seems tempting to have a single unambiguous notation for mathematics. But In constructing such a language, one will quickly realize that doing mathematics becomes an intensely arduous task.

When talking about math, our notation doesn't have to be precise, and that's ok.

> No, I don't dispute that blackboards are useful.
Just obsolete :P
At last :-)

My suggestions:

1) It would be good for it not to be just tied to AWS - though I can see why you'd bootstrap up one cloud.

2) The thing I'm always looking for is the following combined elegantly:

Availability Metrics (ala Pingdom), Custom Metric Reporting, Agent Based System Metric Reporting, Metric Viewing, Metric Comprehension (what does it all mean), Metric Triggered Alerting and Automated Actions.

(I can get 80% from DataDog)

The automated actions should be based on alerts, which are based on metrics. The metrics should be custom or system. The actions should include: scale out (on an IaaS deploy by image, on a PaaS scale out), scale back, reboot, rebuild from image, custom script execution etc.

For the life of me I don't understand why there isn't a single SaaS providing end to end metric -> alert -> action flows.

Again good luck, looks very nice and if I wasn't moving away from AWS I'd jump on board.
I'm Anny. I am 25 too and I'm facing situation like yours and I am also lost. I don't have any fancy advice but I want to share some stuff that may work with you as it works with me.

For sure in the future I know that I will have my own business. But Right now I'm trying to get a new job. Also I have to maintain the responsibility that I have to support my family. It is very tough life. I was very suffered.
I recently just realised that yeah suffering demands to be suffered, we have to experience it and never hold back, but once when we done with it we just let it go and look for positive possibility and pursue it.

I was very miserable for past months and just recover from letting those shit go. I choose to be thankfully happy not miserably lost. I am now having job interview with Amazon AWS and Google. I keep positivity high but expectation low and still keep looking for, again, positive possibility. I keep telling myself that always believe in yourself, always look for positive possibility, focus and pursue! Lifehacking is fun after all :)

here are some of my stories. I wrote it couple weeks ago when I was super miserable and I didn't know what to do.

http://fleurblanc.tumblr.com/

Enjoy lifehacking!
Yikes, sounds like a pretty tricky mixed integer programming problem. What are the usual go-to techniques for optimization? branch & bound?
3 (More) Common Uses for Redis in the Gaming Industry
>First, you get a horrible incentive to not repay debts

Isn't that what credit ratings are for? You'd be able to do this exactly once for any meaningful amount of money, and then your financial life would be otherwise over.
That's an interesting angle. The troublesome part is that credit reporting is a two-sided B2B marketplace. You need to convince people to report debts to you AND convince lenders to make lending decisions based on your reports. On top of this, you have to have a B2C facing function for FDCPA and FCRA compliance, and they're very toothy rules to fall afoul of.
> I'm not saying writing secure software in C is inherently impossible, but I'm not aware of it having ever been accomplished

https://sel4.systems

Possibly one of the most trustworthy pieces of software there is.
Well, that doesn't mean there can't be fraud involved. There often is, and that's when things tend to fail spectacularly.
I agree with all of the above. It's difficult to see how useful this is among the deep technical explanation. The chart on the github page emphasizes features of DNSChain that the current system lacks, but perhaps a chart showing where the current system fails and where this fixes those issues would be more useful?
Now I only see Vitess can support resharding with some restrictions, maybe I am ignorant.

I don't think handing sharding on the application level is easy, programmers may care too much about MySQL sharding and can not write sql easily, at least in my company.

I have only used Atlas (https://github.com/Qihoo360/Atlas) and cobar (https://github.com/alibaba/cobar), but they are not suitable for my company, so I want to develop a simple one using Go.

Auto resharding is very awesome but I don't have the power to do that now. Any help is very welcome.
Keep in mind a couple things. First, it doesn't cost very much to operate the information service called a website. But it doesn't matter how much something costs to produce, it perceived value sets the price.

The reason why paywalls didn't work is simple. Almost all websites have NO perceived value. A news site, come on.. Getting news is a total commodity. I can read about Kim and Kanye without coughing up a subscription fee From any number of places. Ever notice HBO never had a straight news program? Getting news is a total commodity and print media feels this pain quite directly.

Now for entertainment. People will pay for quality. HBO being a great example. But look how much content you get for your $12 mo. Netflix, huge. Look at all the content you get. No single website has that much proprietary desired content, and that's why pay sites didn't work.

Ads rule, because it's perceived to be free by the consumer. It isn't of course. Giving up your attention and personal data is a cost, but not felt directly. If the internet explosion of the 20 years has taught us anything, it's the amazing amount of value people will give away for free, whan they don't perceive they are giving it away. Facebook is entirely built on user generated content, and most of the others too.

Ads will not be replaced by pay for content on a wide scale. There is not enough value in most of the information on the net.
Thank you thank you!! I did send thank you e-mail to the recruiter. But for sure I will ask them as your advice if they're being silence. Though I'll keep positivity high and expectation low :)
There's no doubt that the US can learn from the shear audacity and willingness to invest in our country's long term energy plan like Germany has done with the Energiewende. However, we can't pretend that Germany, in terms of its size, existing infrastructure, and structure of the electricity industry, is at all comparable to the US.

While I agree with you that decentralized power will be the way of the future, there's no way the US, where California alone is larger than Germany, can make such a drastic and impressive transition in even a tenth of the time it takes Germany. The power grid in the US is one of the (if not the) most complex networks/systems the world has ever seen. Heck, it's not even a "singular" entity, with three interconnects spanning parts of Mexico and Canada comprising it. We're not going to easily transition away from this--not that I'm saying we shouldn't try. Our current infrastructure is not capable of handling mass amounts of renewable (read intermittent) sources of energy--the energy storage technology, bi-directional communication, and security measures among other necessities just don't exist yet. And while at a certain point our country needs to make the leap and take the risk, we should also be cautious about trying to brute force a solution--look how Spain's renewable energy investments are paying off.

Edit: It may also be too early to call Germany's energy plan a success. They still face many substantial challenges moving forward (http://www.economist.com/news/europe/21594336-germanys-new-s...)
Couldn't these issues be mitigated if the video recording was encrypted and simply archived for a set period of time unless there was a judge ordering its release?

Wearing cameras has a lot of potential for good if there are string safeguards regulating access to the footage.

I think encryption is a basic requirement here, with a software architecture that properly documents all access to the raw footage and enabling release only in some narrow circumstances.
I guess if you want to pretend to live statistically. But once you actually move somewhere and try to live there you might find it's something else.
Maybe have each site page require an underscore: _about.txt, _links.txt, etc. This way the pages appear at the top of the dropbox folder.
So plain http in plain, static html (no javascript, limited css) is best then...
Perhaps I am. I was simply trying to relate a personal experience with these cameras, and the fact that they have made me feel uncomfortable at times (for the sake of the folks I'm caring for). It seemed germane to the conversation.

Maybe someday it'll be routine enough that it doesn't enter my mind. For right now, it's frankly a bit of a distraction (in situations where a distraction can literally be fatal).
> Companies are not inherently evil, and companies can - and do - choose to try to do right by their employees

To the extent that it makes them more money, this is true. Providing perks for employees is sometimes necessary to ensure you have good employees, and going above and beyond what's expected can provide positive PR, which in turn can generate revenue.

Irregular retail schedules are an example of what happens when neither the market, nor regulation force employers to do right by there employees.
How optimistic are you that it would actually be implemented well?
I think you'd be better off to just drop the statement completely. The line below it reads, "Blot is the simplest way to blog." That's short, clear, and tells the visitor why he/she should be interested.
Well, you say 'abnormally/irregularly slow' and 'not unheard of', but the article quote says 'often', which suggests it's frequent practice (along with the general tone of the article).

Scheduling is quite open to abuse from dodgy managers - for example, I had a friend who worked at a supermarket that rostered him on for 3.75 hours, then 30 minutes later, rostered him on for another 3.75 hours. This 'split shift' meant that they didn't have to give him the mandatory paid 30 minute lunch break for an 8-hour shift.

Same goes for it being extremely busy and calling someone who is off and asking if they wanted to come in to make some extra money.

This sounds like a balance, but it really isn't. "Would you agree to do more work" is not the opposite of "I'm reneging on our agreement for your current work" - the latter is unilateral.

Hospitality sucks. When I was in my early 20s, more than half the people I knew worked in hospitality. Now I'm 40, only one still remains in hospitality. It's an abusive industry that people get out of if they can - in general, it's short hours, odd shifts, bad pay, crap managers with little or no training, and no job security. Screw defending the practices of that industry.
We're experimenting with different solving techniques. One of the difficult parts to fit into an algorithm cleanly is "pick how many shifts this employee should have" - e.g. should a part-time employee have two 8-hour + one 4-hour shifts, or one 8-hour + three 4-hour shifts. If you are trying to build that logic into the solver then branch and bound struggles but something like basin hopping seems to work better. However, with fewer employees you can just solve all possible weekly shifts per employee in parallel with a branch and bound. The most basic way to calculate the range is using the hours an employee works in a week and dividing it by both the minimum shift length ("not worth coming in for a shift of less than two hours") and max shift length ("don't have somebody work for more than 8 hours in a day"). Gets more complex when you move into problems like required number of days off per week.
I certainly don't disagree with you.

The fact of the matter is: If a goal involves raising taxes on the rich (or corporations) in the US, it will be pretty difficult to achieve.
According to your link, seeds from Schmeiser's neighbor's field were blown into his field by the wind, he harvested them, and was successfully sued for patent infringement. So everything your parent comment stated was correct.

There is an element omitted, which was that he harvested those seeds (in accordance with his established business practice of keeping seeds from his field) in the knowledge that they were Roundup resistant, since he had sprayed his field with Roundup to see what would happen, and what happened was some of his wheat lived.

Roundup isn't patented or controlled in any way. So what would happen if I took up the hobby of growing a few patches of wheat every year and spraying them with Roundup? Over time, the magic of selection should produce Roundup-resistant wheat, which would be free of any Monsanto influence. Would I be violating Monsanto's IP?

If you think I wouldn't be violating Monsanto's IP by growing, and selecting, my own Roundup-resistant wheat, take note that Schmeiser didn't do anything I didn't describe myself doing in the thought experiment.
It's over 4 years old - i5, 8GB ram, GTX 750 ti (GTS 250 before)
The amount of private health information that would be exposed in someone's bedroom, on a medical call (where a thorough interview is conducted, revealing all sorts of personal information) is _miles apart_ from what would be recorded by a dashcam at the scene of an accident.
"London sets all the high end fashion trends"

Come on, now. Paris? Milan?
Nice! What do people use literate programming for? I've yet to, but I'm sure I'm missing some cool benefits.
Not bad. Not sure it'd come close to replacing org-habits for me.
http://www.timeportalpubs.com/index.php/forum/welcome-mat/16...
I like this. I, too, live near, but not in DC, and my situation is basically the same as his.

I also like his conclusion of eh, we'll just move to Columbia Heights anyway. I would too, but this makes me notice one thing that that this whole thing is missing: schools. I don't know if there's any school data that could be applied to this, but I bet it would be a good way to narrow down some of the results.
The OP specified a time other than zero, so there are four dimensions. This means the usual physical rules apply. My use of "as soon as" is completely consistent with the era specified by the OP, i.e. when four dimensions are available and physics is "normal". And I made this perfectly clear in my reply.
I really really want to like this. Org mode for emacs has really expanded what I could want from a literate programming tool, though. Specifically, being able to execute small segments and have the output immediately usable is rather nice. That you can also feed tables of data directly into the language is also nice.

Granted, I do feel I have a fair bit to learn in how to structure code for others to read. Myself included. I am learning the rather obvious point that keeping a narrative to the code is not easy. And, of course, in the couple of attempts I've done recently, I end with a fairly large dump of "and here is the boring stuff" at the end.[1]

Also, I can't recommend reading straight from Knuth's site heavily enough. His programs are rather interesting by modern aesthetics, but they are all still runnable.

[1] http://taeric.github.io/DancingLinks.html
Sounds like a scary criteria to an entrepreneur ("you can never work!") but it might ultimately make sense for those who go to university, but end up marrying someone with a good job and becoming a lifetime dependent of them (in est, the classical homemaker.)

There are probably a few other less-common situations as well, where a person has no money of their own but access to plenty of the money of others, e.g. the "trust-fund baby."
Asynchronous Programming with Goroutines in Ruby
What are you some sort of hippy Unitarian? I hate to break it to you, but the real religions have rules. Catholics will just politely ask you to take the proper sacraments. Probably the same for most Muslims. I can imagine getting dumped in the desert if you accidentally attended one of the conclaved Mormon rituals.
Ah yes, the old 640K ought to be enough for anybody.
It really is a truly excellent piece of writing.

There's not an ounce of apparent judgement or subjectivity in it. Rather the article is purely an enumeration of causes and effects that leads to a scathing critique of these scheduling practices and the effects they have on people's lives.
I'm not sure that there would be any incentive to. Once they've decided to sell, a high bidder is a high bidder (though it's obviously frowned upon, otherwise he would have gone himself).
Not to mention that if you do have an unusually busy shift and you're run off your feet, management doesn't generally say "hey everyone, here's a cut from the takings because today was good". I have heard it happen very occasionally in small places, but it certainly doesn't happen at McDonalds.
Google acquisition
> Then why would anyone pay their bills if they can buy their debt back for 1/10th of what they owe?

For the same reason why they might not pay to start with. They don't pay and bank sells the debt to someone.

Or the don't pay and then choose to pay later a smaller amount.

Option 1 sounds not too far off option 2. It would be minus the hassle to fend of collection agencies.
No: this API is fundamentally different from /dev/shm, and will hopefully obviate the need for some Android-specific patches (such as ashmem, though ashmem may already have been replaced by a new flavor of the week). /dev/shm is a folder, which represents a global namespace of memory objects, and which essentially must be manually reclaimed (imagine a world where you create an object, and then kill -9 the app before immediately uninstalling it). This API has a name, but it is for debugging purposes only: the lifetime and accessibility of the object is based purely on the Unix semantics of memory maps and file descriptors (which can be laterally shared using Unix domain sockets), allowing them to be automatically cleaned up. There is an additional advantage that it works without extra mount points, but I doubt that would have been a sufficient motivation for this change: /dev/shm is so problematic that it doesn't even exist on Android.
It really is a great way to introduce a narrative into the code. Too much of reading programs feels like taking a look at either just a plain convoluted mess, or an index that someone put together for another larger work. (This is especially true for pieces where someone makes a lot of single use functions. Sure, the pieces may be "self documenting," but it is almost akin to just seeing a bag of screws. You know what they do individually, but you don't know why they are there.)

If you have the time, take a look at any of Knuth's programs[1]. Obviously, they are not all immediately approachable, but render them to pdf and give them a try. You'll hopefully be surprised just how much you do pick up.

The only downside, to me, is that I become less concerned with modern trends of long variable names and abstractions that "self document." These are still great, of course, but they don't go nearly as far as knowing the narrative of why a piece of code was written.

[1] http://www-cs-faculty.stanford.edu/~uno/programs.html
Maybe a stretch, but is this somehow connected:- https://news.ycombinator.com/item?id=8160844 ?

I oddly remembered this comment from my memory trove.
I was rewriting a bunch of custom scrips a few months ago and would have been lost without this tool finding my mistakes.
For what it's worth, that's a nice neighborhood[0].

[0] I've lived within that area
"This little episode captures something I’ll see over and over again in Yemen. Faced with a problem, you find out who is in charge, escalate to the highest level of authority present, and communicate your sincerity by vigorous yelling. There is always a phalanx of sons (and presumably a similar, hidden number of daughters) who can be deployed as messengers, sent on errands, or otherwise made useful. Everything is done with a level of verbal vehemence that would involve grief counseling and possibly lawsuits back in the United States. People are able to operate at emotional temperatures that would melt down an American.

If you asked me what I had witnessed, I would say angry people with guns had nearly come to blows over handwashing."

I'm not from the USA but have spent some time there and this description for some reason reminded me of New York.
The execution could need some polish and the UI isn't doesn't seem very friendly (lots of fields to fill in) but such an app fills a real need.

This certainly doesn't replace official complaints but having independent data collected on Police interactions can probably increase political pressure to tackle abuses.
I've been playing with literate programming for a while, and I don't think having boring stuff is a bad thing. The strategy I've settled on is to try to show a cleaned up history of the evolution of a codebase -- and a key part of that is including tests in the literate program. http://akkartik.name/post/wart-layers
Should we train more people as programmers?
They might not care. It's money now, versus an asset that would still be technically in default. It was a liquidity crisis, or at least that was the official line... $3.4 million in cash might be worth more to them than $18m in bad debt even if it was repaid - it isn't good on balance sheets, and with all the regulations about how much money has to back what and what counts as backing (and private contractual obligations - how do the credit default swaps outstanding treat something that's paying interest only vs a total writeoff), without knowing the details almost anything could be the case.