ONENEPT STUDIOS :: ONE OPERATOR :: REMOTE
READCODE.PROVE THEGAPS.
READ CODE.PROVE THEGAPS.
I find where a codebase and its own documentation disagree, and prove it with a script anyone can run. Available for contract work, remote.
NNAWUOGO
FOUNDER + DESK
01 :: IN OTHER PEOPLE'S CODEBASES
PUBLIC THREADS. NOTHING PRIVATE, NOTHING CLAIMED.
Public threads with named maintainers in them, including the parts where I was wrong and said so.
NOTHING HERE IS MERGED YET. All open. The finding stands on a script you can run, not on whether a busy maintainer got to it.
PR #18685 and the thread around it
WHAT I FOUND
The page listing which entity types support incidents was wrong, and so was my first correction of it. Support is declared in six separate files that no longer agree.
HOW I PROVED IT
Derived all six with a script, after the hand-written version had already been wrong once. Ten types accept an incident, seven carry the summary aspect, five can be read back. The table is now generated at build time.
Issue #18999 and PR #19115
WHAT I FOUND
Raising an incident on an ML model returns a URN and looks like it worked. Nothing can read it back, and no error is ever reported.
HOW I PROVED IT
Opened the issue, released the ML half to a contributor who scoped it first rather than duplicating him, took the schemaField half, and held it in draft while an authorization question was open.
DATAHUB #18684
Two self-hosted failures that produce no error at all. Each cost an afternoon and left nothing to search for.
datahub-project/datahub ↗DATAHUB SKILLS #66
What breaks downstream if this table or column changes. The question every data team asks before a migration.
datahub-project/datahub-skills ↗02 :: BUILT ON DATAHUB
LIVE. OPEN IT.
03 :: DESK RULES
01
Live data or nothing.
If it does not run against real data arriving in real time, it is a slide, not a product.
02
Every output carries its record.
Where it came from travels inside the thing itself, not in a spreadsheet somebody has to be trusted to keep.
03
Derive it, do not maintain it.
A hand-written list of what a system supports is wrong the week after it is written. If it can be read from the source, read it from the source.
04
Settle everything.
A claim that cannot be traced back to a record is marketing. That includes my own claims, including the ones I got wrong first.
THE RULES ARE NOT ASPIRATIONAL.
SCROLL UP: THE THREADS PAID FOR THEM.
WHY ONENEPT.COM
AND NOT MY NAME
Onenept Studios is a real company. It is how the work ships and how it gets invoiced, so a first contract needs no paperwork set up from scratch.
If you are hiring, you are hiring me, and I am on this page. If you are contracting, the entity is already here.
START A CONVERSATION