Have you ever experienced technical debt (burnout)?

Technical debt refers to the accumulated shortcuts and compromises in code, architecture, or processes that over time make project development more complex. Burnout is emotional and professional exhaustion, often related to prolonged stress and overload.

Yes, I have experience working with technical debt. For example, in one project, due to tight deadlines, we temporarily used "workarounds" and did not refactor the code, which later led to difficulties when adding new features. To address this, we allocated time for refactoring and writing tests.

Regarding burnout, I have faced periods of high workload, where it was important to prioritize correctly, take breaks, and maintain a balance between work and rest. This helped to preserve productivity and motivation.