Bjorn Freeman-Benson suggests “listening” to the code, refactoring it based on various factors such as the defect rate or underperforming services, providing strategies and tools.
Bryan Nehl makes an introduction to the data science: data formats, ETL tools, NoSQL databases, languages, libraries, techniques and approaches for exploring data and extracting value from it.
Simon Hildrew discusses the tools and processes used by The Guardian to create a continuous delivery pipeline.
Jevgeni Kabanov discusses the results of a research on a delivering software model, the tools involved and the model itself, concluding on what one can expect from using certain tools.
Matthew McCullough examines the last four years of communication culture at GitHub, starting their internal mobile and web apps, use of pull requests, and emoji.
Ruslan Meshenberg discusses Netflix's challenges, operational tools and best practices needed to provide high availability through multiple regions.
Markus Völter suggests and illustrates creating development environments based on language workbenches that provide a generic infrastructure and can be easily extended and composed.
Daniil Elovkov shows how to define a projectional editor that combines graphical, tabular, textual notations, lets one either mix or seamlessly switch between those, and is deployable to the web.
Richard Minerich explains how ideas and tools from functional programming can save time, prevent subtle mistakes in data science, and how he incorporates them into his everyday workflow.
Dmytro Mindra discusses the tools and practices used for a game engine: Unit Testing and Test automation, Unity Runtime Test Framework, Continuous Integration, Game Test Framework, Performance Tests.
Ian Robinson introduces tools and techniques for building a system around a graph engine, experiment with graph data, and using it in an application.