Discussion about this post

User's avatar
vladimir's avatar

I'd add 2 things:

1. Desired modern enterprise Data Engineering is quite above junior-level of engineers.

2. Emperor being naked is upstream and downstream of AI adoption.

The fact that your team had to write "SQL queries and building data pipelines" means those things were not in place and/or no team to suppert your cause. I'd argue if this really is a "mundane infrastructure work that any junior developer could handle".

"Level of DE difficulty" seems commonly understated and the complexity is only rising. It is likely hard to justify SWE/ML/AI salary on a DE, but that also means everybody has to live with the results of hiring people often not capable or motivated enough for the challenges. A meme "We wanna do AI, but can not do BI" is live and well in big orgs.

The rest of the article felt like a well-written perspective of struggles of "adopting AI where accountability matters". There is a huge difference between an industry where a "count of likes" does not work correctly or "this person is not really my cup of tea. This algo sucks!" vs. an industry where a company has to keep its licence in a highly regulated environment like banking.

If a question for sellers is "Who will lose their job when the algorithm makes a bad decision?" you can follow with a one for the buyers "Do you think IF or WHEN will AI mess up? Are you ok with the consequences?" Atm there is 0 confidence about "IF" and if "WHEN" can be expected in days or maybe months and it will likely repeat - what exactly is the deal for accountable managers?

Maybe some will "Just use AI" #YOLO

Thank you for sharing an experience when not all is shiny and well. Posts like this will help us all get to a better outcome in future endeavors.

Expand full comment

No posts

Ready for more?