Gecko

Challenges

1. 01

   Correct numbers from messy inputs

   Problem

   Equipment data arrives in inconsistent formats. Some values came through as strings or nulls, which led to wrong readings, like severe values showing as zero.

   Approach

   I made parsing defensive and explicit, and added tests for invalid and edge‑case inputs so regressions get caught in CI.

   Outcome

   Live values are reliable, and bad input fails loudly in tests instead of quietly in production.

2. 02

   Keeping the framework current

   Problem

   Older Spring and Jackson versions were flagged with security issues.

   Approach

   I upgraded to Spring Boot 4 and Jackson 3, fixed the breaking changes, and added SBOM scanning to the pipeline.

   Outcome

   The service runs on supported versions with its dependency risk tracked.

What I took away

• Treat every external value as untrusted until it's parsed and validated.
• A test for each bug you fix is how a codebase gets more reliable over time.