Another thing that people honed in on was "software engineering" versus "programming", "software development", or other names for building software. I didn't intend it as a major focus, but I did want to cover all the parts of the job of getting software made -- not just typing code.
@evan too late to vote but my vote would be "very important", pondering that it could have been lower if you asked me in the past, mostly because with the AI tools now it's critical to have someone review the generated code. A less experienced engineer would accept the code as is without thinking of implications
On the flip side of arguments, I also less experience can be good sometimes, having a fearless team member can explore new ideas without the baggage of past experiences
@evan@cosocial.ca "young", "inexperienced", "small". That particular constellation of adjectives would lead to a pretty bad product I think!
The important keyword here is "small". A small but experienced team will run circles around any other combination. Age is less important (but tends to correlate with experience, one would assume.)
@otherdog @tante I guess I'll drop the link again just for reference if you haven't seen it, I didn't do so above because I feel like I post this every single day now to the point where the self-promotion feels shameful. but it remains painfully, almost nauseatingly relevant, so, here you go https://blog.glyph.im/2025/08/futzing-fraction.html
Another thing that people honed in on was "software engineering" versus "programming", "software development", or other names for building software. I didn't intend it as a major focus, but I did want to cover all the parts of the job of getting software made -- not just typing code.