Technology index
The level field is the part that matters here. Many people list twenty technologies without separating what ran in production from what was a tutorial, so the distinction is explicit:
| Level | Means |
|---|---|
applied-in-production | I used it in a system that runs and that other people depend on |
knowledge | I can work with it, but I have no system in production to prove it |
learning | studying it now, I have not delivered anything with it yet |
The column on the right says where each one is used, which is the question that matters.
Language and framework
| Technology | Level | Where I use it | Since |
|---|---|---|---|
| .NET / C# | applied-in-production | the base of everything I write, from Framework 4.5 to .NET 10 | 2022 |
| Angular | applied-in-production | maintenance of what already exists, not new architecture | 2022 |
| React and TypeScript | applied-in-production | whole products, both ends; it is where I write frontend today | 2023 |
Details in Backend .NET and Frontend React and TypeScript.
Persistence
| Technology | Level | Where I use it | Since |
|---|---|---|---|
| Oracle | applied-in-production | the database behind most of the systems I touch | 2022 |
| Entity Framework Core | applied-in-production | the default ORM in what I write | 2022 |
| Dapper | applied-in-production | where the query needs to leave the ORM | 2022 |
| MongoDB | applied-in-production | documents, where the model is not relational | 2023 |
| PostgreSQL | applied-in-production | in the newer systems | 2023 |
| TimescaleDB | applied-in-production | telemetry time series, in the industrial monitoring | 2026 |
Details in Data and persistence.
Quality
| Technology | Level | Where I use it | Since |
|---|---|---|---|
| xUnit | applied-in-production | the suite of most of what I write | 2022 |
| FluentValidation | applied-in-production | declarative validation, in the same set | 2022 |
Details in Quality and context engineering.
Platform and delivery
| Technology | Level | Where I use it | Since |
|---|---|---|---|
| Docker | applied-in-production | packaging .NET applications to run in containers | 2025 |
| Kubernetes, ArgoCD and Helm | applied-in-production | where what I deliver in containers runs, and how the delivery gets there | 2025 |
| GitLab CI | applied-in-production | build, test and publishing pipeline for what I deliver | 2022 |
Details in Platform and delivery.
Integration and real time
| Technology | Level | Where I use it | Since |
|---|---|---|---|
| MQTT | applied-in-production | machine telemetry, in the industrial monitoring | 2026 |
| SignalR | applied-in-production | the real-time dashboard of the same system | 2026 |
| Keycloak / OIDC / JWT | applied-in-production | authentication, where it is centralized | 2023 |
| Polly | applied-in-production | retry and circuit breaker policies in the integrations | 2024 |
Details in Integrations and distributed systems.
What I declare as knowledge, without production
| Technology | Level | Note |
|---|---|---|
| Broker-based messaging (RabbitMQ, Kafka) | knowledge | I never needed it in production, and it is the gap I would close first |
| gRPC | knowledge | no system in production |
| Event sourcing | knowledge | studied, never applied |
Pablo Mickael Quevedo Senior Software Engineer · Novo Hamburgo, Brazil