A1aM0

7 ms·

1.
by A1aM0 7mo ago
I did spend extra time polishing wording in my replies.
2.
by A1aM0 7mo ago
You’re right: structured assessments are old news. The thing I’m testing is not “new tests,” but a tighter system: derive the rubric from real team tasks, apply the same rubric to both public evidence and live assessments, and make every sc
3.
by A1aM0 7mo ago
This is a very fair critique, and I agree with it. You’re right that many strong engineers can’t legally share employer code, and “has OSS time” is not a universal signal. So I’m now thinking of this as a dual-path system: 1) Public evidenc
4.
Ask HN: Does "task-derived JD and evidence-based candidate" make hiring better?
1 points by A1aM0 7mo ago|6 comments
5.
by A1aM0 8mo ago
You hit the nail on the head regarding Juniors—they are already in a tough spot, and I certainly don't want to build a tool that makes that worse. However, my hypothesis is that matching on 'Problem Vectors' might actually he
6.
Ask HN: Could we replace Job Descriptions with actual Git Issues?
1 points by A1aM0 8mo ago|2 comments
7.
by A1aM0 9mo ago
I love the "mental model" approach here. Most guides I've seen either get bogged down in the minute details of TLS/Handshakes immediately or are way too high-level. The interactive packet visualization is a really nice t
8.
by A1aM0 9mo ago
Pavlo is right to be skeptical about MCP security. The entire philosophy of MCP seems to be about maximizing context availability for the model, which stands in direct opposition to the principle of Least Privilege. When you expose a databa
9.
by A1aM0 9mo ago
Love it. It’s funny how we are now building modern tools just to try and get back that simple 'Palm Pilot morning read' vibe.
10.
by A1aM0 9mo ago
The 'once a day' fetching limitation is a fascinating idea. It really captures the vibe of reading a physical newspaper in the morning rather than constantly checking for updates. I think many of us could use a tool that enforces