skysight-inc/HackerNews huggingface dataset:
> I'm a fervent believer that flat organizations are way better, you can discuss directly with people, the pain points and challenges are clearly identified and solved together.

You don't want it entirely flat, and you don't want it rigorously hiarical. You have touched on too hiarical, but too flat is a thing as well. Someone with the skill and time needs to make descisions, and someone needs to keep track of things and coordinate. Both of those things are important even for small teams for 5-6 people, otherwise you end up with "The Bridge"(https://www.stilldrinking.org/programming-sucks).
Would be interesting to know from an evolutionary standpoint why the heart preferentially burns fatty acids, when burning glucose is supposed to be better. The heart muscles have one of the highest rates of use. Maybe there are long-term side effects associated with the glucose pathway?
Can you explain why cooperation still works when you don't repeat partners? (Assuming I've interpreted you correctly.)

The reason cooperative strategies can work is that actions depend on previous actions. If you are not meeting the same partner, then your partner's actions will not depend on your previous actions, and you will always do better by defecting.
Can you comment at all about how the MDMA therapy session is conducted and/or structured, compared to a normal 50 minute session?
In a technical sense, yes.

But really it's only prohibited because it's not licensed by Western corporations.

In Eastern Europe meldonium is an over-the-counter drug that's routinely prescribed for all sorts of maladies and is considered a very mild and inoffensive medicine, just a step above drinking green tea.
Hague Rugby Club Selects Superb Grass for New Artificial Turf Pitch
I like the high level CEO view of this problem since it's a good reminder that the overall phase needs re-think. That said, what this article hints to in the title and misses is that there are inherent problems for startups that are in fact related to the number of employees.

Some commentators touched this subject as well and rightly so, when you reach around 20-40 employees you start having problems that are organizational. If not addressed properly these will cripple growing startups and in some cases even prevent them from reaching the next stage.

I went through a couple of these failures myself and I can't stress it enough when discussing problems related to growth; there is a point when you can no longer communicate or work in the same way and you can't expect things to self organize. It takes quite some reorg including some hard decisions to get to a stable stage or in the best of case, transit smoothly but that takes someone very well aware of all the pitfalls.
Polling. The atmega32u4 only has 4/5 external interrupts, and our instrument has 8 pads.
The CapacitiveSensor Arduino library used does this sequentially, busy-looping for each pin. It would be possible to rewrite this to do all 8 pins in parallel. Right now the readout for different pads is sampled as slightly different times, which works but non-ideal.
A more modern uC can have capacitive sensing pherirals, like in the Teensy 3.0
Unfortunately, I don't think I have the time to test anything rigorously, but I would definitely be interested in learning more about the Django solution when it's more mature! Is there a mailing list or something I could sign up for?
How to Create Your Own Ransomware Virus?
When the majority of ICOs start to crash and burn (and the house of cards will fall), no one with a shred of legitimacy will want to be associated with the process. It's just too toxic, with too much room for bad actors to operate.

