skysight-inc/HackerNews huggingface dataset:
Unfortunately, most industries are rapidly becoming ageist if they aren't already. And if you work in a job with lower general compensation (most of them... except finance which has major discrimination problems too) It's impossible to make enough money to retire at 40, which is exactly what most of us are now being asked to do, at the prime of our expertise, due to "overqualification"... ahem... ageism, I mean.
1. Because people want to know for lots of reasons like financial planning or "bucket listing".
2. The more people who know sooner, the more we might learn about the disease, how it progresses,
and the genetics of the people who acquire it.
Intel delivered a 17-qubit superconducting test chip to QuTech
> has cognitect banned you from forking clojure and fixing whatever you think they've done with some evil intent? no.

I don't understand this objection. The value in a free software project, and especially of a programming language, is primarily in its community and the expectation of a future around the project, not in the existence of some code somewhere. It's extraordinarily hard to build a community around a fork, and if you need to fork to do reasonable things, that's a legitimate criticism of the people running the original community.

(That said, if you only need to fork to do unreasonable things, that's good community management. I don't pay nearly enough attention to Clojure to know what's actually happening - but I have seen both of these cases in other free software communities.)
Okay, but at least with static typing one can have dynamic typing simply by using an all-encompassing type.

With only dynamic typing, one cannot have static typing.
Stay away from it, other then tax advantages you should stay away from it. Nothing but horrible experiences.
I believe the way Dat works is if you don't have the public key for a Dat Repository (AKA the Dat URL), then you'll never find it even if other people are sharing it because peers will only respond if they are asked for that specific public key. However, as soon as you have that public key, then you can see the IP addresses of everyone sharing it. This seems like a privacy problem with the Internet itself that the Tor network is attempting to at least help solve.

- https://docs.datproject.org/security

- https://blog.datproject.org/2016/12/12/reader-privacy-on-the...
Take Aways from React Native EU 2017
I'm convinced there are schools over there that print Masters degrees in computer science with only 6 weeks of training. I'm only half joking.
Having worked with Indian companies and for Indian companies the last 20 years here is my advice.

1) Learn to say 'no' or 'we need to understand this better before we can give you a quote or a deadline — too often, way-way too often Indian outsourcing companies oversell their capabilities. Learn to say, 'this can be done, this can't be done' within the timeframe/budget etc.

2) Increase your prices, get more senior developers (increase their salaries). For most western companies even a 100 increase in price is still many times cheaper than what they can get and if you get better developers because you can pay more you will be able to better meet your deadlines.

3) Invest heavily in proper frontend people. Give them extra training if needed so they know how to write optimized code. There is a world of difference between solving the problem and solving it elegantly. All too often what you get back works but is useless because it's too slow.

4) Hire western project managers. Don't get me wrong I have worked with some really great Indian managers but understanding the western culture and expectations and being able to understand western expectations would remove 90% of the confusion that happens today.

5) Did I say, increase your prices and your salaries?

6) Be better at writing PRD's and set expectations, make sure you can meet those expectations and don't be afraid to push back on what's possible to deliver early on. The sooner a client knows there will be delays or the sooner they know their timeline expectations can't be met in time the better. That allows them to plan accordingly.

7) Did I say, Learn to say 'no' or 'we will have to look some more into this'

Ping me if you want more concrete advice, it's an area I care about a lot because I worked with Indian companies a lot.

Solving the quality, expectations and honest feedback would increase any Indian development house directly into a top-tier partner for me.
This has come up on HN and other places. If you want to avoid this issue, phrase your questions differently (e.g. as non-binary agree/disagree questions).

I'll let one of our Indian colleagues suggest the best alternative here, as I'm sure they know more about the relevant Indian cultural points than I.

But even something like "Tell me how you will accomplish X?" or "Do you have any worries about doing Y?" tend to produce better India-US communication.
IIRC it depends on which storage backend for docker you use: https://web.archive.org/web/20170405122924/https://developer...
Easily log and tune Deep Learning experiments
Great analysis.

You know what's fascinating about the iPhone ? So many people online, really smart ones, have analyzed Apple's sucsess and strategy, with great depth.

And yet rarely mentioned is the huge impact brand/luxury marketing has had on it sucsess and the methods used to get Apple there.

Almost makes you believe in conspiracies :)

For example, it's a known thing in the luxury marketing business - that if you want to create a luxury product with high margins - you need to talk about unique materials and processes, that nobody else knows how to do. And maybe that makes Apple's cpu the first brand driven processor ?

Or that's a good part of luxury marketing, is creating an image of a godlike founder genius. Who is a better example than Jobs ? and only recently we're started to see storiesi about how actually the iPhone was mostly a team effort by a group of smart people, and Jobs didn't play such a big part in it.

