News for hackers. Stuff that matters.
Re:The reality of being a Principal Engineer by giancarlostoro on Wednesday April 12, 2023 @10:16AM (#35540055)
You should consider taking the initiative to meet with them every week where you get future / current initiatives from them and status on anything they need to do moving those forward. Maintain a spreadsheet you can share with them (or whatever they prefer) and you just get new statuses. The goal is to be on the same page and have some familiarity before you even bother telling anyone else in IT correct? So make it happen.

I say this because I host such a call with our marketing team. I know what's coming down the pipeline before any developer even hears about it. My boss also uses it as an opportunity to interject and remind marketing that they already are trying to push too many initiatives our way, so they have to push some back.

Keep titles, descriptions, projected development start dates, and projected release dates, and a column for all status updates (date them, and put a name to the last status).

There are no comments on this comment yet.