HN user

quincyla

692 karma
Posts118
Comments36
View on HN
www.freecodecamp.org 3y ago

After growing 60% yoy for 5 years, freeCodeCamp grew 100%

quincyla
1pts0
www.switchup.org 5y ago

University vs Coding Bootcamp Alumni Analysis for Apple/Amazon/MS/Google/FB

quincyla
3pts0
twitter.com 6y ago

Possible zero-day in YouTube's commenting system

quincyla
12pts0
www.freecodecamp.org 6y ago

How to build a programming YouTube channel 5 years 1M subscribers later

quincyla
2pts0
www.freecodecamp.org 6y ago

How FreeCodeCamp Made $2k from the Brave Browser

quincyla
2pts0
www.freecodecamp.org 6y ago

In an age of social media blogging platforms, exclusivity is a good thing

quincyla
1pts0
medium.freecodecamp.org 8y ago

DevDocs.io turns 5 and joins the freeCodeCamp.org community

quincyla
3pts0
medium.freecodecamp.org 8y ago

The authoritative guide to blockchain development

quincyla
2pts0
medium.freecodecamp.org 8y ago

Stories from 300 developers who got their first job in their 30s, 40s, and 50s

quincyla
3pts0
medium.freecodecamp.org 8y ago

How a Nigerian teen with no laptop built apps with only his Nokia feature phone

quincyla
4pts0
medium.freecodecamp.org 8y ago

Statistical Inference Showdown: The Frequentists VS the Bayesians

quincyla
1pts0
medium.com 8y ago

The Hitchhiker’s Guide to Machine Learning in Python

quincyla
4pts0
medium.freecodecamp.org 9y ago

REST in Peace. Long Live GraphQL

quincyla
94pts88
medium.freecodecamp.org 9y ago

Blockchain is our first 22nd century technology

quincyla
4pts0
medium.freecodecamp.org 9y ago

Common Data Structures Explained with Videos and Exercises

quincyla
156pts15
medium.freecodecamp.org 9y ago

Counting uniques faster in BigQuery with HyperLogLog++

quincyla
3pts0
medium.freecodecamp.org 9y ago

A UX critique of the Nintendo Switch

quincyla
2pts0
medium.freecodecamp.org 9y ago

Finally coding productively on an iPad

quincyla
3pts0
medium.freecodecamp.org 9y ago

Does Data Compression Matter on a Quantum Internet?

quincyla
1pts0
medium.freecodecamp.com 9y ago

Vue.js: a 3-minute interactive introduction

quincyla
5pts0
medium.freecodecamp.com 9y ago

All 500+ engineers at Grab use this front end development guide

quincyla
2pts0
medium.freecodecamp.com 9y ago

How the “token network effect” is a new business model for the decentralized web

quincyla
6pts1
medium.freecodecamp.com 9y ago

Fixing multi-time zone meetings with open source

quincyla
3pts0
medium.freecodecamp.com 9y ago

Building a 360 VR app in 10 minutes with Android and Unity

quincyla
1pts0
medium.freecodecamp.com 9y ago

Parsing math expressions with JavaScript

quincyla
3pts0
medium.freecodecamp.com 9y ago

Which Projects Need React? All of Them

quincyla
2pts2
medium.freecodecamp.com 9y ago

How we taught dozens of refugees to code and helped them get jobs

quincyla
2pts1
medium.freecodecamp.com 9y ago

How we taught dozens of refugees to code, then helped them get developer jobs

quincyla
4pts0
medium.freecodecamp.com 9y ago

After building my first React Native app, I’m now convinced it’s the future

quincyla
1pts0
www.quora.com 9y ago

Why do we still code?

quincyla
2pts0
Mail for Good 6 years ago

I use Mail for Good every week to send my email blast to 3.5 million people. It works fine and is stable.

We haven't made any big changes to it recently because it hasn't broken. There is definitely some maintenance we could do as far as updating libraries.

We're hoping to re-write parts of it to use AWS Lambda instead of a Linux server, so we can further simplify use of it for less-technical users (a lot of nonprofits don't have developers on staff).

Gitter has been a huge part of freeCodeCamp's community since the beginning. Thousands of people have asked questions there, and most of them have gotten helpful answers quickly. This is thanks to the experienced developers who contribute their time and expertise in there.

Like IRC, it's a great platform to ask and answer questions on. Find the right rooms and talk to the right people.

Author here. I just realized someone had submitted this to HN. I spent a lot of time researching and writing this article, and am excited to read any feedback you may have.

Also, here's how you can contact the FCC directly:

1-888-225-5322

press 1, then 4, then 2, then 0 say that you wish to file comments concerning the FCC Chairman’s plan to end net neutrality

Or on the web:

