skysight-inc/HackerNews huggingface dataset:
I was in my mid 20's when I quit my job to learn programming.

Do you mean if I tried to enter the industry in my 40's it would have been much harder? Or now that I'm in the industry, the smooth sailing will eventually get rougher as I approach my 40s? If the latter, I don't really believe it...
https://news.ycombinator.com/item?id=13872613
The Unsung History of America's Hard-Working Hoboes (2015)
Whats the tldr of this story?
web2py handled all of these issues and made its markup language extensible with its markmin specification: http://www.web2py.com/init/static/markmin.html
Honestly, at this point I found reddit a much nicer place to go then stackoverflow for technical questions.

SO users demand that your question be "correct". Note, I didn't mean that it should be clear what your problem is, it's just that if you ask a "noob question", for an explanation, or if five people think it can't be done, you'll get down voted and closed in a second.

It's sad because other (smaller) SE sites are quite nice.
Try increasing your attention on what's important to you, instead of decreasing your attention on what isn't.

You can be asked for your attention, explicitly or implicitly, any time, for the dumbest stuff. Most of us have never learned to ignore it. And ignoring it is the only way to survive being constantly asked, because saying "no, stop bothering me" is pretty much just another way of saying "yes, you may take my attention right now."

It might help you to stop having a phone. I did this for a few years, and it was modestly helpful, and surprisingly easy to do. But in the end, there were some things I did need to pay attention to, and some I didn't, including on the phone. My partner, my kids, my family- they all really did need my attention.

Hacker News? Not so much.

Figure out what's important, pay attention to that. Might be that the feeling your having is precipitated more by the lack of connection that is really meeting your needs.
A few examples:
github
basecamp
atlassian
Yea, my wives is pretty 93% in "solve" mode and I'm 84% in "solve" mode so we try to explicitly say "can I just vent (or talk something out loud) to you?"
I really wish this weren't being reframed as an "opt out" discussion. The article is expressing valid concerns about the collective impact of FB. Opting out, even in large numbers, won't change the fact that the company has tremendous, unchecked influence on our lives.
The Supreme Court’s Big Data Problem
You were probably a great teacher!
The (P)react component model
Author knows not only this, but notes more than one instance of this defensive tactic failing, including:
"A small French nuclear sub, Saphir, snuck past several points of defense and sunk the U.S. carrier Theodore Roosevelt and half of its escort ships."
If anything, being involved with Company XYZ correlates positively with (paying lip service to) being concerned about its policies. Example, I quit Facebook so I stopped caring about their privacy violations, but I'm still attached to Google so I still am "concerned" about theirs.
Transit Is Dead and Content Rules the Network
The Making of the Legend of Zelda: Breath of the Wild Video
User experience.

Gifs/apng load and play instantly* and loop. There is no play button to click. No volume button, sliders, etc.

One simple link. Instant load and play.

*assuming good bandwidth
HN Guidelines say "Please submit the original source. If a post reports on something found on another site, submit the latter" [1].

This is the original source: http://www.atsb.gov.au/newsroom/news-items/2017/battery-expl...

[1] https://news.ycombinator.com/newsguidelines.html
Representation tells us almost nothing, because of the problems further up the pipeline. Women aren't studying CS in large numbers, which may or may not have anything to do with SV. Women make up only 18% of computer science graduates, so one could easily argue that your data shows that women are significantly over-represented in the industry.

Why so few women study computer science is an important question. Again, I think it's dangerous to presume the answer without sufficient data.

https://nces.ed.gov/programs/digest/d12/tables/dt12_349.asp
1995 called, it wants its bad arguments back.

The honest answer is that people releasing software under the GPL don't want you using their code in your proprietary whatever. They explicitly said they don't want you to do that.

How is that different than you releasing your proprietary whatever, and conditioning use on paying you money and agreeing not to share it? If you get to set the terms of use of your code, so do other people.

> What's the point of open sourcing something if it can't be used in a proprietary product?

Obviously, the point is to share it with people who want to do something other than use it in a proprietary product.

