skysight-inc/HackerNews huggingface dataset:
Have been doing iOS programming with Swift 2.5 days per week for a bit less than a year now. The first step I took was to read through Apple's Official Swift Language Guide[0]. After completing this I followed the Stanford course on iOS Development with Swift[1]. I didn't spend much time on this, I did this in a Friday afternoon(language guide) and full weekend(watching lectures), since I believe more in learning by practicing.

I've really come to like Swift as a language, since it's concise and simple. The iOS SDK however is not so much fun. Learning the iOS SDK will take a lot of time before you develop routines to approach your problems. I'm still learning about strange behaviour from the SDK and getting frustrated by it every time I use it. It's important to keep things fun, look through the trending Swift repositories on GitHub, follow #iosdev on Twitter and /r/iosprogramming, you will learn a lot if you keep up to date with these sources.

Some of the habits I've created, which might be handy to other people:

- I manage dependencies with CocoaPods, with no dependencies residing in my repository.

- I don't use storyboards or xib's at all. Everything I do is with SnapKit[2]. This takes some time to learn, but it greatly improves the diffs and overview on how the ui elements are constrained and set up.

- I use API endpoint enums which get called by an API Handler, which uses Alamofire[3] to execute the api requests.

- I try to use as many tools provided by Fastlane[4]. Especially if you're developing many Apps, or incrementally building an App, releasing a new version every two weeks: automate all the things. Otherwise you will waste so much time simply waiting for a process to complete.

Side note(if you're interested):

I'm currently developing a tool called Evans(will write a blog post as soon as it's reasonably finished), which performs all kinds of routines automatically. It for example listens to GitHub comments like '@evans screenshots' on a pull request. Evans then emits a request to one of the build slaves, which retrieves the branch, builds the project and runs the screenshot routine, puts the screenshots in an s3 bucket and posts a link as a response in the pull request.

[0] - https://developer.apple.com/library/ios/documentation/Swift/...

[1] - https://itunes.apple.com/us/course/developing-ios-8-apps-swi...

[2] - https://github.com/SnapKit/SnapKit

[3] - https://github.com/Alamofire/Alamofire

[4] - https://github.com/fastlane/fastlane
There are plenty of tours that operate in North Korea.

Koryo Tours is one that I took a few years ago.
Lessons learnt from 10+ years with actors in C++
Benefits of Having Online Project Management System for Business
> There’s been speculation about whether the UK, China or
> the NSA are to blame — but today’s revelation strongly
> suggests that it might have been the US.

Why would the NSA infiltrate Juniper to change the Dual EC DBRG parameters, when the standard parameters are already exactly how they want them?

There is a good chance they noticed that their attacks against Dual_EC_DBRG weren't working - but to reveal that pre-Snowden would prove that they knew the private key and were exploiting it.

That said, I understand there was more than one back-door disclosed.
> holocaust survivors have on average longer lives

Sounds to me like they might have the causation reversed. Maybe only healthier/tougher than average people survived in the first place.
IMO, loading by hash and/or sign are better solution.
Their name is the National Security Agency, after all. It seems that they should be focused on the security of all Americans, and rather than notifying and helping secure Americans they do the exact opposite.

Is there another division in the government that reduces or allows the security of Americans to be so blatantly abused?

If the military had just given away the keys to our nukes, Someone's head would roll, but because this is tech, and congress only sees a black box, they can't see that the NSA is more often acting against Americans' best interests rather than for.
The lineage is hardly an excuse - PC started out just like ARM is, with manual IRQ assignment, no hw detection, and the like. But this was solved in the mid-90s with plug and play standards. It's really sad that in 2015, embedded SoCs still don't have anything comparable.
> What nudged me out of my love affair with CLJS is when I needed to implement a really simple async pattern in CLJS.

What? Async/await in CLJS is:

(defn async-fn []
(go true))

(go (<! (async-fn)))

How is that syntactically and conceptually complicated compared to async/await?
> Also, for using a system that's allegedly broken, the US is the country that has been the most innovative in terms of software for decades in a row now.
I was not remarking about Theranos, but rather to ThomPete's statement.

