Geekfolio

Fnplus, 2018 to 2020

The profile I designed at nineteen, run once on me, with the number left out.

Geekfolio was going to rank engineers on everything they learn in public: an API-fed trail from across the web, our own assessments, and a tracker for how people work together. No screen of it was ever published, so this is the design itself, running on the one person this site is about.

the machine, as designed in 2019
Geekfolio's machine, run on one person Three inputs feed three stations. the trail, pulled through APIs, drawn solid, runs on this site, filled from the record with rows in every year from 2018 to 2026. Our own assessments and the collaboration tracker are drawn dashed: designed, never run, and designed, never built. Pull and file stamp done, one slot for every year. Rank, against everyone else, holds: it finds one person and five places empty, because a ranking needs more than one person. What comes out is the record, year by year, every row linked to the thing itself, and a place in a ranking is not printed. inputs the trail, pulled through APIs here: every row bound to its link ’18 ’19 ’20 ’21 ’22 ’23 ’24 ’25 ’26 our own assessments geeks garage sessions andhackathon-like events designed, never run collaboration tracker computer vision and AI designed, never built stations pull from the web here: by hand done file under the year 2018 2026 every year rank against everyone else one person here, the rest it would need are not held what comes out the record, year by year every row linked to the thing itself a place in a ranking not printed
Geekfolio's machine, run on one person, drawn top to bottom Three inputs feed three stations. the trail, pulled through APIs, drawn solid, runs on this site, filled from the record with rows in every year from 2018 to 2026. Our own assessments and the collaboration tracker are drawn dashed: designed, never run, and designed, never built. Pull and file stamp done, one slot for every year. Rank, against everyone else, holds: it finds one person and five places empty, because a ranking needs more than one person. What comes out is the record, year by year, every row linked to the thing itself, and a place in a ranking is not printed. inputs the trail, pulled through APIs here: every row bound to its link 2018 2026 own assessments geeks garage,hackathon-like never run collaboration tracker, computervision and AI never built pull from the web; here, by hand file under the year 2018 2026 rank against everyone else one person here held: a ranking needs a population a place in a ranking: not printed the record, year by year every row linked to the thing itself
Fig. 1. Geekfolio's machine, drawn from how I described it and run on the record. Two of its three inputs never ran, and the ranking stops, because a ranking needs more than one person. Drawn for this page only.

How it would have worked

Three stations, in the order the data moves.

  1. 1 of 3

    Pull

    Good engineers keep learning from informal sources, so the trail was the input that mattered: what you built, wrote and showed up to, pulled in through APIs.

    here: every row bound by hand to its link

  2. 2 of 3

    File

    Everything lands under the year it happened, so a reader sees the whole run of it instead of a summary line.

    here: something in every year since 2018

  3. 3 of 3

    Rank

    The last station put people in order. It needs a population to do that, and this site has one person in it, so it stops here.

    here: held, and nothing printed in its place

The words, 2019 and now

Fnplus was my first company, and its product page is still up. Geekfolio is the fourth of five tools on it, beside Footsteps, Enroll Me, News Bot and Geeks Garage. Between the 2019 capture and today, two of its lines changed.

research card
Learning Locker & Geekfolio (Smart CVPortfolio)
tool line
A Learner Portfolio Of Geeks Based On Tracking Data Skill-portfolio of geeks based on learning tracking data

A smart CV became a smart portfolio, and tracking data became learning tracking data. In 2020 I wrote the argument down on a page that is still online: a résumé does not communicate expertise, offers nothing to back it up, and simply sums up your skills.

The idea was that an engineer is the sum of everything they do across the web, and that keeping at it is what counts. This site runs it on one person: the record, year by year from 2018 to 2026, every row of it linked.

My reading shelf is on a page of its own.

Your visit

The original product kept Rewards and Achievements for the person being measured. Here they belong to you instead.

Pick what you came for

Three ways through the site. Follow one to its end and it goes on your list. None of them adds to your count, and you don't have to pick.

  • The work Work · ChargerDojo, to the end · Agent platform, to the end
  • The record Record on the home page · The record · The record's years · The CV
  • The story About · Geekfolio · Reading

22 pages count: every page the top bar and the footer link to, each write-up, the record on the home page and the end of the reading shelf. Reading something to its end counts three times over, and that is the end of each write-up and most of the record's years. The legal pages don't count. The first time you reach one it's marked on the map below, and the line in the footer keeps the count. It stays in your browser under one key and goes nowhere else. There's no account and no cookie, and I don't measure you or compare you with anybody. See all of them and you get a card at the end.

Two pages are not on this map.