Or the fact that all the stars use iPhone(maybe because it was the first smartphone, and now they are locked into it), and that's the kind of advertisement money cannot buy ?

Anyway, reading the full story of Apple's marketing would be a really interesting tale .
Hey everyone,

To the people who contacted me regarding the IOS version.

It is currently under development and not available yet.

Thanks :)
How is that different from Dat?

https://docs.datproject.org/security
Greed and war has always been the best motivators.
I agree with your last point. An early detection tool can help find a treatment/cure that works before the disease progresses too far. Again, I see the use for research purposes. While writing my original comment, I specifically had WHO's Wilson criteria in mind (http://www.who.int/bulletin/volumes/86/4/07-050112/en/). The 2nd point requires that there needs to be a treatment in order to screen for a disease.

The current time from diagnosis of Alzheimer's to death is about 8 years (with some variability) with a relatively slow progression of symptoms. It's possible that some people may want extra time to make arrangements like you say, but this comes at the cost of living without knowing whether you have Alzheimer's. I've never been in this situation, but I can't imagine that this tradeoff is clear-cut for anyone.

I think my gripe with the article is that it claimed this test will "promptly be used clinically". I seriously doubt this. The article doesn't report the sensitivity or specificity of the test, and we don't have a great sense of how early this test can detect Alzheimer's.
Capitalism is an economic system and an ideology based on private ownership of the means of production and their operation for profit. You want creativity? Leave capitalism.
I was actually overstating the case :) the quote is "My manager has told me that I should not feel pressured to contribute at all for my first 6 months and I should feel free to just focus on learning as much as I can." (emphasis mine)
The new Conj talk is certainly an interesting look at one man's (or one community's) look at static typing. However, as much as I admire Rich, some of the points he made don't resonate with me, particularly the one about how compile-time checks to catch minor bugs in syntax are not a particularly useful feature of static typing. I certainly disagree. As someone who writes Clojure all day long right now for a living, I am constantly dealing with runtime errors that are due to minor typos in my code that I have to track down, and this time would be greatly saved by having a compiler tell me "on line 23 you looked for :foo keyword in a map but you meant to type :foobar, so that's why that was nil" and many other similar woes.

I love Clojure but I really miss static type checks.

The other item in his talk I do not agree with, he says (slightly paraphrasing) "in static typing, you can pattern match on something 500 times but if you add a case, you have to update those 500 matches to handle the new case, when really they don't care about this new case, only the new logic needs to consume this special case, it's better for the producer to speak directly to the consumer". Well, in languages like OCaml, Swift, Haskell, it is a feature that pattern matches much be exhaustive. This prevents bugs. In most cases, I'd expect that if I add a case to an enum, the chances are good my existing logic in pattern matches should know about that. Maybe not all, but a lot of them will. It's nice to have the compiler guide you to those places.

I certainly like how fast I can write programs in Clojure, and I like the minimal amount of code that makes refactoring and rewriting fairly straightforward since there is not a lot of time investment in the existing number of lines, and I like the incredible elegance of Clojure's approach to functional programming.

But I do miss having much greater compiler assitance with typos, mis-typed argument order to functions, mis-typed keyword names, etc. Would really save a lot of time.
Morgan Stanley predicts space industry will triple in size
I've seen the same thing. If I didn't know better, I would say they have 1 or two guys in a large group that are talented and helps the tens of hundreds of people who are unqualified. That works ok for a while, but doesn't scale well, and you end up getting code written by unqualified people and the 1 or 2 good people don't have the time to check everyone's code and a lot of stuff falls through the cracks.

FWIW I worked with an eastern bloc country team (Europe) and it was top notch.
There was never any lustre for me, the first thing I ever knew about "Virgin" was "virgin mobil, which was "free" if you'd click through ads. It was aimed at youth who didn't have much pocket money and I thought that was just awful that teens were clicking through ads to answer the phone.
Basically, in my experience, and the experience of others I've spoken to, you need to do almost exactly the opposite of everything the India dev agency industry does. The sector as a whole it completely trashed and discredited in the UK, from what I can see, and if I interview somewhere and they have an Indian agency on-board somewhere, it's a major red flag that something very, very bad is probably happening somewhere.

That's because every single Indian dev agency experience I've had, has resulted in a net negative outcome, sometimes so bad we've thrown away _everything_ they've touched and started again.

A couple of ideas that might make everything "nicer":

1. Increase code quality. Commit to it. Understand technical debt and commit to reducing it. Refactor. Code reviews. Cite and apply industry standard texts like _Clean Code_ or language-specific texts (e.g. _POODR_ for Ruby). Test coverage, great documentation, highly readable code: they're not optional any more.

