I think this is generally well-put, with a couple of exceptions:
"Understand that more math is needed than just High School level."
If one is developing business applications, this is not true. I have seen very highly-paid technical leads who can barely solve two linear simultaneous equations, which is around 6th grade math in a lot of countries.
"On teams today, forty to sixty percent of my day is in meetings:"
This sounds very excessive. If more than 20% of a programmer's time is spent in meetings, your department needs training on how to conduct more efficient meetings. The majority of meetings drag on for far longer than they need to.
Nobody is static on a job for 40-years any more, so assuming the math isn’t needed would be a disservice to someone that might need it on the next job.
I should say on the meetings that I included pairing sessions.
I’d love to say you’re right about the meetings, but having worked with several enterprise-level organizations, this is the way things are. Very focused on process … often overriding common sense. But those base premise behind mentioning the meetings, that developers need to communicate stands.
It sounds like you do a different kind of programming than I do. I normally work with business applications on desktop and web, and I haven't had a need for anything beyond simple arithmetic. I did work at an engineering firm once, and most of the math was already done by the scientists and engineers; we just had to program it in. With the exception of specific fields that demand the math, a fresh graduate is more likely to be hired for their programming skills than their math skills, so I would encourage them to focus on that.
Regarding meetings, there might be a cultural difference between non-technical departments and developer teams that often needs to be addressed. The two communicate differently. I think there are firms that specifically provide training to increase the efficiency of meetings, so the meeting science is there. Just that not many companies are using it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this is generally well-put, with a couple of exceptions:
"Understand that more math is needed than just High School level."
If one is developing business applications, this is not true. I have seen very highly-paid technical leads who can barely solve two linear simultaneous equations, which is around 6th grade math in a lot of countries.
"On teams today, forty to sixty percent of my day is in meetings:"
This sounds very excessive. If more than 20% of a programmer's time is spent in meetings, your department needs training on how to conduct more efficient meetings. The majority of meetings drag on for far longer than they need to.
Nobody is static on a job for 40-years any more, so assuming the math isn’t needed would be a disservice to someone that might need it on the next job.
I should say on the meetings that I included pairing sessions.
I’d love to say you’re right about the meetings, but having worked with several enterprise-level organizations, this is the way things are. Very focused on process … often overriding common sense. But those base premise behind mentioning the meetings, that developers need to communicate stands.
It sounds like you do a different kind of programming than I do. I normally work with business applications on desktop and web, and I haven't had a need for anything beyond simple arithmetic. I did work at an engineering firm once, and most of the math was already done by the scientists and engineers; we just had to program it in. With the exception of specific fields that demand the math, a fresh graduate is more likely to be hired for their programming skills than their math skills, so I would encourage them to focus on that.
Regarding meetings, there might be a cultural difference between non-technical departments and developer teams that often needs to be addressed. The two communicate differently. I think there are firms that specifically provide training to increase the efficiency of meetings, so the meeting science is there. Just that not many companies are using it.