Video publishing sometimes feels like a Rube Goldberg machine. To get a single video to play back successfully, a dozen different systems need to play nicely together: websites, players, browsers, ISPs, CDNs, network operators, cloud providers, encoders, standards bodies, content producers, and more. And underlying a single video delivery are dozens of individual computers, spinning disks, and network links. (Yes, even The Cloud uses computers.)
From Runscope's Heitor Tashiro Sergent: I've been wanting to create a project on Glitch for quite some time. Glitch is a startup/product/friendly community where you can create and remix Node.js projects, use an online code editor to personalize them, and you don't have to worry about hosting or deployment. And it's free! It's a really great way to start a project and prototype an idea, without having to worry about those million little things that can get in the way of your dream app.
When building for developers, many of us start by scratching our own itches. That's great for pulling together an MVP — and doing some interesting engineering along the way — but it's all too easy to get wrapped up in the functionality of the thing and lose sight of what it's like to be on the other side of your API.
To prevent your shiny new tool from being reduced to just a set of inputs and outputs, Christine explores best practices worth baking into your team's culture — and how to carry those principles through growth and change.
The latest news, product updates, jobs, and discussions in the developer tools industry. Brought to you by Heavybit. Update your preferences if you no longer want to receive the DevToolsDigest *|UPDATE_PROFILE|*