skysight-inc/HackerNews huggingface dataset:
I haven't read a legitimate argument against the IRS calculating taxes automatically, but here it is.

The more invisible taxes are to the individual person, the less they think about that money (and the higher taxes can go without them complaining too much).

Rent feels expensive because every month you write a check for rent. However, for many people, taxes are a much bigger expense than rent. But taxes don't feel as painful, because people don't write a check every month for taxes. Taxes are just invisibly withdrawn from your paycheck.

The easier and more invisible it is to pay taxes, the more you forget about how much money that really is. If you believe in constrained government, there's a good case to be made that we should make tax payments more visible, not less.
The above mentioned security. The workload, which has two spikes in January and April, moderate traffic in between and is basically non-existent April through December is pretty much the poster child for cloud since you could spin down capacity in the 8 months where you don't see much traffic. This is why Intuit has publicly stated that they want to go all in on AWS. But, at least when I was there, the internal security teams were making it very difficult to get cloud deployments approved. I know they were working closely with Amazon engineers to fix/design solutions to the gating security concerns, but I have no idea how far they've gotten.

But when you look at the money involved, you can see why Intuit is moving so slowly and is willing to continue to spend on its own data center. $40m/yr may sound like a lot of money, but when your product pulls in $3b/yr, it's a rounding error. And the data centers aren't dedicated to TurboTax...Quickbooks and a few other products run there too. And I have to say that, for certain services, I think you get a lot of piece of mind from not sharing and having your own data center. Take, for example, Intuit's service for scraping data from financial institutions (FICDS). It powers Mint, Quickbooks and TurboTax and is required to store login credentials for people's banks, retirement accounts, brokerage accounts and such. Needless to say, the security of such a service is paramount and there's no way that I'd ever entrust my banking credentials to any service hosted in the cloud. You just can't get the same level of security you can get when you've got physical control over your hosting.
Well, with the kind of budget that Military has, it could pretty much be called a nation; you're not invited, but thanks for the kindness though!
My banks online password requirements match the suggestions in these documents, but the passwords are entirely case insensitive. So its the same if I type "password" or "PaSSwOrD". There is a second passphrase that youre asked to select randomly chosen characters from combo boxes for, but that is case insensitive also. I got into an argument with their customer rep on Twitter about this not being the best case and they replied that it was based on industry best practice. I've never heard that before...
I read others code in code reviews, and as necessity to get the job done. I very occasionally read others code say in GitHub, but not for any desire to get better, but out of curiosity. But when I do that I get bored quickly!
http://webcache.googleusercontent.com/search?q=cache:WNVCznx...
Could you poke holes in his/her arguments? Or perhaps cite examples? The counterpoints seem convincing but, hey, I might be totally missing something.

For context, I'm a long-time fan of your writings and REALLY appreciate how much you've given to the community (with the only VC blog worth reading IMO). Just want to fully understand the issue at hand here.
Because capital keeps telling the young developers that they’re smarter/quicker/more adaptable than the older ones. It's a seductive lie.
What country on earth has these 100% free things?
One of the first tech talks I remember was Bryan Cantrill at Google, and I vaguely remembered that he mentioned at the beginning of that talk that he had contributed to a book called Beautiful Code, so I double-checked and it seems to be the same book.

Looking back up the talk, it points to his review of the book here: http://dtrace.org/blogs/bmc/2007/07/28/on-the-beauty-in-beau...

> More specifically: read [two specific chapters with very different attitudes on what makes code beautiful]. It seems unlikely to me that one person will come away saying that both are beautiful to them. (And I’m not talking new-agey “beautiful to someone” kind of beautiful — I’m talking the ”I want to write code like that” kind of beautiful.) This is not meant to be a value judgement on either of these chapters — just the observation that their definitions of beauty are (in my opinion, anyway) so wildly divergent as to be nearly mutually exclusive. And that’s why the title is perfect: both of these chapters are beautiful to their authors, and we can come away saying ”Hey, if it’s beautiful to you, then great.”
cache: https://archive.fo/aZDJF
Slashdotted...
Renters fight new construction too. "Gentrification will raise our rents". It's absurd how hard it is to get a permit to build in SF. Mountain View fought new housing construction for a decade as google was ramping up. Nobody seems to remember first year economics when it comes to construction on their block.
Do be aware the ibuprofen and the like can be incredibly hard on your stomach. Ibuprofen caused gastroenteritis so severe I went to the ER due to the excruciating pain. Apparently daily/frequently usage is often associated with gastroenteritis. Which sucks because it is effective. I recommend taking natural antiinflammatories instead. There are quite a few which are effective. Also, ranitidine (commonly suggested for stomach acid issues) is very well tolerated by the stomach, cheap, and really effective at controlling inflammation.
Wow, I had no idea. Thank you.
I agree with your general point, but to sanity check your numbers: car radiators don't even weigh a tenth of that. The entire cooling system, including fluid, is in the sub-20kg range. The entire drivetrain of a common 4-banger is in the 150-160 kilo range.
I found DPDK and FreeBSD's pkg package manager to be very clean and educational.

