Be a T-shape developer

by Mar 25, 2024

Be a T-shape developer

I always advocate developers to specialize when they are becoming senior. But don’t lose track of the rest of the playfield.

So be broad, know a lot of technologies and areas, but also go deep into one or more. That is a T-shaped developer.

Why be a T-shaped developer?

1️⃣ Being an expert will give you respect and the money.

2️⃣ Being broad will give you insights on how to solve it differently and you can help others in your team.

One risk!

Don’t be to stuck on your specialization. Switch when it is dying.

Don’t be that COBOL developer. Maybe not the correct example, because people pay a fortune to keep their old code running… 😉

What kind of developer are you?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more