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

Microsoft Teams: Too Many Apps in One?

Microsoft Teams: Too Many Apps in One? All-in-one apps like Teams? That’s a hard pass from me. Microsoft Teams wants to be the one app to rule them all. But I’m the guy who likes my apps separate, like LEGO bricks—not superglued together. I open my To-Do app...

read more

I see your comment. And I see AI fingerprints all over it.

I see your comment. And I see AI fingerprints all over it. You know the ones where you think: Bro... did you even read my post? 😅 I get it. We want engagement. We want the algorithm to give us more eyeballs. But fake engagement is still fake. Here’s what happens when...

read more

Abstract the abstraction 🤯.

Abstract the abstraction 🤯. .NET devs, we love our patterns... maybe too much. For a simple CRUD app, I've seen: Repositories – because obviously we can't query directly, that's too mainstream UnitOfWork – like transactions, but now with extra ceremony Services –...

read more