https://www.fcc.gov/ecfs/filings/express Under Proceedings, enter 14-28 and 17-108

Suggested script:

It's my understanding that the FCC Chairman intends to reverse net neutrality rules and put big Internet Service Providers in charge of the internet. I am firmly against this action. I believe that these ISPs will operate solely in their own interests and not in the interests of what is best for the American public. In the past 10 years, broadband companies have been guilty of: deliberately throttling internet traffic, squeezing customers with arbitrary data caps, misleading consumers about the meaning of “unlimited” internet, giving privileged treatment to companies they own, strong-arming cities to prevent them from giving their residents high-speed internet, and avoiding real competition at all costs. Consumers, small businesses, and all Americans deserve an open internet. So to restate my position: I am against the chairman's plan to reverse the net neutrality rules. I believe doing so will destroy a vital engine for innovation, growth, and communication.

This information is taken from this thread on Reddit: https://www.reddit.com/r/technology/comments/6894i9/heres_ho...

The EFF explains how this was done here:

Back in 2011, several ISPs were caught red-handed working with a company called Paxfire to hijack their customers’ search queries to Bing, Yahoo!, and Google. Here’s how it worked.

When you entered a search term in your browser’s search box or URL bar, your ISP directed that query to Paxfire instead of to an actual search engine. Paxfire then checked what you were searching for to see if it matched a list of companies that had paid them for more traffic. If your query matched one of these brands (e.g. you had typed in “apple”, “dell”, or “wsj”, to name a few) then Paxfire would send you directly to that company’s website instead of sending you to a search engine and showing you all the search results (which is what you’d normally expect). The company would then presumably give Paxfire some money, and Paxfire would presumably give your ISP some money.

In other words, ISPs were hijacking their customers’ search queries and redirecting them to a place customers hadn’t asked for, all while pocketing a little cash on the side. Oh, and the ISPs in question hadn’t bothered to tell their customers they’d be sending their search traffic to a third party that might record some of it.

Source: https://www.eff.org/deeplinks/2017/03/five-creepy-things-you...

For what it's worth, FreeCodeCamp.com has 1/3 the page views that Medium has, with only 3 full time staff. https://www.similarweb.com/website/freecodecamp.com?competit...

I love Medium and I hope it succeeds. It sounds like their headcount was substantially higher than it needed to be and that this layoff was the right move.

I wish Ev had mentioned all the additional facts that are in this article by one of Medium's investors: https://500ish.com/long-medium-b9ddfe2c3a0a#.ch2benant

I'm a former English teacher and school director, and I created FreeCodeCamp.com two years ago specifically to help people transition into web development as a career. We have a large community of career-changers, more than 5,000 of whom have now gotten their first developer job.

Thanks for the clarification on TOR. I guess I should change "virtually impossible" to something more moderate like "extremely difficult" as colluding with a network to gain access to the network.

How reliable would this approach be if, say, 100x the number of people who currently use TOR start using it?

These seem to be non-interactive (text with occasional videos). Free Code Camp is fully interactive coding, with test suites, in the browser.

Also, this is 35 hours including projects. Free Code Camp takes closer to 2,000 hours with projects.

I wrote this article to explore why anyone would ever think that learning to program is easy, their incentives behind doing so, and the effect on people new to the field.

Our "business model" is to keep costs as low as possible and sell merchandise. We will never charge for our curriculum.

We have turned down all offers of funding specifically to avoid a situation where an investor could try and force us to do otherwise. We will remain free and open source.

If institutional partners treated MOOCs as a marketing exercise for their university's brand, instead of trying to monetize courses and certificates, people could continue to have this content for free. Unfortunately, universities don't exactly exemplify long-term thinking.

Most of the content for these MOOCs is created by professors as part of their jobs, so this content is owned by their universities. I bet a vast majority of professors would prefer their MOOCs to stay open.

Most of the work has been done already, and the quizzes and exercises are automated, so there's no practical reason these videos couldn't be hosted on YouTube and thrown into an open source MOOC framework like EdX's and continue to serve millions for a few hundred a month in server costs. Except that Coursera is explicitly forbidding non-private use of these courses.

For what it's worth, Free Code Camp gets about 1/8 of the traffic Coursera does, and our (non-opportunity) costs are pretty minor. I don't think hosting these MOOCs would add much to the burden.

If only the individual professors who created these MOOCs could give us permission to host these courses. But there's no way we're going to get anywhere with the university bureaucracies themselves.

There is wisdom behind these bullet points. This wisdom could be better communicated through a series of fleshed-out articles with real life examples.

Otherwise, these points are difficult to contextualize, retain, and apply.

In light of all the recent data breaches, and waking days of my life spent reseting passwords, I think there is only one solution to this mess. Let's destroy all passwords. It starts with developers.