This article posits that professional experience is not a function of time, but a result of intentionally seeking out and solving a diverse range of technical problems. It encourages engineers to proactively engage with complex issues in professional and open-source environments and to document their findings to solidify their learning.
Key points
Technical experience is built by encountering and resolving varied problems, not simply by spending time in a role.
Actively seeking out low-level technical challenges like debugging flaky tests or investigating deployment errors accelerates professional growth.
Developing deep domain expertise can be achieved by positioning oneself as a go-to resource for specific technical issues.
Documenting technical findings through public channels forces deeper analysis and reinforces retention of knowledge.