I'm hugely bullish on Bitcoin and crypto in general, but ICOs are like a bad joke that won't die (look at e.g. https://icowatchlist.com/ and tell me that isn't a fucking farce). I'd love for ICOs to be able to democratize investing, but the information asymmetry is too large. At best, you enable tech workers to make some more money if they're smart and understand a particular business space.

No, a 'blockchain powered' competitor to WeWork (i.e. Primalbase) and the billion other office-share companies isn't going to find any competitive advantage with Ether. None whatsoever. Yet they managed to fleece millions out of gullible investors. Tell me, do you honestly think that's a 7 million dollar idea? Oh, sorry, closer to 9 million when you count the non-public tokens. Late to the game in a super-saturated market that's 99% real estate? Have fun, I guess.

At least your Airtoken thing doesn't reek of scam; there's something actually distributed and blockchain-y going on there. Perhaps you guys are completely legit; if so, kudos. I hope you don't get dragged down with the rest of the charlatans.

But take off the blinders and take an honest look at what is going on.
Sad.

Since there's no details, the likely causes include HCM, aortic dissection (Marfan syndrome) and vfib. AED availability, doppler ultrasound and Marfan screening can be life-saving. It's important to do autopsies and publicly or anonymously release cause(s) of death in an effort to prevent deaths of others.
7 Reasons How Web Push Notifications Boost Your Marketing Strategy
Maybe not looking down so much as differentiating from it. Kind of like you don't have to look down on coffee to sell tea instead cuz some people prefer tea.
You should be able to type it in a 'shell', and you should be able to set it on a function/program you call from the shell. But you cant download and run program that automatically references a file by path. This system is different enough a unix style system so I'll try and roughly describe some details (with some shortcuts) of how I imagine it. It is a messaging based data flow system (could be further refined, of course):

- The programs behave somewhat like classes - they define input and output 'slots' (akin to instance attributes). But they don't have access to a filesystem API (or potentially even other services, such as network). Programs can have multiple input and output slots.

- You can instantiate multiple instances of the program (just like multiple running processes for the same executable). Unlike running unix processes, instantiated programs can be persisted (and are by default) - it basically persists a reference to the program and references to the values for the input slots.

- When data is provided to the input slot of an instantiated program (lets call this data binding), the program produces output data in the output slot.

- You can build pipeline of programs by connecting the output slot of one program to the input slot of another. This is how you compose larger programs from smaller programs. This could even contain control and routing nodes so you can construct data flow graphs.

- Separately, there are some data stores, these could be filesystem style or relational or key/value.

The shell isn't a typical shell - it has the capability to compose programs and bind data. It also doesn't execute scripts at all - it can only be used interactively to compose and invoke the program graphs. A shell is bound to a data store - so it has access to the entire data store, but is only used interactively by an authenticated user.

So interactive invocation of a program may look something like this:

> /path/to/file1 | some_program | /path/to/file2
# this invokes some_program, attaches file1 to the input slot, saves the output slot contents to file2.

You could save the instantiated program itself if you want.

> some_program_for_file1 = [/path/to/file1 | some_program]

Then invoke it any number of times.

> some_program_for_file1 | /path/to/file3 # runs some_program on existing contents
(update file1 here...)
> some_program_for_file1 | /path/to/file4 # runs some_program on new contents

With advanced filtering programs, you could define more complex sets of input files.

> /path/to/folder | filter_program(age>10d, size<1M) | some_program | /path/to/output_folder

You can even persist the instantiated query, and reuse it

> interesting_files = [/path/to/folder | filter_program(age<1d)]
> interesting_files | program_one
> interesting_files | program_two

So that's the rough idea, using an ad-hoc made up syntax for single input/output slot programs.
I agree about Bill Nye, that he's more of a science educator than expert about any one specific topic, but Tyson is definitely an expert on astrophysics. He talks about a lot of stuff that he isn't an expert in because he's a popular guy, and for that reason I'm not very fond of his speaking engagements, but it's not fair to say he's not an expert at anything.
It depends what you mean by significant. SQL update becomes a two phase commit with double network connection setup, execute, teardown latency as a worst case. External auditing must be made. Sounds like hell.

A flip-side view is that, in many cases, if you really want to trust your data (not your database), then you want to be doing this stuff to a large extent anyway... which means that, basically, it's just enforcing good practices that should have already been present.

Complexity and per-TX latency increases, but for that you get maintainability and a great deal of flexibility. Nothing is free... take your pick!
> OK, but you realize that the blockchain in your case is only used because regulation exists right? As in, if the SEC did not exist, you could just sell shares on an open market without registering. But you're using the blockchain so you don't have to do this. Is this correct?

No. He's not selling shares in the company. He's selling the product, he just hasn't built it yet.

The reason to do this on Ethereum instead of MySQL is partly because it makes it easier for users to exchange tokens with one another, partly because the infrastructure is already built, and mostly because people ho mad for it and it seems to be an easy way to get millions of dollars.

I think almost all ICOs are basically scams, but that doesn't mean they're just a way to sell shares without regulations.

Edit: and in fact the vast majority of Ethereum network costs are paid by the customers, not the company. I'm confident that using Ethereum for this is a cost-saver relative to MySQL, but it wouldn't even matter if it wasn't because of the huge ICO craze.
Just a simple example of the one-sidedness of the "evidence" presented:

> until recently, women weren't allowed to vote

Until recently nobody was allowed to vote. Before that we had "the strongest rules", later locked into hereditary rule.

When voting rights were extended to common men, they were (and mostly still are) inextricably linked to military service, that is your willingness to be killed for your country.

Voting rights were extended to common women very soon after they were extended to common men (compared to the time no-one was allowed to vote), and with no such requirement attached.

And of course, since women are statistically smaller than men, all evidence you present for the marginalization of women is evidence for the marginalization of smaller people.

In fact, there is strong evidence that small men are in fact one of the most marginalized groups of all, far more than women, except they don't get treated as a group.

http://www.jonathanrauch.com/jrauch_articles/height_discrimi...

And finally, history is just that: history. Past tense.

I have been ruled by a female chancellor for ... well can't actually remember how long. With the advent of Trump, she has been called "Leader of the free world" and so is arguable the most powerful person in the world. She is not marginalized.

And if lack of female representation in the past is evidence of female marginalization in the past, then lack of representation in the present is evidence of male marginalization in the present (see overall rates of college attendance). Whereas unequal distribution of genders to areas of interest is evidence of unequal interests.
There pretty much is no way for you or I (a.k.a: people without mass surveillance) to get # of users accurately. The best metrics we can go off of are # of transactions[1] and # of unique addresses[2].

[1]:https://blockchain.info/charts/n-transactions?timespan=all

[2]:https://blockchain.info/charts/n-unique-addresses?timespan=a...
A "cup" is almost certainly less than an actual normal serving these days.
A lot of software engineering practices lean towards tribal wisdom instead of being evidence-based.

The only resource I know of that provides citations to studies is Code Complete by McConnell. But having data is no guarantee of correctness. Bossavit debunks some SWE common sense in "The leprechauns of software engineering", including the cone of uncertainty which is referenced by McConnell.

I'm also planning on reading SW engineering best practices by Capers Jones, which is likewise based on data, not anecdotes.
Replace `least amount of code` with `least amount of complexity` and I completely agree!
How Instant Cash Loans Bring Same Benefit in Diverse Conditions?
NextQL project: Equivalent GraphQL but much more simple
On my side projects at home, I can't even remember the last time I had to slow down or got stuck on maintenance/integration type stuff (as opposed to new functionality or algorithms, which don't rely on existing code). And I have a couple of fairly big ones, it's not all "Todo list" stuff.

