> The reason this occurs is because there is no baseline of competence in software
Funny, I actually feel like it’s the opposite - most orgs I’ve worked in have an ultra high bar in specific areas to pass an interview, leaving otherwise proven capable devs who can perform all sorts of projects like this from being hired. It’s like we demand all engineers be doctors to insert an IV.
What gets things done is smaller teams with fewer dependencies. Large teams of highly competent engineers tend to produce massive project scales.
That sounds like something subjective and not a baseline. A baseline is a uniform standard minimal acceptance criteria. Imagine the employer is irrelevant because the technical qualifications are always the same uniform thing, which would be a baseline. It could be specific to technology platform, such as OS specific, Java, web, and so forth so long as it is focused on the technology and not created by a single specific employer.
Funny, I actually feel like it’s the opposite - most orgs I’ve worked in have an ultra high bar in specific areas to pass an interview, leaving otherwise proven capable devs who can perform all sorts of projects like this from being hired. It’s like we demand all engineers be doctors to insert an IV.
What gets things done is smaller teams with fewer dependencies. Large teams of highly competent engineers tend to produce massive project scales.