Community Service Hour
Bring the work. Get it argued with, live.
Every Tuesday, one hour. Bring a change and take the floor, or listen while someone else does. The reaction is live: design, implementation, and whether it is correct.
Bring the work. Get it argued with, live.
Every Tuesday, one hour. Bring a change and take the floor, or listen while someone else does. The reaction is live: design, implementation, and whether it is correct.
You can produce a draft, and still cannot tell if it is right. A model will write the code. It will not defend the design on a live call.
You do not yet know a correct change from a wrong one. A first pull request is a rep. It is not a portfolio.
You would rather watch the argument than read a tutorial. The episodes are the worked example.
A typo fix, a small pull request, or the thing you are building. Bring a diff.
One hour, live. In the ring, the work goes on the table. In the audience, you watch that hour.
Design, implementation, and whether it is correct. Early is fine. Unchecked is not.
The episode, the notes, and the participant page are the proof it was looked at.
Never landed a correct change before? Start there.
Create a GitHub profile. Pick a project you can actually read, including this site. Make the smallest correct change and open a pull request. Then bring the diff to the call. You will get a reaction, not a medal for having a profile.
+1
A flaw in Pannellum 2.5.6 let attacker-controlled panorama configs run script on trusted domains. We trace the NPS and CNN examples, investigate urlscan.io and attacker infrastructure, and examine the risks of session theft and search cloaking, plus the fix in 2.5.7.
+1
A trading bot, torn down: order book, DuckDB, and whether the backtest is real.
Particle patterns against a copied QR code, with Unclonix.
What breaks when a trade clears in the same block.
Recaps of the live hour, the change that got argued with, and the next call.