Category
7 articles in this category.
Written by me.
A technical portfolio is judged on evidence, not adjectives. See how README files and technical writing turn projects into proof of skill, with each claim's status explicit.
The mix of assets matters more than the choice within them. Read how to set a target, a worked example, and why the horizon decides the rule.
How products are named and related is a strategic choice. Read the two models, a worked decision, and why the hybrid is common.
Diversification, control, cost, and time are the actual differences. Read a worked comparison and when each structure fits.
Rebalancing restores a target mix, which costs money and may trigger tax. Read the rules, a worked example, and when to leave it alone.
A professional reputation is accumulated evidence, not a slogan. Read how to build it with verifiable work and why self-promotion without proof backfires.
A technical portfolio proves skill through reproducible artifacts—code you can run, writing you can verify, systems you can explain—not through tool lists or certificates.