Tech Talks – A short list of recommended talks

The other day I was browsing HN and I find one of those really good questions. This one was about the favourite tech talks of the community members. Some of them you probably had already seen, but others are some hidden gems (or at least they’re for me). This was the spark that creates this post, so, here are some of those cool Tech Talks.


Let’s start with a classic.


Wat by Gary Bernhardt

This awesome talk takes the quirks of the everyday programming job with a good dose of sarcasm and humor.


Fork Yeah!! The Rise and Development of Illumos by Bryan M. Cantrill, Joyent

In August 2010, illumos, a new OpenSolaris derivative, was born. While not at the time intended to be a fork, Oracle sealed the fate of illumos when it elected to close OpenSolaris: by choosing to cease its contributions, Oracle promoted illumos from a downstream repository to the open source repository of record for such revolutionary technologies as ZFS, DTrace, and Zones.


The Myth of the Genius Programmer by Brian Fitzpatrick and Ben Collins-Sussman

A pervasive elitism hovers in the background of collaborative software development: everyone secretly wants to be seen as a genius. In this talk, we discuss how to avoid this trap and gracefully exchange personal ego for personal growth and super-charged collaboration. We’ll also examine how software tools affect social behaviors, and how to successfully manage the growth of new ideas.



Discovering Python by David Beazley

So, what happens when you lock a Python programmer in a secret vault containing 1.5 TBytes of C++ source code and no internet connection? Find out as I describe how I used Python as a secret weapon of “discovery” in an epic legal battle.


What We Actually Know About Software Development, and Why We Believe It’s True by Greg Wilson

Greg Wilson makes a deep analysis about what we actually know about software development.


How To Design A Good API and Why it Matters by Joshua Bloch

Every day around the world, software developers spend much of their time working with a variety of Application Programming Interfaces (APIs). Some are integral to the core platform, some provide access to widely distributed frameworks, and some are written in-house for use by a few developers. Nearly all programmers occasionally function as API designers, whether they know it or not. A well-designed API can be a great asset to the organization that wrote it and to all who use it.


Beyond PEP 8 — Best practices for beautiful intelligible code by Raymond Hettinger

Distillation of knowledge gained from a decade of Python consulting, Python training, code reviews, and serving as a core developer. Learn to avoid some of the hazards of the PEP 8 style guide and learn what really matters for creating beautiful intelligible code.


I hope you enjoyed one or all of this awesome tech talks. If you are hungry for more, you can take a look at the original question at HN. See you soon! 🙂

Compartí el post, no seas careta...Tweet about this on Twitter
Share on Facebook
0Share on Tumblr
0Share on LinkedIn

Recent Posts

Recent Comments



    Santi Written by:

    Be First to Comment

    Leave a Reply