By martinig
via softdevtube.com
Published: Dec 13 2012 / 10:43
More and more applications are being written in dynamically typed languages like JavaScript and Ruby. Theoretically, this is progress. But, what happens when they go bad? What are the recovery options. This talk explores methods for making sense of, and recovering large legacy code bases in dynamically type languages. It concentrates on the differences between them and their statically-typed counterparts.
Tweet
SaveShareSend
Tags: how-to, javascript, methodology, ruby
-
Android to Windows Phone 8: Working with Key-Value Pairs
-
AWS Cost Saving Tip 10: Make right choice between PIOPS vs Std EBS volumes for saving costs
-
Live Collections using Backbone.js, Faye and Node
-
Technical Debt: In an Agile World
-
Traceroute’s Working and Problems With It
-
Building a Falling Block Game Using CSS Grid Layout & Blend 5
Add your comment
