John Resig

Introducing the GraphQL Guide

John Resig and team at Khan Academy implemented a generic GraphQL platform and their development practices changed overnight. The benefits they saw were so substantial that he and Loren Sands-Ramshaw decided to write a book about it. ...we’re using GraphQL in more and more places: we are transitioning older pages over to use GraphQL and have a mandate in place that all new pages need to use GraphQL. The benefits that we’ve reaped have been so substantial, even though it’s still early days. We’re writing new products faster, we’re able to rapidly iterate on designs, and we’re keeping our server implementation slim. Wow, "REST APIs now feel quite antiquated..." I look at how well it’s worked for us and read stories about how GraphQL has changed other organizations, and I can only think that GraphQL is going to dramatically change how we all build APIs going forward. REST APIs now feel quite antiquated by comparison. Beta chapters of The GraphQL Guide are available now.


Chris James

Learn Go with tests: HTTP server

Chris James: Write a simple web server in Go with test driven development. Learn how to use mocking to let you break the problem down into small iterative chunks. All using standard library, source code is available to read. The linked page is a sub-section of the Learn Go with tests GitBook. Do you enjoy TDD and want to learn Go? Or do you enjoy Go and want to learn TDD? Either way, this looks like a great (WIP) resource.


Linode Icon Linode – Sponsored

Linode is hiring a React developer to work on open source Linode Manager

Linode is looking to hire a React developer to work on thier open source single page app called Linode Manager which is used by customers like Dark Sky, The Onion, Changelog, and developers from all around the world. These systems are used to manage hundreds of thousands of Linodes running on thier global datacenter network. Apply here and tell them we sent you!

logged by @logbot permalink

React Icon

Docz – it has never been so easy to document your things!

Docz' high-level principles give you an idea of what they're all about: Zero config and easy. No unnecessary build steps with confusing setups. Blazing fast. Always use the fastest things to build our tools. Easy to customize. Create something that will be easy to use and customize. MDX Based. Have the best standard to write documents. Pluggable. Plugins are the best choice when you need to be custom and flexible. Watch the demo video on the homepage to see just how nice this tool is to use.


Ken Wheeler

A bitter guide to open source

Ken Wheeler (Director of open source at Formidable) shared some pretty helpful words to get you excited about open source and also how to launch your first project. Nothing makes your repo look more legit than badges. Too many badges looks memey as fuck, but if you include useful ones, its a stamp of legitimacy. It shows you care. Things like npm version, test status, coverage numbers. It’s nice flair. Also, Markdown supports raw HTML, so you can make your repo header look nice. Center things, add a quote, jazz it up a bit. Ken even shared his thoughts on the best time to launch. My recommendation is very specific. Release at 12pm EST on a Monday. It’s the end of Europes day, New York’s lunch break and San Franciscos hour in the morning before anything gets done.


Spencer Brown

To yarn and back (to npm) again

Yarn and npm was discussed in-depth on JS Party #29. Spencer writes on the Mixmax blog: We tested that this flow with npm 6 would work for our needs and we suggest you do too. If you need the absolute fastest package manager, then you may still find Yarn to be best. But if you're looking to simplify your setup, we've found that npm 6 recaptures a critical balance between speed and reliability. Spencer and team also shared deyarn a command-line tool for converting your projects from Yarn to npm.


Raspberry Pi Icon

Learn OS development using the Linux kernel and a Raspberry Pi

This repository contains a step-by-step guide that teaches how to create a simple operating system (OS) kernel from scratch. I call this OS Raspberry Pi OS or just RPi OS. The RPi OS source code is largely based on Linux kernel, but the OS has very limited functionality and supports only Raspberry PI 3. 6 lessons available with 5 more on the roadmap.


Mike Cohn

10 practices to be a better Scrum Master

