Engineering methodology

Being a backend developer today isn't just about writing code — it's about having a process that holds up quality from the initial analysis to production, regardless of the project.

1

Problem analysis and requirements

I understand the real problem and its requirements before designing anything. The order never changes: understand first, implement second.

2

Design and technical decisions

I choose architecture, technologies and data structure based on the actual problem, not out of habit or the latest trend.

3

Small, traceable changes

I move in small, reviewable increments, each with its own commit — never mixing a new feature with a bug fix or a refactor.

4

Testing and validation

I verify with tests, compilation, and real behavior — logs and evidence, not the feeling that "it seems to work".

5

Security and review

I review access control, data protection, and exposure surface before closing out any change with real impact.

6

Documentation and maintainability

I log decisions and technical debt explicitly, so the project can be maintained without relying on the memory of whoever wrote it.

I use AI assistance as a regular part of this process — including the platform I develop at LIT —, integrated into the same review, testing, and validation stages above, without replacing technical judgment or engineering responsibility over what ships.