I think an 'Intro to Web Assembly (WASM)' is probably needed for a lot of data engineers, DS, analytics engineers and analysts, etc.
(I agree with most of your points, btw, but you know this already.)
I am also personally pretty staunchly of the opinion that data products is the single most obvious use with meaningful adoption for Web Assembly as a commercially viable paradigm. There's a lot of hype and hoopla around this for crypto trading, lots of Rust vs. Zip silliness that may not actually be important.
IMO, this is the single best opportunity for data engineers and data-focused software engineers to "lead from the front" that I've seen in the past few years, and if it's executed well it will help get around the classic "data teams are secondary to software teams" narrative that is too common.
I know I've said this in reply to you elsewhere, but as I'm digging into binary DataOps pipelines, your idea of WASM being an enabling force for Data Mesh makes a lot of sense to me, at least conceptually.
Right? I'm sure there's a chance I'm just hallucinating, but it seems like there's something here. For me, the crux to Data Mesh has been a truly decentralized p2p service that's not controlled by any particular company. WASM allows the creation and operation of data products locally, whilst also facilitating sharing. Time will tell I guess.
I think an 'Intro to Web Assembly (WASM)' is probably needed for a lot of data engineers, DS, analytics engineers and analysts, etc.
(I agree with most of your points, btw, but you know this already.)
I am also personally pretty staunchly of the opinion that data products is the single most obvious use with meaningful adoption for Web Assembly as a commercially viable paradigm. There's a lot of hype and hoopla around this for crypto trading, lots of Rust vs. Zip silliness that may not actually be important.
IMO, this is the single best opportunity for data engineers and data-focused software engineers to "lead from the front" that I've seen in the past few years, and if it's executed well it will help get around the classic "data teams are secondary to software teams" narrative that is too common.
Totally agree. It's a GIANT paradigm shift, both mentally and practice-wise. Smart call on leading from the front. Thanks Lauren.
Never once in your article did you expand on WASM.
You assume everyone is intimately familiar with your jargon :)
Sorry about that. Here you go.
https://gprivate.com/5yvxv
I know I've said this in reply to you elsewhere, but as I'm digging into binary DataOps pipelines, your idea of WASM being an enabling force for Data Mesh makes a lot of sense to me, at least conceptually.
Right? I'm sure there's a chance I'm just hallucinating, but it seems like there's something here. For me, the crux to Data Mesh has been a truly decentralized p2p service that's not controlled by any particular company. WASM allows the creation and operation of data products locally, whilst also facilitating sharing. Time will tell I guess.