One of my favorite jobs in software was when I was a Product Manager for a non-profit startup. In that role I was able to impact and touch pretty much any part of the business I wanted to, it was almost like being an entrepreneur, but doing so from within an already formed company. I also led our agile software development as Scrum Master — it was awesome. I wish I had this list of advice back then. Mike Cohn writes on the Mountain Goat Software blog: Never commit the team to anything without consulting them first — As Scrum Master, you do not have the authority to accept change requests (no matter how small) on behalf of the team. Even if you are absolutely positive that the team can fulfill a request. Always say, “I need to run this by the team before we can say yes.” And certainly don’t commit the team to deadlines, deliverables, or anything else without first talking to team members. You may not need to talk to the whole team--plenty of teams will allow some or all members to say, “Yeah, we can do that” without a whole-team meeting. But it’s still their decision, not yours. This is number 1 on the list, because you should never get this one wrong.


Casper Beyer Medium

Is the internet at the mercy of a handful of developers?

In this post from Casper Beyer titled The Node.js Ecosystem Is Chaotic and Insecure, he cites examples like left-pad, is-odd, is-number — and goes on to say the way to be responsible with dependencies is... ...don’t trust package managers, every dependency is written by some random developer somewhere in the world and is a potential attack vector. ... Is this being too paranoid? Perhaps, or maybe it’s the healthy amount considering the massive reach these trivial packages can have. While this focuses on Node.js, the lessons learned apply anywhere you have dependencies in your code.


Donald Fischer Tidelift

The data behind Microsoft's surprising open source track record

Our friends at Tidelift have joined data from GitHub and their own, "the largest open source software dataset in the world," — which covers over 2.8 million open source projects. They were able to combine the two datasets to gather the entire commit history of each project on GitHub to more closely examine the following questions: What exactly has been Microsoft’s role in the open source community? In which projects and ecosystems have they contributed most? Have those contributions been focused on the large Microsoft open source initiatives, or has the company also participated in projects beyond their immediate purview? They were also careful to clean the dataset of forks and duplicate packages which would misinform this analysis. So what’s the verdict? Microsoft may have a mixed history with open source, but today the company is demonstrating some impressive traction when it comes to open source community contributions. If we are to judge the company on its recent actions, the data shows what Satya Nadella said in his announcement about Microsoft being “all in on open source” is more than just words.


Diego ZoracKy

MagiCLI can generate a command line interface for any module

MagiCLI was built to expand the use of npm modules. When all modules can be executed via CLI, npm becomes a source for anyone who wants to find a solution ti be run from a terminal and also for those who would like to call an existing solution written in Node.js from a program written in another language. For even more context, check out the intro post on Hacker Noon.


GitLab Icon GitLab

Apple just announced Xcode 10 is now integrated with GitLab

No other details were shared in this tweet, but this image from the stage of WWDC says all it needs to. In a post-Microsoft + GitHub world — it has been a crazy 24 hours for GitLab. More than 2,000 people tweeted about #movingtogitlab. We imported over 100,000 repositories, and we've seen a 7x increase in orders. We went live on Bloomberg TV. And on top of that, Apple announced an Xcode integration with GitLab. Here's an interesting exchange between Emily Chang and Sid Sijbrandij on Bloomberg Technology: Emily: I spoke with Satya Nadella earlier today, and he said "he promises to put developers first." Do you not believe him, or do you think it's not possible for a company with so many objectives to really put developers first? Sid: I believe him. Microsoft has shown that it is the new Microsoft, and they've done great. The new CEO, Nat Friedman, shows he really understands developers. So I believe him when he says they are going to be good maintainers of GitHub. Emily: So, then what's so bad about GitHub? Sid: There's nothing bad about GitHub. Emily: What’s so much better about GitLab? Sid: It's a fundamentally different product. It's open core, so a lot of it is open source. You can host it yourself. But second and I think most importantly, it's not just code hosting. With GitHub you host your code. GitLab is the entire DevOps lifecycle. So all the way from planning something to rolling it out, container registries, monitoring — all in a single product. That allows you to get the whole organization on the same page. And that's why people are flocking to it. They go on to talk about being a sustainable business, financials, etc.

0:00 / 0:00