Triadic Programming 4.23 http://spkr8.com/t/1312

Description:

Since the Cold War, the secretive Dyadic Society has been stealthily sapping the strength of the software development community. Haven't heard of them? That just proves that they exist! To conceal the truth from programmers, the Dyads promote their ideology through proxies, using content-free blanket terms such as “best practices” and “design patterns.”

You can fight the Dyads by avoiding so-called “best practices” such as:

  • polymorphism via classes and methods
  • error handling via throwing and catching exceptions
  • thread-safe code via objects and locks

Notice the dyads: throw and catch, class and method, object and lock. In this keynote, you will see what the Dyads fear most: a set of Triadic techniques that break the Dyadic chokehold on developers everywhere:

  • polymorphism via structures, functions, and multiple dispatch
  • error handling via signals, handlers, and restarts
  • thread-safety via immutable data, references, and transactions

Remember: threedom is freedom.

Comments on this Talk

Stream joelind, 15 Aug 19:14

This user has yet to validate her/his profile with LinkedIn. It is therefore simple to assume that she/he is but a charlatan or common hoaxster.

Great content, well delivered. Very valuable. Would have liked some pointers to some more real-world examples of triadic techniques.

Missing garethconner, 15 Aug 23:28

This user has yet to validate her/his profile with LinkedIn. It is therefore simple to assume that she/he is but a charlatan or common hoaxster.

I really enjoyed this talk; it was the highlight of the day for me. It's great to hear the thoughts of someone with a broad view.

Missing garethconner, 15 Aug 23:28

This user has yet to validate her/his profile with LinkedIn. It is therefore simple to assume that she/he is but a charlatan or common hoaxster.

I really enjoyed this talk; it was the highlight of the day for me. It's great to hear the thoughts of someone with a broad view.

Have an account? Sign in.

Leave a Comment

Remember to keep it constructive! Identify strengths and areas for improvement, and make suggestions!

10 Ratings: 4.23

Delivery: 4.49

Content: 3.98

Your Rating: 2.5

I'll Rate It! I was there.

Last Five Ratings

Welcome to the SpeakerRate Beta! Have feedback? Let us know over at Get Satisfaction (but be nice).