freeCodeCamp Icon


Learn to code with free online courses, programming projects, and interview preparation for developer jobs. • 9 Stories
All Sources

Flavio Copes freeCodeCamp

Every developer should have a blog (here's why, and how to stick with it)

Flavio Copes is a great person to take this advice from. He’s been blogging for “more than 11 years,” more or less consistently. In this post he covers not only what you need to know to be successful, but also what you need to forget. One of ways I learn best is by doing. I literally decide on a topic I think I know something about, and I drill down in a spiral loop through things I didn’t know, or I didn’t even think about. They say you never fully understand a topic until you are able to explain it. Blogging is a low barrier to explaining things.

read more

Virginia Balseiro freeCodeCamp

How I finished the entire freeCodeCamp curriculum in 9 months while working full time

Virginia Balseiro shared her story and experience of completing the freeCodeCamp curriculum last year. It wasn’t easy, I won’t lie. It helped that most of my friends and acquaintances don’t live near me, and I live in a small town that doesn’t offer a lot of entertainment opportunities. …I couldn’t just quit my job and study full time, since I needed to pay the bills, so I had to get really good at 3 things: Time management Discipline Organization Not only does Virginia share her experience and strategy, but also other supplemental resources she used on her freeCodeCamp journey.

read more

Quincy Larson freeCodeCamp

freeCodeCamp – the first BILLION minutes

Quincy Larson: People have now spent more than 1 billion minutes using freeCodeCamp. That’s the equivalent of nearly 2,000 years. To put it another way — if freeCodeCamp usage was a person, it would be old enough to have broken bread with Jesus himself. Congrats to everyone who’s helped freeCodeCamp reach this milestone! Quite an accomplishment, and just the beginning for the tiny nonprofit that’s teaching the world to code. Quincy shares a bunch of numbers in this post, including traffic comparisons between and funded startups.

read more

freeCodeCamp Icon freeCodeCamp

We fired our top talent. Best decision we ever made.

Would you fire your top contributor — someone with a deep understanding of your product’s architecture and a ton of domain-specific knowledge? Jonathan Solórzano-Hamilton writes on the freeCodeCamp blog about this exact scenario… “You will never be able to understand any of what I’ve created. I am Albert F#@$ing Einstein and you are all monkeys scrabbling in the dirt.” He declared this in front of the product design team, developers, management, and pre-launch customers. One of our project sponsors had the temerity to ask when the problem crippling our product would be fixed. No one gets a pass on being a jerk. I personally subscribe to the “no asshole rule,” and do my best to purge the assholes as soon as possible. The sooner the better, for everyone. Have you heard of the book on the subject? Here’s why Robert Sutton wrote ‘The No Asshole Rule’

read more

Tigran Hakobyan freeCodeCamp

Reflections on being a remote developer

Tigran Hakobyan, remote software engineer at Buffer, writes on the freeCodeCamp blog: Working remotely is very different from working in the office. I don’t think you fully grasp the difference until you actually start being remote. For someone like me who never worked in a remote environment, the beginning wasn’t smooth and it came with challenges. I can clearly remember my very first day at Buffer… Tigran also shares a pretty comprehensive breakdown of a typical workday.

read more

Manuel Vila freeCodeCamp

Let’s fix the good old command line

Manuel Vila: We are using more and more command-line tools, and while many of them are really good, I think they could be even better if they were based on more modern foundations. Because our tools are based on ancient paradigms (*nix, Bash, etc.), it’s difficult for them to be both customizable and easy to use. After working for a year trying to solve this problem, he came up with “resources”, which he says: brings an object-oriented interface to the command-line tools, making them a lot more flexible, composable, and user-friendly. The curmudgeon in me immediately thought, “old dog … new tricks”, but Manuel has a reply ready: I am well aware that I am not going to change 50 years of old practices by myself. It has to be a collective effort. So I’m trying to communicate as much as I can to find the few people crazy enough to join the adventure. Are you “crazy enough” to go on the adventure with him? Click through to find out more.

read more

0:00 / 0:00