What We Can Learn From COBOL
summary
COBOL started as a practical 1959 spec for business ETL and claims lasting relevance rather than theoretical elegance the language enforces four divisions for identification environment data and procedures which makes data layout explicit but makes abstraction awkward builtins for common tasks arrive late with functions added in 1989 and user defined ones in 2002 modern comparisons show the same pattern in ETL tools like Pig Hadoop and Storm and simple copytransform pipelines that actually run at scale
AI-written summary · about
chapters (6)
related talks
52mData Over Code: A Short Hyperbole
58mUnderstanding Big Data for Software Engineers
15mNext Gen ETL Generators
39mLeaving ETLs Behind: Moving from a ‘Code Less’ Solution to a ‘Code Full’ Approach
41mModern Data Architectures – What They Are and How to Implement?
14mMIT Impact
30mRetooling for a Smaller Data Era
01h 01mCurrent Methods for Building Data Pipelines