throwawaybbqed
Joined 9 years ago
Joined 9 years ago
You posted this for a reason .. would be good to get your thoughts.
edit: adding one more point. I went to a fairly high-ranked university(top-20). We would get graded based on how clear our code was, comments (both for functions and inline comments). This code would get a zero on those metrics.
Flexibility in producing the "right" work product is really key. In many large corporate environments, figuring out what is the right work product is possibly more work than the work itself. I have a feeling we may even see different models between different types of companies (nimble startups vs small companies vs large corps). In my personal org, what you are describing can be viewed as an engineer "phoning it in" .. as the engineer is depending on their manager or team lead to assign them the right work. An IC who phones it in may think they are a top producer but will get surprised when it comes to their career progression.
Also, if the R&D project is a team project involving multiple people, what is a reasonable update/sprint cadence?