Rigorous science is not sufficient (e.g. the Shechtmans/Warrens that we don't know about -- it is pure hubris to believe that all those were eventually vindicated), nor is it required (e.g. Vioxx, Thalidomide, ADA recommendations, baby peanut allergy recommendation, dietary cholesterol recommendation, dietary sodium recommendation).

If Theranos is a lesson to entrepreneurial scientists it is probably: "Don't waste your time failing quietly and cheaply, when you can fail extravagantly and retire rich"
I totally agree. My first job was exactly as you describe. I graduated in 2009, in the teeth of the recession, and every company I applied to had a hiring freeze... except for one, which was known to be a miserable place to work, and known for chewing up programmers and spitting them out after six months to a year of grinding labor. I signed on anyway, because, at the time, I needed a job, any job on my resume. So I took the job, but I was cognizant of the fact that it was a "gig", not a career, and I spent time burnishing my portfolio outside of work, and kept looking. The moment the job market started to thaw, I jumped ship for a modest improvement in pay and a massive improvement in working conditions.

That said, I think you're underestimating how good the job market is for programmers right now. Yes, your first job might suck. But if it does, try to recognize that fact early and make plans to switch companies at the earliest possible moment. Look in other cities (or even other countries) if you must. This is, after all, advice for young programmers, so they're not likely to have houses, family, etc. tying them down to a single location.
> So, am I missing something, or are they, or both?

They are.
Show HN: Microsoft Face API Implementation
I'll assume the main keywords are "one and a half year ago". Me personally, I like the fact that React is a library wheras Ember is a framework. React doesn't dictate how you code your program, while Ember does.
This dataset seems to include all businesses and not just technology startups.

In my experience, those who attempt to start small businesses often learn the hard way of the importance of accounting and financial planning. Can't just run a business out of your personal bank account.
I agree with you that to blame corporations about every bad thing is going too far.

But I also think that you go too far exculpating them.

To say "all of these things are democratic, they reflect the will of the people", is a very naive comment.

Tobacco is a good example of a need that was just created.

Or in the news not so long ago:

Coca-Cola 'spends millions on research to prove that fizzy drinks don't make you fat' ( http://www.telegraph.co.uk/finance/newsbysector/retailandcon... )

We could find so many examples as you need.
Their primary mission is to defend (including both protecting US information security and gathering intelligence) - cases like this show that they have compromised their direct information security defence mission to further their offensive capabilities.
There's an event here in London, Tech meet City, that requires an AngelList profile to apply to it. It's a sort of pitch fest.
You use the word "therefore" as if you had presented a syllogism, but for an actual solid argument you need to explain how the conclusion follows from the premises. Presumably you are making use of a principle that implies that the existence of people suffering more than you means that your suffering is lessened. That can be disputed, but you haven't even argued for it yet.
The piece is quite directly a statement that the focus on Snowden's is a distraction from the issues he raised, and is actively being kept as such by people who interest is in avoiding the substantive issues (and, while it doesn't say this, one might argue that the actual discussion of the issues raised by Snowden is essential to actually going anywhere with the debate about his ultimate status, which until the issues debate happens is just a noise that produces nothing.)

And it's not a stance by a politician. The HN headline was misleading (by including "Sanders" as if it were part of the title or the original source, as well as -- and this has still.not bee corrected -- by omitting the "(2013)" that should be included): Sanders' office reposted this wheb ut was current as recommended reading, but the source is Ron Fournier of the National Journal, and there is considerable distance between reposting something as writing on an important issue that people should be aware of and adopting it as Sanders own position.
> This is the first time I have seen any snowden document.

Seriously? Then there's interesting[1] reading available[2].

[1] For various definitions of "interesting" ranging from "meh" to "OMGWTF" depending on your interpretation and politics.

[2] https://en.wikipedia.org/wiki/Global_surveillance_disclosure...
Aviation and marine fuel demand is only a small fraction of global demand.