2. Go agile and lean. Don't expect BUFD. Realise the client is learning as they go too.

3. Don't take specs from a client and develop code that meets them. Develop the spec _with the customer_. Use BDD properly.

4. Realise there are many things that go outside the spec. Pre-empt. Don't wait to be told. Realise that functional requirements are less than 20% of what is needed to successfully ship a product. There are many things I would "just expect" a developer to do, but every time I've worked with an Indian dev agency I got exactly what I asked for, no more, no less, no common sense applied. Do I really need to tell you the "password" field should be encrypted at rest, and which crypto scheme to use? No, you should do that because it's basic common sense, and tell me what crypto you chose, and why...

5. Say "no" more. Say "I don't know" more. Say "we made a mistake" early when it's obvious you made a mistake. Don't pretend you/your colleagues are an "expert" in something if you've read one or two books or developed a couple of projects: you're still novices until you have 3-5 years experience of doing that thing. Embrace that, be honest about it, it's OK. Price yourself accordingly.

6. The sector tries to compete on price. Try and compete on speed or quality instead.
Maybe tell them that it can be hurtful, even when said with humor, or tell them it's not really funny.

If they are that much overconfident, just remind them of what they did wrong to make them realize they are not so perfect.

Also just try to tell them without being judgemental. Try to use the "maybe" word or "I might be wrong but", try to make the person doubt a little so that he/she can take a step back.

You can also try to joke about that person's overconfidence.
This sounds almost too good to be true. It's published in a lower impact journal so I'm wondering if the sample size was very small. Also, how did they confirm the 'topography of the pathophysiology' (where the disease is) without taking people's scalps off?
Thank you for your comments.

2. I still believe the CS Education needs to be improved like anything.

Some Unis are picking up good practices but at large the fundamentals of programming needs to be taught in a better way.

3. 100% agree with you on work-life balance. We are doing our best to keep the workplace healthy, interactive & fun.

As a small team, our emphasis is never about more work but better work. We have always encouraged team members to speak at developer events, contribute to open source etc.
>> "The group’s fight against inflation isn’t news."

> Oh! What an unfortunate turn of phrase for someone to use to describe their topic. If even the reporter doesn't think this is newsworthy, why are they writing about it?

I think the author of the article is german (I'm german too) and this sentence is maybe a "false friend". What she most likely meant is that the groups goals are already well known.
Am I right to be concerned about this, if only in principle? I don't like having a mysterious embedded chip that can access the network when my computer's off.
It won't happen in a day. If your scenario is correct, economy will transition slowly to bitcoin from fiat. Fiat inflation is not a problem when you have non-inflated currency in a wide use.
Or "We're developing a website for them, maybe we can upsell them an associated Android/iOS app as well".
Starting a Web Design Firm from Scratch
For those with an Android device that want to browse the Dat based P2P Web, there is an experimental Android browser called Bunsen Browser in development. And we could use your help :)

https://github.com/bunsenbrowser/bunsen
> Talk is cheap. Show me the code. - https://lkml.org/lkml/2000/8/25/132

Insist on implementation to back theory.
I invite you to watch this talk.

Dynamic typing is about a lot more than having an "Any" type. It's about widespread lack of extra code and cognitive overhead associated with the imposed structure of adding static types to a project, as well as the verbosity that static typing typically adds (including in type-inferred languages).

You can't just turn off the static typing in a static-typed language; you can turn off the static type for a specific type, yes, but that doesn't give you the experience that dynamic languages offer.
It does sadden me there aren't a bunch more advanced options a level or two below the standard options on iPhones.

I didn't down vote you by the way.
Central Vacuum System for Hospitals
You are so brave
I think having no experience is an advantage in industries which have become stagnant. If the industry is stagnant, than in a sense, most people in the industry is a failure. I'd compare this to visual programming. There is a small click of people in visual programming who have been at it for decades. They are failures, as none of their projects or ideas have had any value. Taking advice from them is worse than useless.

Edit: I changed what I wrote, so as to not claim that "everyone" is a failure, some people worling in visual programming are still having fresh ideas. But they don't have the attitude of being "industry insiders" the ones with fresh ideas are the least arogant and offputting to outsiders. They are the ones who are least likely to put someone like Elon down as being inexperienced.
> And if I go to the edit view, make changes, then exit without saving, then go back, the view should be reset.

This is business logic and it's dependent of the UI. If you have a Save button but the user doens't save and leaves the page, on change route you reset the model. If it doesn't have an explicit button, on change route you save the model. It has nothing to do with the framework.

If you mean the library doesn't have a way to reset the model to its original state, it doesn't take too long to implement, just call fetch as the author says or when you load the original model store a copy somewhere, even inside the model itself.
How is this Rotonde different from the RSS Reader client that Paul Frazee wrote? https://hashbase.io/pfrazee/rss-reader

