From open source project to a $3.8 million dollar seed round to transform Gatsby.js into a full-blown startup that's building what's becoming the defacto modern web frontend. In this episode, we talk with Jason Lengstorf about this blazing-fast static site generator, its building blocks and how they all fit together, the future of web development on the JAMstack (JavaScript + APIs), the importance of site performance, site rebuilds, getting started, and how they're focused on building an awesome product and an awesome community.

Learn about the fundamentals of JavaScript to ease your learning/usage of React. After all my teachings about React, be it online for a larger audience or on-site for companies transitioning to web development and React, I always come to the conclusion that React is all about JavaScript. The following walkthrough is my attempt giving you an almost extensive yet concise list about all the different JavaScript functionalities to complement your React application.

This is how you accomplish step 1 to becoming a Go contributor. Before we can become Go contributors, the very first step is being able to build Go from source. I followed the official doc and filled in the blanks a bit to figure out how to get everything working. This post is part of a series from Carolyn Van Slyck called Adventures in Gopher Source. The goal of the series is "for more of the gopher community to become upstream Go contributors."

Is this really a chance to get $10,000 in equity-free funding just for completing a free online course? Seems there's also $50,000 in credits to a variety of other services too. Startup School is a free, 10-week, online course. It’s designed for any startup founder who would like to get help through the earliest, most difficult challenges of starting a company. The course will begin on August 27, 2018 and applications are now open at StartupSchool.org.

A dependency-free port of the asciichart library. It includes a CLI for feeding it data directly.

In this special episode of JS Party, we're sharing a full-length episode of our new show, Away from Keyboard. This show explores the human side of creative work. In this episode, Tim talks with Justin Jackson about his parents, dealing with depression, and a new business he's co-founded.

This post is a simple, step-by-step explanation of how Patrick created 'an insanely simple “did” file accessible by terminal'. What's interesting about it to me is not how to do it, but the idea of doing it itself. His motiviation: Time flies by when you’re learning how to code. Its super important to take a second every once in a while to simple write down what you did during the past mental sprint. Writing down what you learned solidifies the knowledge. This is a great truth, and one that applies far beyond learning how to code. Sometimes we need a did.txt just to recognize how much we've accomplished recently. For me, there are days when I get to the end and feel like I didn't really accomplish much. If I'd catalogued my wins throughout the day as they occurred (no matter how small), I bet I'd feel different about that. However, I'm both busy and lazy (a hellacious pairing) and wouldn't keep up with this habit unless it were dead simple. Patrick's 'did.txt' solution is about as simple as it gets...

How do we know whether an open source project is doing well? Number of contributors? Number of users? Number of appearances on The Changelog*? Nadia's been researching these things: A lot of people are interested in measuring the health and velocity of open source projects. After digging through the current research landscape, I’d like to summarize the most common approaches I’ve seen, and my conclusions here. One conclusion she's come to is that our current methods aren't cutting the mustard. Find out why and what some of her suggestions for improvement are in this excellent piece. *yes of course that's a joke

Usually, we don’t need to know the internals of an engine which runs our code. The browser vendors invest heavily in making the engines run code very fast. Great! Let the others do the heavy lifting. Why bother worrying about how the engines work? Good question. Read the article to find out why.

Lyndsey Ferguson: Unit testing and the tests themselves are written by humans. Humans are prone to error. Unit tests and the testing infrastructure can be imperfect. The test_center plugin includes tools that remove (or alleviate) the effects of an imperfect test infrastructure. (fastlane is a popular way to automate building/releasing iOS and Android apps.)

I first heard of Justin Jackson about six years ago. Back then, he was consulting full-time for a company with the dream of going independent. Fast forward to 2018, and after building a successful business, he's now embarking on a new adventure. Justin talks about his parents, dealing with depression, and a new business he's co-founded.

Waytab connects to your browser bookmark, Github, Twitter, Pocket, Pinterest and Unsplash account to remind you of your stars, likes and bookmarks every time you open a new browser tab. This looks like a good idea, well executed. I've long given up on bookmarking, liking, and starring stuff because I never go back and revisit. Waytab changes all that.

These are always fun. React, anyone?

Jordan Eldredge has been working hard to make Webamp even more rad: Take a trip down memory lane with this faithful WebGL port of MilkDrop, the iconic music Winamp visualizer. Check it out in Chrome and Firefox. What should you listen to while the visualizer does its thing? Our episode all about Webamp, of course. 🤓

Dennis Reimann: The UIengine is a tool to build pattern libraries and documentation for design systems. It helps designer and developers to work closely together and offers features to boost their productivity. Alternatives already exist in the ecosystem (Fractal, Storybook, etc). Why reinvent the wheel? Most of the existing tools focussed on the component development, but lacked ways to also provide good documentation. Some were limited to using a specific templating language or framework, which was suboptimal for me: As a freelancer I am working on many projects and each one has its own set of constraints and requirements. I wanted to build a tool with an open source license, which I could use and extend with every project I work on.

Ives van Hoorne writes on Medium: Personalizing color schemes is one of the most important things to have in an code editor. CodeSandbox didn’t have any way to personalize colors in the editor since release, but I’m happy to announce that we do now. The best part is that we were able to reuse a big chunk of logic from VSCode directly and also support any VSCode theme natively in CodeSandbox!

Hasura helps you build GraphQL apps backed by Postgres or incrementally move to GraphQL for existing applications using Postgres. This looks superb.

gaia is an open source automation platform which makes it easy and fun to build powerful pipelines in any programming language. Based on HashiCorp's go-plugin and gRPC, gaia is efficient, fast, lightweight and developer friendly. Gaia is currently alpha! Do not use it for mission critical jobs yet!

This is a virtual treasure trove of information! But like all good treasure, you'll have to do some digging to find what you're looking for. There are so many PDFs in this repo that GitHub won't even render the entire file tree: Sorry, we had to truncate this directory to 1,000 files. 257 entries were omitted from the list.

Andrew Vanderburg of UT Austin and Christ Shallue of Google Brain join us to talk about their deep learning collaboration, which involved searching through a crazy amount of space imagery to find new planets.

Kball and Feross talk with Shelley Vohr and Jeremy Apthorp about what Electron is, why to use it, and what comes next for the platform.