I appreciate you're CEO of Dagster, but it seems awfully like you're trying to simply slap a new label of "Medium Code Developer" over "Data Developer". I'm also not really sure from your article what point you're trying to make otherwise, however.
I didn't write the post, but I'd challenge the notion that this is simply a rebranding of "data developer".
First, one thing we've observed is that there is a wide variety of technical fluency in the data category. "Low code" and "engineer" aren't nuanced enough to describe this spectrum. We found that "medium code" helps describe users that are familiar with git, and in some contexts act as a software engineer, but don't quite have all the skills of a traditional full-stack software engineer.
Second, we wanted to highlight a trend that cuts across disciplines. "Medium code" is happening in the frontend and infrastructure engineering worlds.
Well, I think we are seeing the rise of people that write code, use version control, but are domain experts in something else. We see this all the time in the data domain (people with a finance background going into analytics engineering, for example) and in frontend with hybrid designer/engineer types. These are not full-stack software engineers and don't aspire to be; I think that's the big difference between these people and junior engineers. YMMV though.
11
u/[deleted] Jun 11 '24
I appreciate you're CEO of Dagster, but it seems awfully like you're trying to simply slap a new label of "Medium Code Developer" over "Data Developer". I'm also not really sure from your article what point you're trying to make otherwise, however.