Archive
1046 posts · Page 43 of 88. ← Blog
Most engineers hit a ceiling that has nothing to do with their technical ability. They can design the system, write the code, solve the hard problem — and then stall, because the next level of impact runs entirely through other people: persuading, collaborating, leading, handling conflict, staying steady under pressure. That ceiling is emotional intelligence, and the good news is it's not a fixed trait you either have or don't. It's a set of skills, and skills can be learned.
Most engineers hit a ceiling that has nothing to do with their technical ability — the next level of impact runs entirely through other people. That ceiling is emotional intelligence, and the good news is it's not a fixed trait you either have or don't. It's a set of skills, and skills can be learned.
Why a scorecard trained only on funded loans quietly overstates its own accuracy, and the inference techniques that pull the declined population back into view.
Why credit models trained only on approved-and-funded loans are biased, and the reject-inference techniques (reclassification, parceling, augmentation) that correct for the applicants you never observed.
In finance you never update and never delete — you only append. Event sourcing gives you a perfect audit trail; the right to be forgotten is where it fights back.
In finance you append, never update or delete. Event sourcing gives a perfect audit trail; the right to be forgotten is where it fights back — and crypto-shredding is how you reconcile the two.
Structs let you bundle related data into a single named type — the closest C gets to an object. Combined with pointers and heap allocation, they're how you build every data structure C is famous for: linked lists, trees, hash tables. This post covers structs, their cousins unions and enums, the memory-layout details that bite (padding), and puts it all together to build a linked list from scratch.
Structs let you bundle related data into a single named type — the closest C gets to an object. Combined with pointers and heap allocation, they're how you build every data structure C is famous for: linked lists, trees, hash tables. This post covers structs, unions, enums, the padding that bites, and builds a linked list from scratch.
Fundraising, stripped of mystique, is a sales process — you're selling equity to investors — and it runs on the same fundamentals as any sale: a compelling pitch, momentum, and the leverage that comes from having options. Most founders approach it as supplication (please fund me) rather than as a mutual evaluation between parties choosing each other, and that framing costs them. And the relationship doesn't end at the wire transfer: your investors are your partners for years, so how you choose and work with them matters long after the round closes.
Fundraising, stripped of mystique, is a sales process — you're selling equity — and it runs on a compelling pitch, momentum, and the leverage of having options. Most founders approach it as supplication rather than mutual evaluation, and that framing costs them. And the relationship doesn't end at the wire transfer.
How lenders turn a model's raw probability into the specific, legally required reasons a declined applicant must receive.
Turning model outputs into legally-required adverse-action reason codes. Global vs local explainability, SHAP values, mapping contributions to reason codes, and fairness checks (disparate impact) that regulators expect.
Every movement of money touches at least two accounts, and the entries always sum to zero. That one invariant is the backbone of a correct financial system.
Every transaction is balanced postings that sum to zero — enforce it at write time. The ledger is append-only, and booking, value, and settlement time are three different clocks you must not conflate.
Stack memory is automatic but rigid — sized at compile time and gone when a function returns. For data whose size you only know at runtime, or that must outlive the function that created it, C gives you the heap and four functions to manage it: `malloc`, `calloc`, `realloc`, and `free`. With that power comes C's heaviest responsibility: every allocation you make, you must free — exactly once, and never use again.
Stack memory is automatic but rigid. For data whose size you only know at runtime, or that must outlive its function, C gives you the heap and four functions: malloc, calloc, realloc, and free. With that power comes C's heaviest responsibility: every allocation you make, you must free — exactly once, and never use again.
Venture capital is so culturally dominant that raising it can feel like the definition of startup success — but VC is a specific tool for a specific kind of company, and taking it commits you to a specific, high-stakes path. For most businesses, it's the wrong fit, and the alternatives — bootstrapping, revenue-based financing, venture debt, grants, crowdfunding — are not consolation prizes but often the better choice. The most valuable thing a founder can understand about funding is when not to raise venture capital.
Venture capital is so culturally dominant that raising it can feel like the definition of success — but VC is a specific tool for a specific kind of company, and the alternatives (bootstrapping, revenue-based financing, venture debt, grants, crowdfunding) are often the better choice. The most valuable thing a founder can understand is when *not* to raise VC.
How WOE binning turns raw variables into monotonic, interpretable predictors on a log-odds scale, and how Information Value ranks which features earn a place in a regulator-defensible scorecard.
How WOE binning turns raw variables into monotonic, interpretable predictors, how Information Value ranks feature predictive power, monotonic binning, handling missing/rare bins, and why this discipline underpins regulat…
The first decision in any financial system, and the one people get wrong most often: never store money in a floating-point number.
Never store money in a float. Use integer minor units or fixed-scale decimals, round half-even, allocate so splits sum exactly, and treat currency and the FX rate you used as first-class, auditable data.
In a multi-agent system, a shared identity means one compromised agent carries every agent's blast radius. Here's how I split agent identity across three layers.
Most teams give a whole multi-agent app one workload identity, so one hijacked agent has every agent's blast radius. Splitting identity across app, cloud, and crypto layers shrinks it to a single role and makes the audit trail provable.