Enyo Kumahor shares software development stories from the African continent.
Kevlin Henney examines seven coding habits that are not as effective as many programmers — whether working with Java, .NET, native or scripting languages — might believe, and suggests alternatives.
Russ Olsen tells the moon landing story and how it has affected the software development.
Em Campbell-Pretty overviews how to create an Impact Map, sharing real world examples of how impact mapping has helped support the delivery of software products.
Melissa Pierce discusses the history and present of CS culture, gender relations, and tensions between hardware and software engineering.
Sri Viswanath shares the ideas and program driving Groupon’s engineering culture.
Alvin Sng discusses the important engineering aspects of the Resolution Center’s development.
Leslie Lamport makes the case for separating the design details of what a program should do and how it should work from the business of writing code, and discusses how the design process should work.
Sid Anand discusses the architectural and development practices adopted by LinkedIn as a continuous growing company.
Josh Knowles shares thoughts on the strong engineering culture which has made the Pivotal Labs team successful, taking a look at how things have evolved over the past 20 years.
Douglas Crockford discusses how to use programming languages more effectively; reviews the good parts in EcmaScript 6 and JSON.
Bruce Eckel reviews some of the ideas and practices of the development community, outlining patterns of the problems related to communication, organization, process, etc. it has been trying to resolve