Lena Park

Before a model writes a single word back to you, your prompt goes through a transformation you never see. Understanding it changes how you write prompts.

Your calendar isn't broken. It's optimizing for the wrong thing. Here's the scheduling bug hiding in plain sight.

A software team that consistently cleared their task board wasn't operating at peak efficiency. They were operating at half capacity without knowing it.

The days you move the most important work forward often look like nothing happened. That gap between real progress and visible output is worth understanding.

When Air Street Capital's research team caught GPT-4 fabricating citations with perfect formatting, it exposed a problem that gets worse as models improve.

The most productive people you know aren't disciplined despite their chaotic notification setup. Their settings are the discipline.

When you cancel a meeting, you force the work to happen differently. That different way is often better. Here's why, and what to do about it.

That bug that only appears in production isn't bad luck. It's a diagnostic. Here's what it's trying to tell you.

Most meetings exist to transfer information, not make decisions. That's a document's job, and documents do it better.

A software team's calendar audit revealed they had scheduled their best thinking hours out of existence. Here's what they found and what they changed.

You did the work. But if you never formally closed the task, your brain didn't get the memo. Here's why that gap is draining your focus.

Scheduling a meeting feels like progress. Often it's the opposite. Here's the cognitive mechanism behind decision-avoidance meetings and how to stop running them.

You're not bad at deep work. You've just handed your best cognitive hours to a calendar that doesn't know the difference between thinking and talking.

A correct bug fix can introduce new failures. Here's how that happens, why large codebases are especially vulnerable, and what the Knight Capital collapse teaches us about it.

A software team's near-miss with a half-closed ticket system reveals why marking work 'done' and actually ending it are two very different things.

You wrote detailed notes for future-you. Future-you has no idea what they mean. This isn't a tool problem. It's a documentation design problem.

The problem isn't that notifications exist. It's that most people have never thought carefully about how they're configured, and the cognitive cost compounds quietly.

A software team tracked the true cost of their weekly sync and found the math brutal. Here's what they learned about meeting overhead that nobody calculates.