Ginocorp Industries

Field guides for the parts of engineering nobody templates: code review, RFCs, post-mortems, incidents, promotion cases. Writing →

[Ginocorp Industries @__Ginocorp__]

Ten failure modes, three root causes, and how to read a part like a log:

https://t.co/twetl308Le

[Ginocorp Industries @__Ginocorp__]

A 3D print that fails doesn't throw. No logs, no stack trace, no exit code. The printer finishes, and the object is just wrong.

But the part is a time-ordered record of its own execution. Height is elapsed time.

So "where did it break" answers "when did it go wrong."

[Ginocorp Industries @__Ginocorp__]

The twelve questions I ask instead, in full, nothing held back:

https://t.co/pE1G2FGLcJ

[Ginocorp Industries @__Ginocorp__]

Every code review checklist you've used was written for a diff whose author could explain it.

Nobody wrote that assumption down, because until about two years ago it was free.

Now a meaningful share of diffs arrive with no reason behind them. The checklist hasn't changed.

[Ginocorp Industries @__Ginocorp__]

I wrote a playbook on how software engineer promotions really work.

50 pages. Google, Meta, Amazon, Microsoft ladders side by side. Craft, writing, sponsors, packets. Five worked cases, one stalled two years. A 12-month plan.

$12, no email wall 👇

https://t.co/qsbOvHj9aH

[Ginocorp Industries @__Ginocorp__]

Quick test for whether you should actually be a senior engineer.

Your manager vanishes for a month.

Do the team's technical decisions still get made, and made well?

If people come to you, that's senior.

If the answer is "we'd wait," you're not. However good your code is.

[Ginocorp Industries @__Ginocorp__]

Engineers: the meeting math from GitHub's Good Day Project is worse than you'd guess 📉

1 meeting in a day → 99% chance you make progress
2 meetings → 74%
3 meetings → 14%

The cliff is between two and three.

Same study: pull request count predicted nothing.

[Ginocorp Industries @__Ginocorp__]

I put the full list up for free.

All 62 EM interview questions in 9 categories, plus the prep method that works: build a situation inventory first, then map it against the categories. The empty ones are your real gaps.

No email wall 👇
https://t.co/Jl0vzCqfqA

[Ginocorp Industries @__Ginocorp__]

@CollinWilkins7 The hard part is scoring those in an hour. One format that covers most of the list: hand them a real design doc from your codebase with two arguable decisions in it, and ask what they'd push back on and how they'd raise it with the author.

[Ginocorp Industries @__Ginocorp__]

That's 6 of the 62 questions in the playbook.

It also has 7 full worked answers, the resume formula, negotiation scripts, and a 4-week search calendar.

52 pages, $10:
https://t.co/OvOHt1HRy9

[Ginocorp Industries @__Ginocorp__]

Most EM interview prep stops at "tell me about a time you had conflict."

Here are 6 questions that actually come up in engineering manager loops, and what the interviewer is really checking with each one. 🧵

[Ginocorp Industries @__Ginocorp__]

6. "What questions do you have for us?"

Asked as a formality, scored as a signal. Ask what happened to the last person in the role, and how the team found out about the last reorg. Those two answers tell you more than the rest of the loop did.