It's happened constantly at work though, throughout multiple jobs. Sometimes I've been so stuck I've got basically nothing done for days or weeks at a time. Sometimes that happens a few times in a row and I feel like I'm an inch away from being fired for incompetence. This even happens on relatively small projects. It's not confined to big 10 year old monstrosities.

The sad thing is, I work for startups, which should be all about lean, clean code and making big changes rapidly to respond to business needs.

I think a lot of it comes down to how hard it is to work on other's code. I don't think any of the conventional wisdom is a solution to this problem either. I haven't noticed any discernable difference between projects with big fuck off linters, or 50 page style guides. It's not a mish mash of semi-colons that's causing trouble (although consistency is nice).

"Dirty code" is really the crux of the problem. But like the author of this article, I don't always agree with what the conventional wisdom says about writing clean code.

To me, the most important part of keeping your code clean is always having the minimal solution to the problem. Your code shouldn't do one thing extra it doesn't need to. Half of this is YAGNI, half of it is being a good enough developer to come up with simple solutions that aren't too fancy.

On that note, don't get too fancy, and don't take DRY too seriously. Whatever complicated mess of higher order functions you're writing probably isn't going to phase other experienced devs in a vacuum, but combined with all the other icky parts of the code base and it might just be the straw that breaks the camel's back. If you need to write twice as many lines to make it more grokable, that's fine.

Speaking of YAGNI, people should be applying it somewhat to dependencies as well as functionality. It's just far too easy for a simple React project to blow out in complexity because of an over-reliance on other's code. Sometimes it's easier to build something out of code than NPM Lego.
explain?
Yes, meldonium is prescribed to help with recovery after stress and injury. It won't make you stronger or faster or tougher.
Agreed. I've worked in the public sector though and this is shockingly equally likely to be nothing but regular old stupidity mixed with total lack of accountability. If a government department throws away all it's money they are just given more.
Some of the reason schools start homework so early is that parents demand it. I've seen parents complain that a first grade class isn't academic enough because the teacher didn't assign enough homework.
Amazon customers connect their Facebook friends to find people with wishlists. Someone who has the contact could have information that could link the two accounts, for instance if the OP has someone in their friends' wishlists and they have someone with OP's name in theirs. Or could be connected to a subsidiary like IMDb.
It didn't really seem that odd to me. We had 75% coverage and it was more or less as if a cloud was passing by. Had I not known there was an eclipse that day, I might not have even noticed it wasn't.
It is possible. Beware though that each `puppeteer.launch()` will spawn a chromium process.
FizzleFade
HospitalRun team is great and very welcoming. You can join there Slack channel here: https://hospitalrun.slack.com/ . The project is expected to be undertaken by JS Foundation in near future.
And Yeah, I am a Full stack developer.
We are all sitting ducks for next big natural disaster.
This is really amazing!
Given how young the practice of programming is, I doubt anyone alive today knows how to write truly good code. Just look at the kind of code people used to write 30 or so years ago. It's interesting to think about: what will "clean code" look like in 2047?
"Easy to throw away" sounds to me like high cohesion, low coupling.
Now that I think about it, you are right that for PD, there has to be some one-on-one iteration too. I think my automatic mental model was that agents came together and played a few rounds with one partner, and then switch to some other partner.

In this case you can afford to be nice in the first round, and then cut your losses. But even that strategy is only optimal if most of the rest of the community is nice in the first round too. If it is full of defectors, then you should defect in the first round too.
> in fact you claim they are a utility transferable for data but why would the price of the product/data being offered fluctuate

