Post

More from @lucaronin

Luca Rossi ꩜

@lucaronin

Jul 26, 2023

📋 Underperformance Checklist

I believe 80% of performance is systemic, rather than individual. So, with underperformers, it is useful to ask yourself questions about the *context* they are working in.

Here is a 15-items checklist I built for this over time 👇

🌟 Culture

1. Are they aware of the company values?
2. Are they aware of the company vision and purpose?

🔄 Systems

3. Do they know what is expected of their role?
4. Are they assigned to a role/work that isn’t suited to their skills?
5. Are they let down by tooling / DX?

Read 6 tweets

Luca Rossi ꩜

@lucaronin

May 8, 2023

How to Prioritize Bugs 🐛

Bug fixing is not exactly everyone's favorite engineering activity.

It's a tricky process that requires coordination between several stakeholders — PMs, Customer Support, QA, and Engineers.

Let's figure out how to make it work 👇

Every team has a slightly different process, but it always involves some version of these steps:

1) ✍️ Report — bugs are entered in some kind of backlog.
2) 🚥 Prioritize — bugs are triaged and a priority is assigned.
3) 🔨 Fix — bugs are addressed and fixed by Engineers.

Out of these three, I have seen the most problems happen in the *prioritization* stage.

👑 Who takes such decisions?
⚔️ How do we avoid conflicts?
⏱️ How much time should we spend on it?

Let's figure this out 👇

Read 12 tweets

Luca Rossi ꩜

@lucaronin

May 6, 2023

Should you put side-projects in your CV? 🕹️

The goal of your CV is to get you to the first interview call. Then it’s on you — but a good CV can easily bring you 3x the interviews than a bad one.

So, there is debate about what activities to put in there besides your work ones 👇

To me, the rule of thumb is that you should include anything that proves either *good impact* or *good skills*.

Both is better, of course, but it’s ok to display projects that mostly demonstrate one of them.

So, about tech skills, common entries are stack overflow profiles, open source contributions, or research papers.

Technical side projects are ok granted they are not trivial:

– Simple dashboard in React → No thanks
– Fullstack app to run a movie club with friends → Yes!

Read 7 tweets

Luca Rossi ꩜

@lucaronin

Apr 12, 2023

Some of the best-performing engineering teams DON'T use a Staging environment to test things before release.

They just push to production.

1) Why?
2) How do they pull this off?
3) Should you use Staging yourself?

I talked with tens of teams and are the lessons I learned 👇

Staging envs have two main issues:

1) They are often not reliable — cos it's hard to keep them at parity with prod.

2) They make releases many times slower — because of the additional release level and batching changes together.

Let’s see why these are serious problems 👇

🚚 Being at parity with prod

For Staging to be useful, it has to catch a special kind of issues that:

A) would happen in production, but
B) wouldn’t happen on a developer's laptop.

What are these issues?

Read 20 tweets

Luca Rossi ꩜

@lucaronin

Apr 10, 2023

I used to schedule things to do based on my available *time*.

Over time, though, I found that time just *loosely* correlates to how much work I can do.

For two reasons:

1) ⚡ Time ≠ energy — there is a limited amount of energy I can spend over 1 day.

2) ⚖️ Not all tasks are created equal — some are more cognitively intense, others are lighter.

So, two hours of design work can easily knock me out for the day. Two hours of email feels lighter.

For dev process we invented story points to decouple effort from time. They are totally made up, but they kinda work.

What is the equivalent of story points for our lives?

Enter pomodoros 🍅👇

Read 8 tweets

Luca Rossi ꩜

@lucaronin

Dec 16, 2022

✨ Product Engineers ✨

The rise of Product Engineers fits a broader trend of making product/tech roles *wider* and giving people more ownership and autonomy.

To me, the Engineers vs Product Engineers feud resembles the one between Product Owners and Product Managers 👇

🔴 Product Owners have mostly tactical responsibilities.

They groom the backlog, write user stories, prioritize what to do next, and attend all the Agile meetings.

Their focus is short to mid-term.

🟢 Product Managers have more strategic responsibilities.

There is overlap with Product Owners about how they both shape what to do next, but PMs are also responsible for the product vision and success.

Their focus is mid to long-term.

Read 5 tweets

Share this page!

Enter URL or ID to Unroll

Luca Rossi ꩜

Try unrolling a thread yourself!

More from @lucaronin

Luca Rossi ꩜

Luca Rossi ꩜

Luca Rossi ꩜

Luca Rossi ꩜

Luca Rossi ꩜

Luca Rossi ꩜

Did Thread Reader help you today?

Don't want to be a Premium member but still want to support us?

Send Email!