5
cjde225
150d

What no one told me was, as a senior resource how much context switching I need to do.
It's not even 12pm and I have been in 5 meetings, about 4 different projects
-- streaming platform but blockchain (Node, Golang) > planning + deployment issues meeting
-- goodreads but lighter > frontend approvals and ideas
-- custom node module development in C++ for internal db > debugging
-- SD card ETL tool > estimations and planning

Comments
  • 2
    Literally the reason why I refuse to become "senior".

    Every company has its own definition of senior anyway.
  • 0
    @retoor that is also the one I wanna focus on and am thinking of it like a *treat*
  • 1
    @retoor my company lets you have the senior title only if you practically stop doing dev work and start doing people management and meetings all day.
  • 2
    @Lensflare I have had some meetings where I have been told being a senior dev I need to step a bit away from dev work, and focus on the bigger picture as being more of a solution architect and having my hands in multiple things at once

    I still focus half my day on active dev stuff because I simply cannot let it go, it's where I derive work satisfaction from the most - the other half is problem solving and meetings
  • 1
    @cjde225 @retoor

    Sad to hear that this kind of practice seems to be common in the corporate dev world :/

    It just feels… wrong.
  • 1
    @Lensflare I happen to have a very similar approach for the position of a 'lead'.
  • 1
    @retoor Your small company sounds like my 1st job at a small, startup gamedev company.

    Pay was abysmal && often !on time, projects were uninspiring, but the team was tops.

    Met many great people there.

    Became best friends w/ one of them - we keep in touch to this day, even though we'd both left that company in different directions career && geographically-wise.
Add Comment