Why we built this

The problem we had

The gap that this site exists for is a specific one. A software student finishes two years of a degree, can write a working application, has three or four assignments behind them — and then opens a job application and has no idea what to attach.

The advice available is either too general to act on (“build projects!”) or written for people several years further along. The concrete questions go unanswered: which of my projects is worth showing, what goes in a README, how do I describe something I built without sounding like I am overstating it, why does my GitHub look like a filing error.

What we kept noticing is that the students asking these questions could nearly always code. The gap was never programming ability. It was that their ability was not legible — sitting in undocumented repositories with names like assignment3, none of them deployed. That is a documentation and positioning problem, and it is much faster to fix than a skills problem.

What we are trying to do

Answer the specific questions properly, in public, for free — and then sell an implementation system to the people who want the whole thing organised for them rather than assembled from fifteen articles.

That order matters. The free toolkit is not a teaser with the useful parts removed. The checklists are complete, the templates are the ones we would use, and the five project briefs are five of the thirty from the paid library — the same specifications, not summaries. If the free version turns out to be all you need, that is a good outcome.

What we will not do

A few things are worth stating plainly, because the category this site sits in is full of them.

• No invented testimonials or customer numbers. When we have real ones, they will appear with names attached. Until then there are none on the site, and that is deliberate rather than an oversight.
• No fake scarcity. The launch price has a real deadline that is set in configuration and does not reset. There are unlimited copies of a digital product and pretending otherwise is insulting.
• No job guarantees. Hiring depends on the market, the role, your interviews and a lot of things nobody selling a product controls. We sell the part that is controllable: whether your portfolio clearly demonstrates what you can do.
• No fabricated portfolio examples presented as real. The three worked examples on this site are constructed, and it says so on every page they appear on.
• No advice that requires you to overstate your ability. Everything in the toolkit assumes you have to be able to defend what you claim, in an interview, out loud.

How this is funded

One paid product: Developer Portfolio Builder. There is no advertising on the site, no affiliate links in the guides, and no sponsored recommendations. When we suggest a host or a tool it is because it is what we would use, and every one we recommend has a free tier that covers a student portfolio.

The free resources are the argument for the paid one. That only works if they are genuinely useful, which is a constraint we are happy to be held to.

Build in public

This site is new. The product is new. Rather than pretend otherwise, we would rather say what stage things are at: the free toolkit is complete and in use, the paid product is in its launch window, and the resource library is being written continuously.

If you use something here and it is wrong, unclear, or missing the thing you actually needed, tell us — vantonderstuart@gmail.com. Corrections from people who are currently in the situation the site is written about are worth more than anything else we could do with an afternoon.