4 ms·
A lot of how this is received may depend on the role you have in the group. You state you are new to the project; were you brought in as a junior novice? Or as
by tjr 13y ago
A lot of how this is received may depend on the role you have in the group. You state you are new to the project; were you brought in as a junior novice? Or as a seasoned professional? If the former, then you might consider presenting these ideas as suggestions rather than as a critique.
I think, though, that either way, this is a lot to digest all at once. Breaking this apart into separate communications might be easier to grasp.
Generally, it sounds like your team needs some sort of coding / development standards. Until a behavior has been established as "correct" or "incorrect", it's all a matter of opinion.
- ThrowawayCoward 13y agoI'm new to the project, but not new to the company. My previous role was a project lead, and I interacted with this project on a regular basis. I was brought in to this project to get stuff done because it's very behind and new work is piling up in the future. I agree that it's too long. If I send it anything at all, it will have to be shorter or in segments. Based on this and other peoples review, I probably won't send it. Still, it helped my identify the issues for myself. There must be ways of getting results without sending this, and I'll continue to consider that as I work with the team. I suppose I really would like these ideals to be a standard. Thank you for taking the time to read that novella and to post your thoughts!