Engineers Shouldn’t Write ETL
multithreaded.stitchfix.com
Engineers Shouldn’t Write ETL
1–10 of 178 posts
Re: Engineers Shouldn’t Write ETL
#2This author seriously needs to expand all of his TLIs (three-letter initialisms) the first time he uses them, as any writer worth his or her salt would do. There are those who may be interested in what he has to say, but can't follow because of assuming abbreviations.
Re: Engineers Shouldn’t Write ETL
#3I'm getting a DNS error - could be me though.
Re: Engineers Shouldn’t Write ETL
#4This author seriously needs to expand all of his TLIs (three-letter initialisms) the first time he uses them, as any writer worth his or her salt would do. There are those who may be interested in what he has to say, but can't follow because of assuming abbreviations.
Agreed. I think ETL = https://en.wikipedia.org/wiki/Extract,_transform,_load
Re: Engineers Shouldn’t Write ETL
#5... a highly specialized team of dedicated engineers...If they are not bored, chances are they are pretty mediocre. Mediocre engineers really excel at building enormously over complicated, awful-to-work-with messes they call “solutions”.
OMG, the author just described the last place I was at. Processed a few Tb of data and suddenly there's this R. Goldbergesque system of MongoDb getting transformed into PostGres...oh, wait, I need Cassandra on my resume, so Mongo sux0r now...displayed with some of the worst bowl of spaghetti Android code I've witnessed. The technical debt hole was dug so deep you could hide an Abrams tank in there. To this day I could not tell you the confused thinking that led them to believe this was necessary rather than just slapping it all into PostGres and calling it a day.
All because they were processing data sets sooooo huge, that they would fit on my laptop.
I quit reading about the time the article turned into a pitch for Stitch Fix, but leading up to that point it made a good case for what happens when companies think they have "big data" when they really don't. In summary, either a company hires skills they don't really need and the hires end up bored, or you hire mediocre people that make the convoluted mess I worked with.
Re: Engineers Shouldn’t Write ETL
#6This author seriously needs to expand all of his TLIs (three-letter initialisms) the first time he uses them, as any writer worth his or her salt would do. There are those who may be interested in what he has to say, but can't follow because of assuming abbreviations.
It's a pretty common acronym in the field, actually.
Re: Engineers Shouldn’t Write ETL
#7This author seriously needs to expand all of his TLIs (three-letter initialisms) the first time he uses them, as any writer worth his or her salt would do. There are those who may be interested in what he has to say, but can't follow because of assuming abbreviations.
Though I agree with you on expanding TLIs, if you have to have "ETL" defined for you, you probably won't get the "joke". And though this will come out more cynical than I intend, if you don't know the acronyms, then you probably won't be buying what Stitch Fix is selling. Filtering their funnel, maybe?
Re: Engineers Shouldn’t Write ETL
#8This article is so one sided it is painful. it is almost like Sheldon Cooper wrote this article. As an engineer I am offended and hurt that we are referred to as “Tony Stark’s tailor”.
Re: Engineers Shouldn’t Write ETL
#9This author seriously needs to expand all of his TLIs (three-letter initialisms) the first time he uses them, as any writer worth his or her salt would do. There are those who may be interested in what he has to say, but can't follow because of assuming abbreviations.
Might end up sounding like this: https://www.youtube.com/watch?v=BpMwZDfSLBk
Re: Engineers Shouldn’t Write ETL
#10>You Probably Don’t Have Big Data
"Big Data" is like sex in high school. Everyone talks about it but few people really have lots of it and some just don't have any.