Skip to content
Said Yaka

Topic

Software Engineering

9 essays

  1. End the Meeting With a Decision

    A design review that ends with "let's sync again" is not unfinished thinking. Here is how I write the question, name options, timebox, decide who decides, and leave with a written next step.

  2. Write Design Docs That Drive Decisions, Not Theater

    A design doc that never forces a choice is theater. Here is how I write ones that decide: when to write, how to frame the problem, and how to run review so it ends.

  3. Onboard Engineers So They Ship in Their First Week

    A tour and a stack of docs is not onboarding. Here is how I prepare before day one, pick a scoped first change, pair without taking the work, and make week one a team outcome.

  4. Ownership in Software Engineering: Owning Outcomes, Not Tickets

    Closing a ticket is not owning the outcome. Here is how I define done, own rollout and cleanup, close loops early, and share the work without hoarding it.

  5. Give Feedback Engineers Can Actually Use

    Vague praise and late notes do not change the next pull request. Here is how I give feedback engineers can actually use: specific, timely, and followed up.

  6. Unblocking Teammates Is the Highest-Leverage Work You Can Do

    A blocked teammate burns more hours than your interruption. Here is how I notice stuck work, unblock it without taking over, and still protect focus time.

  7. How to Be a Mentee Worth Investing In

    Mentors invest in people who make help cheap to give. Here is how I arrive prepared, ask about decisions, close the loop, and turn advice into a pattern.

  8. Code Review Is Mentorship in Disguise

    Code review is the highest-leverage teaching loop on an engineering team. Here is how I review in a way that grows the author, not just the diff.

  9. Working at Evertune (NYC, 2025)

    A personal look at what it’s like working at Evertune as a software engineer in NYC — the people, the collaboration, and what makes it different.