Think about it; for most of history shipping was entirely wind-powered. Clearly not comparable to today's massive freighters, but don't rule out new technologies finding a way to harness more wind and sun at sea.

And at the end of the day if there's a surplus of renewable electricity, it can be converted into high density fuels such as gas or diesel. That technology exists today; it can only get better especially if a cost incentive existed.
From my limited POV, this is how I see most of the newcomers to JS community currently behaves. And it's a good example of 'learning by doing', which is the advice that everyone gives around here.

- Do some research, look what successful/smart/sane people are using/working on, and why.

- Jump in, hack stuff, make things work.

- Learn while creating. Discover the insights behind the choices that people you're following made.

- Start making your own informed choices.

As long as you're not stuck in the step 2, and advance beyond doing what everyone is doing, you're probably on the right track.

That's how I learned to build maintainable/scalable/successful applications.

It worked out perfectly for me.

Edit: typo, clarified first sentence.
>But, equally I feel the author is speaking of the go-big-or-go-home model of "startups"

I think startups, as far as Hacker News is concerned, are "go big or go home" businesses. Quoth Paul Graham:

A startup is a company designed to grow fast. Being newly founded does not
in itself make a company a startup. Nor is it necessary for a startup to work on
technology, or take venture funding, or have some sort of "exit." The only
essential thing is growth. Everything else we associate with startups follows
from growth.

http://www.paulgraham.com/growth.html
I've been through many, many tech interviews during my 25-year career, and not one of them has been objective. I have always been hired based on whatever opinion the interviewer formed about me within the first minute of meeting me. The rest of each interview has always been a drawn-out, cumbersome attempt for them to justify their initial, subjective decision.

In my experience and opinion, software engineers are some of the world's most incompetent buffoons at interviewing; myself included.
Let me see if I've got this right.

TL;DR: you worked at Google where they said average CPC was important and you worked on a search related startup that sold relabeled Google ads (presumably through the AdSense for Search program?) where Google paid some contractually fixed fraction of revenue on searches (revenue on these searches is not necessarily correlated with revenue on main Google search, correct?). At this startup, they wouldn't let you resell these ads for mobile searches because it would hurt margins (seems like shaky reasoning to me, who doesn't like more money / more profit?).

Then a smattering of recent news stories with tangential relationships to your main thesis about margins (YouTube (when have the margins been broken out on this?), Android (not sure how this fits into your narrative about the decline of Google's growth)) mixed in with some real medium term competitive threats (EU, Facebook/Bing (didn't FB used to redirect their search traffic to Bing? not sure that made much of a difference)).

Here's some alternative narratives:

a) There's far more to profitability on online advertising than average CPC, like query mix as I mentioned before. Additionally, advertising on Google owned & operated properties have been continually far more profitable and growing at a much faster pace than relabeled search advertising or AdSense on third party websites. Google has refocused their engineering / sales efforts on advertising products on their owned & operated properties and de-emphasized properties like Blekko.

b) Google's PE ratio has gone from <20x in 2010 to >30x today. The market believes Google's growth prospects are brighter than ever.

To summarize, I also keep a careful eye on Google / other tech company's financials and how they relate to both my personal work and larger trends in the industry as a whole. I simply disagree with your theses that a) search engine margins are decreasing and b) that the search engine business needs to grow at a faster rate for Google to continue to grow sustainably due to a) the continued power of direct response search advertising and b) other growth areas like video, brand, mobile, and new markets.
>There's no sign in the operating system, the researchers say, of the kinds of cyber attack capability North Korea has been accused of.

What were you expecting to find? A text file named sonyhack.txt?
Actually I compared working for Google or for a startup in the US to working for Google or for a startup in Israel.