Reference http://www.dpdk.org and https://github.com/freebsd/pkg
OP says "I keep reading on HN that I'm order to become a better developer I need to write code everyday, and more importantly read other people's code."

It hardly sounds like he is looking for a shortcut
You're implicitly assuming the law of the excluded middle. Depending on the logical foundation, a fact chain could exist which is seemingly infinite, but for which no finite proof exists that it violates any of the three laws.
You might want to get educated about the history of psychiatry. Asylums were an amazing upgrade to people being tied up in basements by their families. Medications helped people who otherwise would spend their whole lives in asylums, or simply kill themselves.

Even lobotomies kind of made sense, although thankfully far better treatments were invented at roughly the same time, so they were short-lived.

A nice book on the history of psychiatry: https://www.amazon.com/History-Psychiatry-Era-Asylum-Prozac/...
Good response.

It's fascinating that people find it so pointless to change platforms for the sake of their own privacy. Generally when I suggest to my peers we start chatting via Signal, they think I'm a conspiracy nut or something, it's fascinating and a little disappointing. Strangely, this "why bother" not only seems to apply to passive family users who don't understand what's behind these systems, but people who do.

I assume this why you're still using WA?
It is sort of funny that 'conservative' and 'liberal' are commonly meant as opposites when talking about US politics. But isn't conservatism pointing back to liberalism if that's the founding principle of the country?
To be fair, she had experience on her side.
Checkout "Freightened" - https://vimeo.com/202104276
Uh..get rid of the government involved in all these tax laws. Obviously?

Are you suggesting complicated taxes isn't the government's fault?
At least the govt is ostensibly about the public good. Anyone else through self interest is suspect. Which gets back to the title of the original post here for this thread...
> Make all paid lobbying illegal.

Regulatory capture is a problem, but I think you'd have much worse problems regulating complex industries without talking to them.

For example, the FCC doesn't really exist to protect consumers from anyone, but to be the "traffic cop" protecting manufacturers and operators of radio equipment from each other. I have a hard time believing the FCC could make coherent rules and spectrum allocations without the affected parties being able to raise issues to it.

Ditto, for example, airlines and pilot unions being unable to raise concerns to the FAA.

Ideally, lobbying is a way to say:

"Hey! We do this thing you want to ban [guns | amateur radio | general aviation | take your pick], and here's why, and by the way, we vote."

"Hey! We have this serious problem in our industry, one of our peers is behaving badly, can we do something about this?" Net neutrality regulation, for example, comes from companies like Netflix advocating for their interests against companies like Comcast.

You can publish this on the web all you want, but Congressmen aren't going to read the whole internet every day. We need some kind of "push" mechanism to get issues in front of them.

Obviously there are many very serious failure modes, particularly when one side of an issue has a disproportionate budget compared to the other. But there are also important use-cases.

Lobbying is not so simple an evil. Lobbying backed by campaign contributions, on the other hand, is much more simply bribery.
I have a couple issues with your post.

First up, you seem to be conflating the source of infrastructures funding (state vs city) in an area with whether the population of that area could without external funding pay for their infrastructure.

And secondly, while maintaining buried infrastructure in the city is likely more expensive, your argument presents no claim that it is more expensive _per capita_.

