3 ms·

I'm your target audience, seeing as this year was my first year in the workforce and I'm young. I don't see the point in trying to prove yourself in most situa

I'm your target audience, seeing as this year was my first year in the workforce and I'm young. I don't see the point in trying to prove yourself in most situations, since most organizations have little opportunity. I just quit my first tech job. The first team I was on had very little agency and was basically told what to do, the second team I was on had an "architect" who dictated how everything was going to be. Without going into boring details, I was told by management and other team members I was doing well and it showed compared to most of the other Juniors I worked with. I don't want a glamorous role, or one that gives me social proof. I just want to have some agency and the opportunity to take on responsibility and advance. It seems like that's hard to come by, though.

sergeykish 6y ago
I found it easier to extend in Product Ownership direction. Resolving use cases with customers (like writing test cases against reference Excel computation, legacy SQL dump), filling stories, writing documentation. It results in natural leadership. I don't know your story but I've been tech lead in a team with to many juniors, bad idea. I've struggled to give them agency, they were arguing about placing spaces and braces, there were cases of designing not so great API, mutating frameworks private variables and defending as "own vision". Promising juniors left, I've left. Finding good team is hard. It is often ruined by management.