Regarding your point, the difference in prices is not nearly large enough to wipe out the difference in the amount saved working for Google in the US vs working for Google in Israel.
If you discuss and regulate the privacy issues in times of peace it limits, or at least hinders, their ability to cause harm when they can take advantage of fear or rage.
That's the commenters point. We don't know what data was sourced for "failures"
Yep. Bare metal refers to your code accessing the silicon without the help of other drivers or an OS. You write the code to directly access the IO pins that drives the LCD or LEDs or to read the buttons, or other on board circuitry.
The psychological tolls of being a digital nomad
They might have also learned that lesson with Solyndra in 2011.
You could say that about any sci-fi, they are all set in the future.
Click Fraud Detection: Adversarial Pattern Recognition Over 5 Years at Microsoft [pdf]
According[1] to Dan Geer[2], the intelligence community is all offense:

Chris Inglis, recently retired NSA Deputy Director, remarked that if we were
to score cyber the way we score soccer, the tally would be 462-456 twenty
minutes into the game, i.e., all offense. I will take his comment as confirming
at the highest level not only the dual use nature of cybersecurity but also
confirming that offense is where the innovations that only States can afford
is going on.

[1] http://geer.tinho.net/geer.blackhat.6viii14.txt

[2] (among other credentials) CISO at In-Q-Tel
You said, "if [the patent system] didn't work, the US would not be the most innovative software country in the world."

So your claim is that the US is innovative because of its patent system.
Well that article was completely devoid of information.

Here's the post by the researchers themselves: https://srlabs.de/pos-vulns/

tldr: POS card readers have poor security - their HSMs leak their keys, and many of them don't have unique keys so you can impersonate them
I completely agree with your characterization of how beginners can feel. That said,

> If you are suggesting that instead I should learn by sitting down for six months in an ivory tower and learn all the theory and function of every part of the software ecosystem

It's not simply a choice between "learn for 6 months" and "use whatever the latest thing is". You seem to be advocating for the later, which I think is just as unworkable a solution as the former. For instance, a nice medium ground would be to read the github README as well as the front-page website of the candidates.

Also, as someone else here pointed out, you can't kill off gulp/grunt even if webpack exists, because webpack is not a task runner, and some people use the task-runner features of gulp to do more than combine modules, etc.
Enough ketcheh! Let's talk Jabascript gais!
It depends how you interpret non-neutrality:

1. Laws written to allow different "lanes" of traffic, with protections that prohibit censorship and don't raise the bar of entry for websites.

2. Providers mostly have free reign to slow/stop any data that crosses their network and charge anyone however they want.

Given Facebook's internet.org and similar "zero-rating" schemes, I'm not sure you can dismiss argument 2 so easily.
People really are confused about patent trolls ans NPEs. An NPE is not a troll.
"It's essential because", huh, small companies are going to pay 10-99,000 fee? I don't think so. small means that is around the same cost as settling, but it has some unknown % chance of working, wheras settling will work 100%.
DHH on the immediacy of PHP (2008)
If the NSA/GCHQ knew about those backdoors but didn't introduce them it's even more worrying.

Finding/buying a zero day exploit is what most SIGINT intelligence organizations around the world could more or less easily achieve.

Penetrating an organization to the point of being able to introduce foreign code into their products which remained there for at least several years, as well as launch a fairly sophisticated crypto attack which would only benefit some one if they had the ability to tap into large scale internet traffic isn't something that many organizations if at all outside of the NSA-GCHQ coop should be able to achieve.

Russia and China are quite far behind, Germany and France don't have the budget (as far as appropriations goes, if they wanted too they could surely find the money), Israel could pull the exploit off both technically and operationally but it most likely lacks the ability to gather internet traffic on wide scale (it is probably one of the best out there as far as wireless sigint goes but it lacks the resources to be able to tap into world wide internet cable infrastructure) which makes it unlikely that they would introduce the VPN backdoor (unless it was for a very specific target, although Juniper together with ZTE pretty much rule the Iranian ISP market).
This either means that either Russia and China are playing way beyond their presumed level of both capability and competency or there are other players most likely private hanging around the court which should is even more frightening.

Ofcourse there's still a chance that the NSA not only knew about those backdoors but actually introduce them but at the time being all the supportive documents just show that they discovered them rather than introduced them.
> I don't care if that opinionated path changes every month

