Building Career Capital: A Project-Based Approach to Professional Growth

Sustainable, long-term professional growth requires deliberate and sustained practice through artefact-producing projects.

Introduction

At the close of 2025, I am launching this blog to take a more intentional and proactive approach to developing my career. In an evolving technical landscape, maintaining a competitive edge requires a deliberate approach to skill acquisition.

Why a Blog?

In planning my career development, I have been inspired by Cal Newport’s So Good They Can’t Ignore You book. His thesis is that one should focus on building career capital through deliberate practice and shipping real work, as a craftsman, rather than chasing passion. By “career capital”, Newport means those skills and experiences that make you valuable in your field.

This blog represents my commitment and promise to myself to be more deliberate about accumulating career capital by acquiring new skills and building a portfolio of tangible projects over time, while keeping myself accountable to continued and consistent progress.

What to Expect

Projects

Most blog posts will be project write-ups. When I complete a project, I will publish one post describing the problem, the approach, the trade-offs, and the result, in a structured format similar to my project posts. If a project is larger, I may write a short series of articles, tracking the delivery of meaningful milestones with concrete artefacts, such as the writing of a project plan or the completion and deployment of a feature. My rulebook is simple:

No inspectable and reproducible artefact, no post!

Quarterly Audits

Once per quarter, I will publish a brief audit, tracking:

• what milestones have I reached,
• what I shipped,
• what skills were acquired or improved,
• what mistakes, costs or trade-offs I incurred, and
• what I will focus on next.

Measuring Career Capital

While sounding appealing, “career capital” is somewhat vague. To track my progress, I will use Inspectable Shipped Hours (ISH) as a proxy for measuring my progress during focused, deep-work sessions. Hours can be counted as ISH if they meet the following criteria:

1. Inspectable: they were used to create an artefact that someone else can review, such as a code repository, slides, workshop recording, published papers, or course capstones with a public artefact.
2. Shipped: the artefacts are in a finished state, meaning they are built, published, documented, shared publicly, and if applicable, tested and deployed.
3. Role-relevant: The work strengthens my applied machine learning and software engineering skills, or other skills directly translatable to my career.

Items that would count towards ISH are, for instance:

• Learning projects.
• Data Structures and Algorithms, if implemented, documented and added to my GitHub.
• Open source contributions.
• Online courses or certifications if they include a shippable, public artefact (e.g., a capstone project).
• Talks or presentations I deliver, if recorded.
• Work-related projects, if I have permission to share them publicly.

This system is intended to keep the focus on deep work, allowing me to prioritise building and shipping over passive content consumption. Reading, courses, and talks are useful inputs, but they count towards ISH only when they lead to a shipped public artefact, as unpractised knowledge is quickly forgotten.

Conclusion

In short, this blog is a practical accountability tool. I will focus on shipping inspectable work, documenting it, and reviewing progress through quarterly audits. The metric is intentionally simple, allowing me to track time spent producing artefacts that others can review.

Next, I will publish the first posts on the work I have completed in the past few months, including two personal projects, a framework for machine learning projects, and the plans for two upcoming larger projects.

Here’s to a great start to 2026!