> Thanks for generalizing Spark engineers to an insulting level, though. I have no clue how you got that from what I wrote. I even said a Spark project needs a

> Thanks for generalizing Spark engineers to an insulting level, though. I have no clue how you got that from what I wrote. I even said a Spark project needs a Spark dev! It really sounds to me like you're the one generalizing from "the one C++ dev we hired couldn't do data engineering right at all" to "senior programmers are dangerous to us unless they are Spark developers" (which imo, is more indicative of serious deficiencies in your architecture / design process), to "all senior programmers crossing subdomains are dangerous."