Also, is it really necessary to git clone the rotonde repository? Why not go to a starter Dat url and use Beaker to fork your own copy?
Cyanogen pivots from trying to be an 'Android killer' to self-driving tech
I mean... say what you want about communism but it's full of creative people who know how to get things done. I am sure anyone reading this will find the list below very creative :D

https://en.wikipedia.org/wiki/Mass_killings_under_Communist_...
If your wife is a woman and you too are a woman, this would be puzzling. If you are a man, it becomes a lot less puzzling. "Race/culture"still trumps gender.
Firstly is your perception that they are 'quite mediocre, or above average at best' - this is your problem. Looking down on people for being less than yourself is not an admirable trait, something you seem to share with them.

Why are you assuming the comparison is with oneself?
I would love to hear a comparison of Dat and Zeronet. The only difference I'm aware of is that Zeronet uses Blockchain technology and the Beaker Browser / Dat folks are of the opinion that Blockchain won't scale for the P2P web.
In that case, the problem is not overqualification, the problem is that the person is high maintenance.
Depends on the company but here's what I have been through:

* Good dev team doesn't need "managing" but instead you become some kind of BS umbrella to protect them from arbitrary disruptions.

* Don't expect every developer to be as communicative as you expect. They may be unhappy but may not let you know directly. 1 on 1s are really important.

* Much less coding. Less than I am comfortable with.
Exactly, my two peeves having worked with companies like Tata and InfoSys were:

1. Saying yes to everything. Questions, estimates, analysis: everything was answered in the positive even when the facts were negative. I makes project control very hard.
2. Deferring to management every 10 minutes. On every call, meeting etc. Engineers were very much not able to make decisions by themselves.

Having said that, all men and women I worked with from these companies we're really friendly and certainly tried their best.
Communism is not the only alternative to Capitalism. Also it is worth to discuss whether a self-described communist system was truly communist.
Ask HN: Noteworthy code craftsmanship in open source projects?
Think of an open source project featuring an elegant solution to a problem. What design do you find noteworthy and worth sharing with the HN community?

Please, share a link highlighting the code block.
You'd be amazed at how productive you'd become if you're working mostly on your own, uninterrupted, and with a clear vision of what you're building. Look at how much you already churn out in the span of a year, then multiply that.
I think it depends on the applicant, I'm willing to do such a project but the prices I will demand if hired will be markedly higher than a firm that offered me a simpler project that consumed less time. The way I see it is you have limited the risk you have undertaken in hiring me thus I can see more of the fruits of my labor.
Does your agency have any public GIT repository? To be more specific.
Absolutely - there’s a ton of implicit biases at work whenever you go down this path. Comes down to, if you want them to work for you, make them an honest offer and let them decide if it works for them. Companies obviously can’t put out multiple offers for the same position at a time, so there’s a natural tendency for companies to be careful with offers and only put them out if they are sure they’ll be accepted. But in this kind of case, if it’s an offer the candidate would reject out of hand, then they will reject it immediately and you lose nothing.
> It's extraordinarily hard to build a community around a fork

it follows quite naturally, that reasoning to fork doesn't have enough community support, which only means one thing - you're wrong about clojure community's opinion on state of things around clojure.
> This is assuming you can 100% trust your partners (which should be a requirement when starting a company anyway) because a GbR implies that each of the partners is fully liable for the others' actions and decisions made with regards to the company, too. Creditors can recoup their assets from any of the partners.

That level of risk is nuts. Most companies would never get started, or lots of founders would get screwed.
Try to Code Without If-statements: You might uncover better solutions
That's exactly we have done so far. 80% of our business is either referral customer or repeat customer.

10 to 20% of times we have failed miserably to satisfy customers needs.
I completely agree and these days I follow exactly that strategy, to good effect. However I think it's still, in general, damaging to general perception.

Another factor is that most of my encounters with such groups has been while working for organisations looking for a cheap option. I strongly suspect that this is common and results in hiring low quality groups with mediocre people - again tainting popular perception.
Yes, I tried Ukraine and the quality of back-end code was much higher. Front end UI was not great, but it worked.
> In most cases however this doesn't matter as much as is often presumed.

I only hope you don't fail to deliver and get sued, misuse client data and get sued, get accused of patent infringement et al.

Seen all of these happen.
Unable to download FreeMind from the link on the github repo at the moment.

People can use https://en.softonic.com/download/freemind/windows/post-downl...
Uber lodges appeal over London ban
I watch TED videos.
git blame regret: "who wrote this crap?...oh, right, I did"
Hey! Thanks for submitting the article to Hacker News. I'll be traveling today but if anyone has any questions I'd love to talk about our experience.