A career, visualized

Miguel Laginha

Staff software engineer and technical lead. I build web products across the stack, with a particular interest in backend systems.

How my work shifted · 2006–2016

This chart is historical: it covers 2006–2016, not my current work mix. Content updated .

Each row is a year; each column is a discipline. Percentages are estimated, exclusive shares of working time—not proficiency. Column labels identify disciplines; stronger color means a larger share. White means a recorded 0%; full discipline color means 100%. Hatched cells marked “Unknown” have no recorded value.

  • 0%
  • 50%
  • 100%
  • Unknown

Scroll the matrix to reach every year and discipline. With a keyboard, focus the matrix and use the arrow keys. Select a year for its exact values and recorded context.

Working-time shares · 2006–2016

Three shifts in the recorded years

  1. 2008. The chart broadens from Java-only allocations to include Rails development and project management.
  2. 2011–2014. Software architecture takes the largest share, alongside project management and Python development.
  3. 2016. The recorded allocation is entirely full-stack JavaScript development.

These turning points describe the estimated allocations above. They are not a list of employers or projects, and do not extend the history beyond 2016.