3 ms·
> It's like that "So you're telling me I have to get experience before I get experience?" Not at all. I'm not saying that one should be an architect on day one
by palata 1y ago
> It's like that "So you're telling me I have to get experience before I get experience?"
Not at all. I'm not saying that one should be an architect on day one. I'm saying that one should learn the basics on day one.
Learning how to install a package on a system and understanding that it means that a few files were copied in a few folders is basic. Anyone who cannot understand that does not deserve to be called a "software engineer". It has nothing to do with experience.
- Defletter 1y ago> I'm saying that one should learn the basics on day one. Except that C/C++ have entirely incongruous sets of basics compared to modern languages, which people coming to C/C++ for the first time are likely to have a passing familiarity with (unless it's their first language, of course). Yes, cmake configs can be pretty concise when only dealing with system packages, but this assumes that developers will want to do that, or whether they'll want to replicate the project-localness ideal, which complicates cmake configs. We're approaching this from entirely different places and is reminding me of the diametrically-opposed comments on this post (https://news.ycombinator.com/item?id=45328247 https://news.ycombinator.com/item?id=45328247) about READMEs.