The same reason the price of anything fluctuates. Do you think the price of mobile data should be different?
>Donation cash is the sweetest thing an NGO can have

Also involves the least amount of transparency and not much assurance that the cash is not going directly into the pocket of someone.
Genital Rejuvenation Surgery in Surat
Celebre Aesthetics is the perfect place for genital rejuvenation surgery in Surat. Our best plastic surgeon provides affordable Vaginoplasty, Labiaplasty treatments.
For more details Call @ +91-7226022226
Essentially you are recommending that people slack off as soon as they face trouble instead of spending time making sure they don't break stuff. Had you mentioned Continuous Integration and many commits per hour I would agree that tests and nurture is less important but you seem to base your thoughts on the laziness of old people.
Seems reasonable for a freelancer. If you're doing less, you can work easier and worry-free as an employee.
I'm 19yo, building software as a freelancer and earn 520$/day. If it would be less, I would try to get an employment. If you factor in employer's contribution to your pension plan and health insurance, sick days and insurances for freelancers e.g. IT liability insurance and income protection, this money is spent before it's earned. And you have to make sure that you always have enough contracts and that they don't interfere with each other.

I don't think everyone has to live such a life. It's a great relief to be in an employment without having to think about making money all the time. I chose freelancing because I want to choose what to work on and don't need any security for now, but I can imagine to work for $4,500-5,000/month in the future when I have kids and mortgages to pay for and need security.

The problem I have with freelancing is that you start to measure your life time in your hourly rate, because the time = money equation is ever-present. One has to be mature to resist this temptation, sometimes I'm not able to do it. It's a constant fight between the attitude that money isn't everything and the impression that it actually is.
Do you have examples of things you learned on the courses that you thought made your code more difficult to understand and modify?

After that, did you completely switch back to the code style you were using before the courses? Did you cherry pick some things and not others?

Just to make my view plain, for me 'clean code' was the most important book I've read in my career, and what I learned from it has (in my view) massively positively influenced the quality of my code over the years. I'm really interested in getting an opposing viewpoint. At the end of the day I'm aiming for my code to be understandable and maintainable by other people as much as myself.
They don't have to be equity, and even if they were equity it wouldn't make a difference to his point.

If you think the tokens (equity or not) are likely to become worthless, you can sell them to somebody else, as long as there is anybody willing to buy. It doesn't matter that it's not equity.

Even if it was equity, at the point where it was a dead cert that the tokens would be worthless, they'd still be worthless, regardless of how hard the SEC ensures that you own a slice of that worthlessness.
ICANN could in theory revoke the ability of the registrar to operate. Meaning that they could be put out of business pretty easily. That said I doubt that ICANN would actually do this on a first offense kind of thing. ICANN can also forcibly take the domain from the current registrar and cause a transfer to someone else instead. I think that is what will likely happen if NS doesn't get rid of the parking/stealing of the domain.
You're totally right. And, many couples use porn for a purpose similar to that product. I suppose that's somehow less intimate than buying what this person is selling.
This just seems like poor justification for laziness.

You need to keep a project clean. This means profound refactors when concepts for the product change. Some rules are:

- Keep it readable

- Don't over engineering

- Easy to remove

- Good tests (complete, min stubbing, interface oriented. Never refactor and change tests at the same time.

A lot of "veterans" are just resented with new paradigms and too egotistical to stay relevant. It takes effort to maintain a clean project, many will try to say "it's not worth it". That's just out of the question, it's your job, it doesn't have to be always pleasant or easy. If you don't suffer for it a bit now, someone else will in the future (maybe clients or users).

This is what I like about open source projects, it teaches maintaince discipline. In the end, you can sum up all rules into one:

- Make it easy to maintain
Shouldn't everyone demand more before promoting ideas without any basis? (https://vimeo.com/9270320)

Even if it is just "tribal wisdom", is HN where you recruit a tribe from a vapor posting? I would hope you at least have a tribe before upvoting it up the pile. It feels like it's being promoted for no reason or through a backchannel.

It didn't even give a wiki link to the Chesterton's fence analogy. Sigh.
Gotcha, I was thinking of the Green Card application. H1-B is dual-intent, so all above board there.
Using Ansible for deploying serverless applications
tracking you as you browse around is relatively easy, which is what I believe these particular scripts are doing.

To actually track checkouts/purchases correctly so that you don't advertise to those people requires a completely different setup.
Manage your finances with LibreOffice Calc
How to get started with the Foreman sysadmin tool
To make 100 round trips between Houston and Austin, a total of about 33,000 miles, in 24 hours, the train would have to average 1,375 MPH.