edit: see http://usa.streetsblog.org/wp-content/uploads/sites/5/2015/0... for some numbers on the last point
The gop is soft, but arguing with the alt right is scary. They are extremely good debaters, very antifragile.
Dr. Mercola swears by the eating "pure" approach to solving many autoimmune diseases: no prepared food, no refined sugar, food made from scratch from the highest quality ingredients (organic, or as close to it as you can get). One of these days when my arthritis gets too bad I'm going to give it a shot. It's expensive, and a massive change in lifestyle (no more fast food! Or restaurants!), but I can see why it'd be so effective.
Чехлы для телефонов Meizu и других брендов
I don't think you can consider 5 companies to be an oligopoly especially when you don't see monopolistic practices. These companies regularly undercut each other and innovate.
With a smartwatch you might have to remove both hands off the bars. I would prefer a jeans though and the smart fabric on the thigh or the pocket.
So the alt right evolved because the gop was too weak.
Pretty interesting. I've never thought of it like an arms race before.
Like they don't know.
What kind of subsidies for low deductible health insurance are you talking about? (not from US, so I don't know)
That's fantastic. Especially the theft part.
Fantastic, thank you so much
Individuals are significantly better at allocating resources than a central authority.
Yes, funding a $600 billion military industrial complex [0]. Just think, your complete yearly taxes were probably almost enough for a single JDAM [1] which was then dropped on Iraq, in a war where 13% of all civilians were killed directly by US-led forces [2], and many more in the chaos that ensued from the invasion.

But you love it.

[0] - https://www.nationalpriorities.org/campaigns/military-spendi...

[1] - https://en.wikipedia.org/wiki/Joint_Direct_Attack_Munition

[2] - https://www.theguardian.com/news/datablog/2012/jan/03/iraq-b...
You can ask for a price, but perhaps there's a different reason for that than the one you provided?
I would agree with you. The most natural way to do it seems to be SIGCHLD and a timeout function like select - when the signal hits, the timeout returns early.

I'd add that the most 'Unixy' way to do it probably is to use `alarm()`, though like threads it is a bit of a "now you have two problems" solution as well. But if you blocked all of your signals, spawned your child, called alarm(), and then did a `sigwait()` on SIGCHLD and SIGALRM I think that would work fairly well and be decently simple. You just check which of the two hits first and then handle them accordingly.

I'd also add that even with the threaded cases it's not actually guaranteed to work. Lots of these syscalls may put the program into uninterruptible sleep, which will prevent you from killing the thread until the action is done (And for lots of things this is a necessity, since otherwise you could leave things in an unknown state. Userspace shouldn't be able to corrupt the file-system just by specifying a weird timeout.).

IMO, like others have said I think the real solution to a timeout for things like `mkdir` is in the kernel: If you're attempting to access something like a NFS mount and it's taking too long, it will fail and you get an EIO, which is not extremely graceful, but does mean that you won't sit there forever - it will return after a period of time the kernel considers sufficient to know that it's not going to happen.

In userspace you ideally have no idea what you're actually accessing, and thus have no basis for what an accurate timeout should be anyway. It doesn't make sense to pass a hard-coded timeout to `mkdir()` when that value will probably be stupid long for some things and not long enough for others, and that's a much bigger usage issue then certain programs taking a long time on slow filesystems.
Computer proves that god exists
I also would suggest working through the entire book. It was written by Brad Miller (one of the founding members of NetPerceptions and professor of computer science at Luther College) and David Ranum (currently a researcher for IBM Watson), so they know what they're talking about and what is relevant.

P.S. If you're keen in solidifying your academic understanding of algorithms be sure to pay attention to the section on big-O notation.
Depends what you mean by web development. If you describe the tasks you work on, I can make some suggestions.

Otherwise, the only reasonable answer is http://norvig.com/21-days.html
> what evidence do we have to believe that we haven't made some of the same mistakes in classifying pseudoscience in the present?

The uncomfortable thing is that this can cut both ways. Things can and do get rejected because it doesn't fit the ideology.

Feynman called it Cargo Cult science:

We have learned a lot from experience about how to handle some of the ways
we fool ourselves. One example: Millikan measured the charge on an electron
by an experiment with falling oil drops, and got an answer which we now know
not to be quite right. It's a little bit off, because he had the incorrect value
for the viscosity of air. It's interesting to look at the history of measurements
of the charge of the electron, after Millikan. If you plot them as a function of
time, you find that one is a little bigger than Millikan's, and the next one's a
little bit bigger than that, and the next one's a little bit bigger than that,
until finally they settle down to a number which is higher.

Why didn't they discover that the new number was higher right away? It's a thing
that scientists are ashamed of--this history--because it's apparent that people
did things like this: When they got a number that was too high above Millikan's,
they thought something must be wrong--and they would look for and find a reason
why something might be wrong. When they got a number closer to Millikan's value
they didn't look so hard. And so they eliminated the numbers that were too far
off, and did other things like that. We've learned those tricks nowadays, and now
we don't have that kind of a disease.

But this long history of learning how not to fool ourselves--of having utter
scientific integrity--is, I'm sorry to say, something that we haven't specifically
included in any particular course that I know of. We just hope you've caught on by osmosis.

As you say, it takes a lot of faith to believe that we're now clearly on the path where the truth can only go one way. For example, given that history will always be discriminatory, is there a situation where it will be clear that societal discrimination now reversed to be against, say, white men? After all, even if it was in some hypothetical future, people could still point to history as a justification for why women or other races are actually the oppressed (it's essentially the argument you just made, I don't see why it'd be any less valid in 50 years or whatever).
The Redis code doesn't look exceptionally good to me. I just looked through five files, but things like spacing and the use of braces seem to be pretty inconsistent. There are also a lot of magic numbers and quite a few variables have poor names.
10 Reasons why Asana is the best project management tool [video]
Thanks for saying that!

I don't have any agenda or ascribe any to you. All I think is that to the untrained eye, this post comes across as founder-unfriendly.
The argument is an angry version of "if it's free, you're the product," which at this stage is very uncontroversial, and only comments on the "we've lost control of our data" point made in the original post. The link between what author calls "people farming" and "surveillance" is not compelling.

That said, I personally agree with the author in identifying the main problem of the web as people tracking. In my opinion, Tim Bernes-Lee points about misinformation and political advertising are not specific to the medium, but rather to the times we live in. People are pissed, people are scared, they need something to blame, they need some fantasy to believe in, they make up scary news, they vote for the guy that gives them a dream.

What's specific to the web though, (and that is starting to spread out of the web) is the data tracking. Whether for advertising ends or for surveillance purposes, data tracking creates a power imbalance between people and systems that is unbearable.

That power imbalance is the weirdness you felt the first time you saw a gmail ad related to the email you were reading. It's the anger that heats up your cheeks when the sales guy asks for your email address when you just want to buy shoes. It's the 2-hour phone call to the customer service that ends in "I'm sorry there is nothing I can do for you". It's the "late fee" mails you automatically receive for a service that you cancelled. It's realizing that the app your employer installed on your phone can tell them your location at all times. It's the swatting that reminds you not to shop for pressure cookers online. It's the cameras. It's the cars. It's the lightbulbs.

We as people are weak. I don't think Silicon Valley intended it that way. I think they genuinely wanted to improve the world. And in order to keep it cheap, they found money where they could, and in the process, they undermined people's privacy in a way that is making the world a lot worse than it was.

I personally feel hopeful. Countries are made of people. And I think that people are starting to get it. We need rules to prevent this. Laws that force companies to automatically give you the option not to track you. The same laws that forced mailing list senders to have the unsubscribe button (thank god for the unsubscribe button!). For this to happen, we need lobbying, we need awareness. We need a "this website is not tracking you" label. We need privacy checks.
In all fairness, a stunningly clever insight can make things seem so obvious that you forget how hard it was to have that original insight.

This kind of brevity is extremely helpful when thinking about a problem. You "just" have to grok the mechanics thoroughly. This really helps in designing effective higher level abstractions.

Unequivocally admonishing brevity for ostensible readability kind of ignores the trade offs. I think there are other ways to bootstrap grokkability without having to sacrifice the conceptual clarity of nicely compact code.
This perception causes discrimination which is illegal (if you can prove it)

This is why there are a host of lawsuits for ageism and a bunch of job portal like https://www.giantsforhire.com/ or https://oldgeekjobs.com/ poping up
A man falls off the roof of a ten-story building. As he's passing a third-story window, the occupants within can hear him shout: "So far, so good!"

Given the many. many known nuclear close calls (And I'm just counting the ones that were likely to cause a nuclear war - not domestic mishandling of materials), this is an insane position to take, with our current nuclear arsenals.

Four times in our nuclear history, the decision of one man saved us from armageddon. We are only having this conversation because people like Stanislav Petrov made the right decision - after the entire command-and-control system surrounding them failed.

[1] https://en.wikipedia.org/wiki/List_of_nuclear_close_calls
Funny thing is that I've been introduced to Signal by my peers. No paranoid lunatic glare.

The app has some rogue edges and needs to be refined in order to be as usable as wa, specifically: data usage & media compression.

The service has a high potential indeed.
>an administration with actual white nationalists as advisors

Citation needed. You're probably talking about Bannon - can you explain in your own words why you think this?
Sounds like a liberal bubble.
Using phrases like "muh jobs" probably also turns off people from discussion with you.
The single most important change I've made in how I learn new tools/frameworks/whatnot is Github code searches -- I spend far more time there than on StackOverflow. Maybe this is more important in Scala land, where there are far fewer books and talks and blog posts to work from, and the tool stack is evolving a lot more, but I've found answering many questions of structure / "How do people incorporate this concept into a larger application" to live largely in code.

The answer is never exact, though. Something will have 10 different solutions, and being able to look at them and discuss the tradeoffs that went into the decision is a definite skill.
I like most the python code written by Norvig in http://norvig.com/python-lisp.html and other parts of his site. It's very expressive and simple. Real code will have much more corner cases and logging and error handling crust but still should tend to this simplicity