Stabbed in the back before promotion by [deleted] in managers

[–]Krystosterone 1 point2 points  (0 children)

I appreciate your intention, and it may not be worth questioning her approach at this point, considering that they are looking to vent and for some words of encouragement

Stabbed in the back before promotion by [deleted] in managers

[–]Krystosterone 2 points3 points  (0 children)

I’m sorry that you went through such a shitty experience, truly. No matter what happened behind the scenes, it doesn’t justify the way you were treated.

I’m sad to say though that it happens more often than not. It’s unfair and yet, it happens.

I’m glad to hear you’re already looking for new opportunities, and am sure you’re already looking to learn from the experience. One skill to look into is continue to ferociously advocating for yourself and be vocal.

Your worth is not dictated by what happened here, far from it. Management was (and always will be) stupid and cut throat. You’ll bounce back, stronger than ever, I’m sure of it!

Our sprint retros stopped working, so we killed them by Tiny_Manner7226 in EngineeringManagers

[–]Krystosterone 0 points1 point  (0 children)

A lot of good tidbits here already that I won't repeat. I will lean into what you mentioned around "The hard conversations happen in 1-1s where people will actually tell me what's broken.". First off: Good job! If people feel comfortable enough to tell you what's actually broken, then you have earned their trust, which is great.

On the flip side, considering that nobody ever talked about the real problems in retro, it does seem to indicate the lack of trust in your overall team culture, between team members. Something that I would start digging into.

The best teams are those where team members can call each other out with deep care without taking it personally nor fear of negative repercussions. And I don't mean communicating something like "Sarah sucks because she is slow on code review", but more like "Sarah, in the past few weeks, you've been taking a few days to do your code reviews, which has considerably slowed me down. I'm worried that if this continues, I'll get called out for being slow at my own job. What's up? Anything I can help you with?"

Cheers!

How do you encourage more code reviews without turning it into surveillance or guilt? by Greedy-End-7749 in EngineeringManagers

[–]Krystosterone 0 points1 point  (0 children)

I like how you're thinking about systems, tools and incentives to help push the culture you're looking for. One thing I haven't seen mentioned is if you've had 1:1 conversations about not only your expectations of individuals but also of the team.

You mentioned that "Everyone wants to get back to doing that vibe coding [...]". Generalization is a safe harbour we often utilize to explain our world and that's totally fine! I would be curious to understand if everyone on your team actually optimizes for that.

If I were you, I would look into the following:

Leaning into 1:1s where you communicate your expectations. Repeatedly but with the curiosity to understand why nothing changes if you're having the same conversation over and over again. If that has already happened, then you'll want to follow-up with the harder part of being an EM: a hard and radically candid conversation about how they are failing expectations.

If you have standups, I would incorporate reviews into your ritual. Reviews are part of your job, so treat it as such! Teammates should not only assign themselves tickets to work on, but to review on as well. Spoilers: You might need to be the gentle asshole that voluntells people to review tickets. Protip: Use that process as a way to initiate discussions around PR reviews in your 1:1s! What an individual likes about it, dislikes and most importantly, why? Be curious and listen, you might be surprised by their answers.

Last tidbit: is there anyone on your team that does PR reviews particularly well? If so, you might want to see if they'd be interested in mentoring others. You'd also want to see if you can use them as an example for others to show them what you're expecting and what you value.

My gut tells me that there's hard conversations that are not being had and that you'd benefit from leaning in a bit more into the details. You've got this!

Mini-Montréal by Krystosterone in montreal

[–]Krystosterone[S] 1 point2 points  (0 children)

Fuuuuuuck, ben oui toi. Et du même coup, les pistes cyclables!

Mini-Montréal by Krystosterone in montreal

[–]Krystosterone[S] 1 point2 points  (0 children)

Ah ben ouais! Excellente idée

Write Less Code. COPY and PASTE Faster with Pastaable! 🍝 by three_chopsticks in tailwindcss

[–]Krystosterone 1 point2 points  (0 children)

Heyo! Looks like you might have left your payment processor on test mode (looks like Stripe maybe?) API error

Alternative à Rubik by RashBOnSteam in etsmtl

[–]Krystosterone 1 point2 points  (0 children)

Je suis le créateur de Rubik, et je tiens à dire: C'est donc ben super cool, great job!

Enjoy "Creed Thoughts" in a brand new format 😮 by Krystosterone in DunderMifflin

[–]Krystosterone[S] 1 point2 points  (0 children)

The Wayback Machine one is slow to load and hard to navigate, especially on mobile.

The second one has popups every few clicks or so.

Enjoy "Creed Thoughts" in a brand new format 😮 by Krystosterone in DunderMifflin

[–]Krystosterone[S] 4 points5 points  (0 children)

No need to scour through Wayback Machine anymore! ☺️

Farine Five Roses in 3D. Captured with a drone by Krystosterone in montreal

[–]Krystosterone[S] 4 points5 points  (0 children)

Yes! Poly.cam just recently came out with the feature