Code[ish]

A podcast brought to you by the developer advocate team at Heroku, exploring code, technology, tools, tips, and the life of the developer.

Also listen via

Pandora Android dev.to TuneIn RSS

Subscribe to Code[ish]

Share This

Code[ish] • January 14th, 2020

52. Building and Scaling a Heroku Add-on

Hosted by Corey Martin, Adam McCrea

Heroku applications big and small run on dynos, virtualized Linux containers fine-tuned to execute your code. As the load on a server increases, you must add dynos to keep up with demand—but how do you know how many more to add? And how can you be sure that you are saving costs by reducing the amount of dynos after spikes in traffic settle? To solve that problem, Adam McCrea developed Rails Autoscale, a Heroku add-on that auto-scales Rails apps hosted on Heroku. He'll talk with Corey Martin about how he came up with the idea, how he built it, and how he got word out amongst his network to make it a must-have add-on.

Hosted By:

Corey Martin

Customer Solutions Architect, Heroku

with Guest:

Adam McCrea

Full Stack Developer, Rails Autoscale
@adamlogic

Transcript Available

Share This

Code[ish] • December 31st, 2019

50. High Energy, Low Power: A Bluetooth Christmas Story

Hosted by Charlie Gleason, Chris Castle

Chris Castle has a two year nephew who, like most two year olds, likes pushing buttons—especially ones that turn lights on. When a Christmas tree appeared a few weeks ago, and lights were put up, he was very excited. At the same time, Chris was experimenting with Puck.js, a programmable low-power bluetooth button, and had a brainwave—he could combine his nephew's love of buttons and of lights. A true Christmas miracle.

Transcript Available

Share This

Code[ish] • January 7th, 2020

51. Best Practices in Error Handling

Hosted by Julián Duque, Ruben Bridgewater

Errors are a fundamental part of the programming experience. Learning how to receive and react to them, as well as responding to the user who may have encountered one, is essential to building a great application experience. Ruben Bridgewater, a core member of the Node.js team, talks us through various error handling strategies, both those that are specific to JavaScript as well as those applicable to anyone building a production-grade service.

Transcript Available

Share This

Code[ish] • December 24th, 2019

49. Building Effective Distributed Teams

Hosted by Anthony Mazzarella, Juan Pablo Buriticá

Running a start-up is hard. Running a start-up with teammates spread across the world is even harder. Juan Pablo Buriticá is the VP of engineering at Splice. He believes there's a fallacy that remote teams ought to be treated differently than non-remote ones. He argues that, given enough time, every team becomes distributed, whether that means they're in a different room or office or floor or country. He expounds on this philosophy, as well as how to set up your team for success early, whether they're comprised of four or four hundred people.

Transcript Available

Share This

Code[ish] • December 17th, 2019

48. From NodeConf EU 2019

Hosted by Julián Duque, Alex Korzhikov, Tierney Cyren, Chris Dickinson

NodeConf EU is one of the main conferences for the Node.js community. Community members from all over the world share their projects, leader workshops, and discuss the direction of the world's most popular programming language. congregate to discuss best practices, upcoming language changes, cool implementations, and more. Julián Duque chats with several attendees about what they're working on.

Transcript Available

Share This

Code[ish] • December 10th, 2019

47. Working with an Event-Driven Architecture

Hosted by Robert Blumen, Alexey Syomichev

One factor to consider when designing an application is how to represent information about events that occur. One traditional way is to use a database: as new events occur, a row in a table is updated. Another approach is to use an event log: every event that occurs is retained in a serialized format, so that app's state at any point in time is preserved.

On this episode Alexey Syomichev talks with host Robert Blumen about enterprise architecture organized around an immutable event log. The discussion covers the notion of events - what are they, what do they contain, event data, event schema, event formats; producers and consumers of events; the event log; time stamps versus event log time; immutability; durability of event logs; organizing enterprise architecture around the event log; the log-centric approach to integration compared to point-to-point; in place updates versus append only; extracting event logs from an RDBMS; reconstructing RDBMS change logs as business events; the event log as the system of record; making the event log highly available; scaling the event log.

Transcript Available

Share This

Code[ish] • December 3rd, 2019

46. Go at Heroku

Hosted by Johnny Boursiquot, Ed Muller, Rishabh Wason

Many organizations and teams have adopted Go for its focus on concurrency and efficiency, and Heroku is no different. Although it's no longer a "new" language, diving into Go can be intimidating, whether you're a seasoned programmer or a new hire. Johnny Boursiquot, Ed Muller, and Rishabh Wason discuss the joys and challenges of learning Go, applying it to projects at Heroku, and teaching colleagues how to write idiomatic code.

Transcript Available

Share This

Code[ish] • November 26th, 2019

45. Illuminating Poetry with Technology

Hosted by Casey Faist, Justin Kestler, Devyn Gasperini

Literature gets a bad rap for being too complicated, but it doesn't have to be. Over the years, various websites have sprung up to connect the confused with the clever. LitCharts aims to help by providing source text in one column, and a list of annotations, references, and explanations in another. We sat down with two members of the LitChart to discuss the technical challenges involved in building up a repertoire of literary knowledge.

Transcript Available

Share This

Code[ish] • November 19th, 2019

44. GraphQL’s Benefits and Costs

Hosted by Owen Ou, Tanmai Gopal

GraphQL is a querying language with the aim of increasing the productivity of frontend and backend developers. It can make working with React easier, be used as an API for third-party clients, and allow for feature-rich applications to request precisely the data they need. Like any part of your stack, GraphQL isn't a panacea. The language is still being developed, and has some limitations. Tanmai Gopal, the CEO of Hasura, guides us through the pros and cons of using GraphQL in your application.

Transcript Available

Share This

Code[ish] • November 12th, 2019

43. The GitHub Student Developer Pack

Hosted by Joe Kutner, Anupam Dagar

The GitHub Student Developer Pack is a collection of free offers and discounts from dozens of tech companies including Heroku, SendGrid, Sentry, and TravisCI. Anupam Dagar is a final-year undergraduate student at Indian Institute of Information Technology, and he's sharing with us how the Student Pack has helped him and his peers grow into more confident developers.

Transcript Available

Share This