CSV, JSON and XML (Oh My!)
summary
PowerShell demos show concrete tradeoffs: CSV serializes everything as strings so numbers and dates lose type unless code explicitly casts or constructs objects; ConvertFrom/To-Json needs depth and often returns system.object arrays so you must recreate JSON items to get dotable objects; XML preserves hierarchy and supports targeted updates so XML can be updated in-place without rewriting whole files; a small reminder project called tickle reminder tool evolves from CSV to XML to SQL as needs for typing, nesting and atomic updates emerge.
AI-written summary · about
chapters (16)
- 0:00Overview
- 3:40Using different data structures
- 4:35Type
- 12:50JSON
- 15:40CSV File
- 18:20Create New Entry
- 20:15XML
- 25:50Recap
- 26:50Optimize Text Files
- 31:50File Size Matters
- 33:30Bad Practices
- 35:30Make Parameters
- 36:20CSV Data
- 37:40Configuration Data
- 38:50Import Data
- 42:10Other Questions
related talks
48mA Tree Full of Object Data
38mCreating HTML Reports with Style
47mPower BI Meets Programmability – TOM, XMLA, and C#
29mHigh Performance Data Loss
25mRecursion Schemes Without the Barbed Wire (Part 5)
01h 02mAnalyzing StackExchange with Azure Data Lake
29mSchemas: The Key To Data Happiness
44mThe Future of Data Pipelines with Atomic Wasm Transformations & the Evolving Role of Data Engineers