Complaining about free gifts generally doesn't end very well. Don't like the terms? Pretend it is Oracle or Microsoft crown-jewel code. You can't do what you want with that, either.
There is, alas, plenty of examples of code which were based on BSD-licensed code, and _not_ given back to the community. Exhibit 1: BSD code (open source) and WAFL (netapp's write anywhere file system that was written on top of BSD, and never given back).

If the point is so that people contribute the changes back to the original codebase (which you seem to agree with), then the point of using the GPL is to make sure that actually happens. If it is used in a proprietary product, and never given back, from the perspective of the open source world, that use of the code might as well have never happened.
I'll take someone without a CS degree and an intense rabid desire to solve problems way beyond their current capabilities any day over a pedantic PhD who can't be bothered to even put together Ikea furniture. Yes, I know a couple. They are useless.

Attitude and approach is far more important than knowledge. The latter can be gained in many ways. The former comes from childhood and, generally speaking, is hard to reprogram.
The tack I've come to lately is to say "I don't think we currently have sufficient information available to adequately resolve this issue" - it works like a charm, and people seem to like you more when you say that, compared with "let's agree to disagree"
cheers! I cant count how many times I wish I could melt into a dipping sauce so I can be eaten and disappear. At one point though, I decided I've had enough and started to pay attention to what it takes to 'fit in'. Looking back, the best decision I made was to hire a pickup artist for a weekend. Spending a weekend talking to a dozen beautiful women (out of my league) and getting feedback on my body language, things I said, social awareness, etc, after each interaction helped me break through a glass ceiling in terms of 'fitting in'.
Python Programmin Introduction on comsciu.com
We are in the world of zero and ones and truth is somewhere in the middle
I wouldn't say it's a false dichotomy.

Technical limitations result in different cultural and artistic usages. Twitter's arbitrary 140 character limit resulted in a distinct culture. And it seems like not being allowed to embed images at all on Hacker News is part of this site's distinct culture.

And similarly with gifs. The question is whether you can move to a modern format (for better battery life) without also removing the limitations that resulted in a genre that's not just embedding an arbitrary video in a page.
There is the Russian DRAKON programming language, might be worth having a look at it.
FEE is a fairly biased and bigoted organization, but their argument /sounds/ plausible.

It /sounds/ stupid that you should have to remove, or not publish, content just because deaf people can't read it. But the alternative is for the law to say that the ADA does not apply to deaf people. That is the /only/ way to stop this having to be pulled down.

If that exception is made then there is no longer any reason for any government organization to support deaf or hard of hearing (UCB is huge, so the cost argument that applies here, also applies to any other government organization).

Among other things, that means that the public education system would no longer need to support deaf children.

The ADA exists specifically because before the ADA existed schools did exactly that, as did universities, etc
> Perhaps this will make it clearer that controlling things from your phone currently involves somebody in the middle, monitoring what you're doing.

As I mentioned in another comment, part of the original suit (the claims that the app violated wiretapping laws) was based on the fact that when used in a "solo"/"local" siuation, the app had a direct Bluetooth connection between the phone and the controlled device which means there was no reason to think there was "somebody in the middle, monitoring".
Unfortunately, I only ever got to know him through the self-paced CS9 series.

I truly wish I had gotten to take 61A with him - and before it switched away from Scheme. I don't think the current incarnation is a worthy successor of the SICP based one.
Sure.

In late March 2016 I was working out a problem in Openstack that had the appearance of a race condition. It had to do with the vif_unplugged_event sent from Nova to Neutron. In certain situations when the L2 service component in Neutron was behind on its work it would fail to respond to the event before Nova carried on with its work leaving the network in a bad state. We'd ultimately found a solution to the problem but while I was in the middle of it I was talking about it to someone who would graciously introduce me to the idea of modelling the system and using a model checker to find the race condition for me. I had heard about TLA+ from somewhere, once, so I listened.

I had been an enthusiastic enough student that this someone would become a good friend. Together we decided to work on some models of some underlying components in Openstack. Driven by the Amazon paper on their use of TLA+ on the AWS services it seemed like a worthwhile cause: see if we could convince open source projects to adopt these tools and techniques in the critical parts of their systems. Improve the reliability and safety of infrastructure projects like Openstack which continue to be used as components in applications such as Yahoo! Japan's earthquake notification service.

We haven't published our models yet but we started with a model of the semaphore lock in greenlet. It started as a high-level model using sets, simple actions, and some invariants in pure TLA+. We then added a model of the greenlet implementation in TLA's PlusCal algorithm language and used the model checker to prove the invariant in the higher-level specification still held when refined by the implementation model. We then refined the specification and the model in TLA+ until we came quite close to a representative implementation of the semaphore in PlusCal that was very close to how the Python code was written. We didn't find any errors which I think was satisfying.

We decided to take our little project to the Openstack design summit in Austin. My enthusiastic partner in maths and I found a handful of naive souls to come to an open discussion about formal methods, software specifications, and Openstack. It went quite well. We unfortunately haven't been able to expand on that effort as I'd lost my employment and he had to focus on his PhD thesis.

Needless to say though I've since used verification tools like TLA+ to model design ideas and I continue my studies in predicate calculus and logic-based proofs. I just don't talk about it too much at work. Tends to frighten the tender souls.

Update I should clarify that the errors we were particularly interested in were deadlocks in the implementation of the semaphore.
Be a recruiter for a bit :P or any sales job, really.

Best advice I can give is treat every "no" like a probe from the other side to learn more. They're not saying no, they're saying "I don't know enough about this to want it." Obviously use common sense to avoid harassing someone, and don't waste your time where no opportunity exists (Mark Cuban reacted to the infamous "sell me your pen question" with "Do you need a pen? No? Ok, have a nice day.")

So every "no" has a response -

1. "No, you don't have enough experience."

Response: "I understand that this role requires the right experience. I applied to the job because I'm confident I have the experience you need. What about my background makes you feel otherwise? Do you have a coding challenge I can complete to demonstrate my ability?"

2. "No, we've had issues with bootcamp grads in the past. "

Response: "Hm, I can understand why having an experience like that would make you wary about bootcamp graduates. Was there something specific about why that grad didn't deliver? (choose response based on further information gathered, then: ) Hm, that does sound challenging. I think that my x y or z demonstrates why that issue wouldn't arise with me / I would love to demonstrate via a code challenge why I wouldn't x y z / If you go to myproject.calebjay.com you can see that I have quite a bit of hands-on experience with x y or z, so I'm confident that a b c wouldn't be an issue.

I'm remembering now an old sales training "no" breakdown:

1. Acknowledge the concern. Make the client feel that their concerns are valid, do not challenge or attack them, but at the same time avoid perfectly validating their belief that this is a harbringer that all similar solutions warrant "nos." So: "Yea, it is quite frustrating when recruiters send candidates that aren't even close to a good fit. You should see some of the resumes we people send to us when we open a job!" === good. "Oh man recruiters are so annoying, yea I would definitely never use them" === bad (when you're a recruiter trying to sell your services. Also, "psh, recruiters never act that way, you must have done something to annoy them" === bad.

2. Information gather. Always good all the time anyway. Usually the first "no" gives very little information and you could make some bad assumptions. "We've had bad experience with recruiters in the past" tells you literally nothing. The answer they give you can lead you straight into one of the fifty sells your company has drilled into your head. "What happened with the previous agencies?" "Well, they were sending bad resumes." --> "Oh, we get some hilariously off resumes. We like to think of ourselves as a filter for our clients, so we get maybe fifty resumes for a posting which allows us to hand-pick the best 3 for our clients." "Well, they would have three or four recruiters constantly calling us." "That is frustrating, we decided two years ago to only allow a single recruiter point of contact for our company because of that exact feedback from our clients." Etc.

3. Close. Of course.
Reminds me a lot of Desiderata.

https://en.wikipedia.org/wiki/Desiderata
Sun Tzu - The Art of War.
I was shocked when I went to college about how crazily obsessed the school was about "getting a job". Nobody ever talked about the amazing things we were going to be able to do with the knowledge we learned! I dropped out when I started making enough money in my own programming deal, and am glad I got out of that hellhole where u work like a dog and get treated like one too. I'd rather get paid to do work (my company) vs pay to do it (school)

I was also shocked when I met somebody who was just happy to go to work...

This is why my kids will be homeschooled. School is more about daycare and prepping people to be good employees than real learning. There is a reason why Elon musk started a new, different school without grades for his kids
See the word "comparative" in my comment. We don't know if women in tech are experiencing exceptionally high levels of sexism, exceptionally low levels or completely average levels. The answer to that question matters greatly to how we formulate a response to whatever level of sexism exists in our industry.
If everyone was respectful then of course the problem would resolve itself.

But imagining for a second that the story did somehow manage to get statistics and quantify the "mean"-ness of an individual, there would still be case for sexism being a factor that uniquely impacts women more negatively.

For example, many people are somewhat "mean" but
1. Are these people only mean to women?
2. Are they "meaner" to women than men?
3. Are they mean in different ways to women? (ie, sexual harassment is usually only towards women)

Interesting thoughts though. I wonder though if emphasizing a more radically respectful culture in general would make a difference. It would definitely curb the resentment that men feel over stuff like diversity hiring goals, but without data, we do not know if it would meaningfully make women and minorities experiences any better.
Structure of animated GIFs is odd - you pretty much have to read entire file to animate it correctly; hence the inefficiencies.
Rachel Maddow says she has President Trump’s tax returns
Right, but Comcast doesn't imprison people for life and bomb other countries or throw you in jail for not paying for its services.

Also, bureaucrats are responsible to the organizations most influential to them. "The American People" can barely be motivated to vote in a presidential election, because they rightfully perceive that their votes don't matter, and a vote between two shitty options is a shitty vote.

So, businesses (like Comcast) can just earmark a few million dollars a year to keep buying whatever organization has the power to regulate them, and we (the people) can do nothing about it.

The reason I strongly dislike Net Neutrality is _because_ comcast is horrible and hated. It's reasonable to assume that as we speak, the comcast executive team is figuring out how to best wine and dine top FCC officials.

Because that's way cheaper than being a better company.
I know Jeff Hawkins' Numenta have been tracking "permanence" in their artificial synapses for many years now.
Isn't the talos principle very linear? Or did I just never get beyond the intro?
Food in the Age of Sail
blogspam of

http://www.spsp.org/news-center/press-releases/milgram-polan...
Here's another interesting case (from another thread on HN) of someone who worked his ass off to rise way above average:

https://billmei.net/blog/silicon-valley-job-search

Thousands of people want to be him. Few are willing to do what he did. I am sure some of them blame the rich for their ailments.
Can you elaborate on why you want to split your application into multiple services? This matters, as a 'how' you split may vary based on the 'why'.

My suggestion would be to look at the existing modules in your application, and analyse the coupling and cohesion across them. If you find loosely coupled modules, with minimum dependencies of their own, then these become good candidates for services. Another consideration is to try an split around domain concepts, rather than functional concepts. For additional thoughts, take a look at this post: http://www.nirmata.com/2015/02/microservices-five-architectu...

On your questions:

1. With a microservices-style each service may have multiple instances. And each service instance runs as a separate process, and may be on different hosts. So, you can map each service to its own UID, or may run a group of services with the same UID based on the privileges each service requires.

2. Debugging gets harder! It best to plan for testing each service in isolation (e.g. using mocks), or with minimal dependencies. Troubleshooting is also harder. You will need log aggregation and management. If you are running in containers, you can use services around the container to handle logs.

3. A service should have its own database and only expose an interface to the rest of the world. Hence, you can directly use a database driver in your service.

Hope this helps.

Regards,

Jim
I don't know about this. At my last job, one of the very first problems dropped in my lap was to fix a debugging tool that had been mostly written in Workflow Foundation, a flowchart-based programming environment for .NET that isn't domain-specific, esoteric, or intended for children. It was the tenth circle of Hell and almost drove me to a nervous breakdown in my first month on the job. Despite how often I quote Joel Spolsky's "never rewrite the project from scratch" essay, I threw the whole thing out and wrote it again, and was much better off for doing so.

Now, certainly the specific failings of WF, and the bast^H^H^H^H person who wrote the tool were partially to blame here, but even with all that in mind, the experience has permanently soured me on visual programming. It has all kinds of flaws-- it's harder to reason about, harder to debug, harder to comment, and harder to quickly modify that plain old source code. If there was some trade-off, an upside for all that trouble, maybe it would be worth it, but I can't see one.
> So is the moral of the story for a developer to make sure you have an updated privacy policy?

Given that the original suit included claims that "Defendant never informed Plaintiff that it would monitor, collect, and transmit her Usage Information" that seems to be one potential moral.

> If they would have updated the privacy policy on their product would they have been legally protected?

Presumably only a case being decided at trial could determine that. But it's worth looking at the proposed settlement documents that outline the non-financial changes they agreed to in order to settle the case.
Interesting that they don't mention the airline. I'd like to know which airline uses a bucket of water to handle a battery fire instead of something like http://www.allhandsfire.com/Fire-Containment-Bag
Weird. That isn't showing for me :/

Thanks anyway
> Can you imagine this game on a PS4, or a PC

Yes, It'd be nearly identical. The only thing that more horse power could noticeably improve would be the draw distance.
That's correct, vuls queries the package manager for installed packages, versions, and changelogs. It then compares the CVEs found in the changelogs to NVD.

There are certainly flaws in this approach; it's one of the reasons we intend to support multiple scanners. We started with vuls because clair wasn't released yet and we wanted to support more than containers.
This is a ridiculous position to take. The flagging operation is for things that violate rules and it severely punishes posts. It's not meant to be used as a tool for you to shove your opinions of what is worthy onto the community.

A post will die on it's own if it fails to receive upvotes. If you think something else should be on the front page, you go and upvote something else or leave a comment on the article explaining why it is crappy (comments down-weight an article). If you can't find something else that's better, then move on and stop acting like some gate keeper of worthy content.

If everyone behaved like what you're suggesting, the front page would just be a bland pile of the lowest common denominator content that displeased the fewest number of people.
While this is good, I'm astonished that this took so long, especially compared to Ruby On Rails. GraphQL was introduced 2 years ago, in the spring of 2015. And it's taken this long to get a CLI tool that can auto-generate some of the schema/setup?

These last 2 years, a lot of my clients have been asking me, "Should we switch to React/GraphQL?" And I've done one big project with GraphQL, in the spring of 2016. And I was amazed at how much I had to hand code, especially compared to Ruby On Rails.

In 2004, Ruby On Rails was born with these kinds of CLI tools. Indeed, Ruby On Rails pretty much established our modern ideas of how much a framework should do for us.

A CLI for GraphQL certainly makes the React eco-system more competitive with Ruby On Rails, but I am astonished that it took this long.

(PS: I am aware that React and Ruby On Rails are not strictly competitors, since you can use them together to create software/website. Nevertheless, "Should we use Ruby On Rails or React?" is a real question that I've been asked several times over the last few years.)