who writes this

Where each one cost something

1. Context before tooling

   Stack choice is the last decision, not the first. What comes before is the real constraint: deadline, team, operations and what is already running.

   A tool picked before the problem becomes a requirement in disguise. On a closing portal already running on Lumen, the right answer was not to migrate: it was to measure what was slow and fix it in place. The existing stack is part of the context, not an obstacle to it.

   seen inStechClubprofessionalPortalAZprofessional

2. Decision before movement

   Every meaningful change has an alternative that was turned down and a written reason for the cut. Without that it is activity, not a decision.

   Writing down what was turned down costs minutes and saves the argument six months later, when nobody remembers why the obvious path was not taken. That is why the case schema on this site has a field for rejected alternatives.

   seen inTaskForgeprofessionalJarbaspersonal

3. Evidence before verdict

   A number without scenario, window and limit is not evidence: it is an adjective with a digit. A metric arrives with the condition under which it was measured.

   When the measurement does not show up, the number comes out — from both places it is published, on the same day. That holds for the résumé and for the portfolio.

   seen inProfessor Jarbas Financial AssessmentprofessionalPortfolio APIpersonal

4. Measure before optimizing

   An index is derived from the predicate that shows up in the execution plan, not from a guess about which column looks hot.

   On a monthly closing screen the guess pointed at row volume; the measurement pointed at 316 of 354 queries per load coming from an N+1. Seven indexes later the time went from 4,271 ms to 354 ms — the guess would have created none of them.

   seen inPortfolio v2personal

5. Security as acceptance criteria

   Authorization is not decided by the cheapest check available. If the correct check does not fit the layer, the layer changes — not the check.

   The admin in the first, Next.js version of this api authorized by cookie presence, because the middleware ran on the Edge and could not reach the database. The fix was not to relax the criterion: it was to sign the cookie so the Edge had something to verify, keeping the database check where it belongs.

   seen inPortfolio APIpersonalStechClubprofessional

Education and certificates

What I've used the longest