Good for you, you'll feel right at home because that's exactly what's happening in JS-land, and it's a major reason many of us opt to stay the hell away from such a fad-driven development ecosystem.
For businesses that have to buy in stock cash flow is critical, get that wrong and your revenue can collapse in an instant as suppliers stop shipping.
surely filtering out the false applications should have been the task of programmers / DB admins once the data was all in the DB.
The Ancient Egyptian Discovery of Binary Star Algol’s Period Confirmed
Core Bitcoin Devs Leave Project, Create New Currency Called Decred
Why bring him back? Perhaps on Mars his WaterCredits and PepsiCo-backed drinking water loans could find a good market.
It's interesting that first little JavaScript libraries and one-liners were popular in the 1990s.

Then AJAX and large framework libraries like Yahoo YUI, Ext JS, Google Web Toolkit (GWT) got popular.

Then JQuery a more lightweight library got popular. Then John Resig's (JQuery) book "Pro JavaScript Techniques" (2006).

Later Douglas Crockford's book "JavaScript the Good Parts" (2008) were highly influential. HTML5 and JavaScript5 came along. A new wave of JS5 vanilla style influenced by JS5 and Crockford's book got traction and more and more replaced JQuery (2010 onwards). HTML5 browsers got widespread, the JS performance got a lot faster (JIT VMs) and attracted a lot more developers.

CoffeeScript and new single-page frameworks like AngularJS and Ember.js got popular ca. 2012.

Google initially focused on Dart language as a replacement for Javascript and later transpiled to JS (beside others). Microsoft aquirehired ex-IBM group now known as Monaco code editor (VS Online, VSCode, etc) and created TypeScript that suits their C++/C# massive code base and coding pattern better. They influenced the development of ES6/7 to include "classes" syntax, etc.

Google added "Shadow DOM" feature to Chrome and proposed it as a new HTML5 feature. http://www.html5rocks.com/en/tutorials/webcomponents/shadowd...

Shadow DOM hasn't been integrated in other browser (http://caniuse.com/#feat=shadowdom ) though Facebook thought the idea was good ("Virtual DOM") and re-implemented the idea as JavaScript library; what is now known as ReactJS framework (got popular in 2014).

On the otherside NodeJS with NPM and its ecosystem of many tiny libraries got popular in 2011.

ES6/7 got popular on server and client side (though later still needs a transpiler step).

So we are again with huge JS framworks on the client side (1MB minified JS files are common but not funny on mobile devices). And highly modular small libraries on the server side (NodeJS).

Probably in time when full ES6/7 and Shadow DOM support gets traction in all modern browser, we will see another wave of more lean vanilla ES6/7 code without the huge libraries. You can write a super responsive and fast JS web app in less than 300KB code. You ask for trouble with your 1+MB JS file, especially on mobile devices that will crash or the users has to wait 30+sec on a cellular connection.

Lean vanilla JavaScript is great and high performant. Over-engineered frameworks make your life easier to start but will make it harder to stay in touch and maintain. Hopefully ShadowDOM browser support gets traction.
Nope. You are reading it completely wrong. It's saying patents can be declared invalid in more cases, nothing to do with "declaring a patent dispute invalid."
I can't tell if you're being sarcastic or not.

Wouldn't a doctor be a good person to ask what's good for you? amazon has about 50,000 different diet books, it's really not obvious what's "right". Even the glorious USDA has a lot of industry influence in what it recommends/accepts. The food plate is better than the water, kale, and doughnut diet, but it has its own issues.

so, yeah, for a general practice they should probably talk about quitting smoking, getting exercise, avoiding being overweight, guns, etc. pretty much anything on the top 10[1] seems like a good idea.

[1] http://www.cdc.gov/nchs/fastats/leading-causes-of-death.htm
> strategy of self-liquidation that tobacco companies used

Does anyone have a source for that?
I meant in approach, this one seems like Uniqlo of department stores. Will we see "Uniqlo of X" in other areas as well?