I write about software engineering, leadership, and the judgment built through messy systems, team decisions, mistakes, and curiosity beyond work.
AI agents are entering a software delivery system built around human speed, judgment, and accountability. The next SDLC needs machine-readable context, enforceable limits, reproducible environments, and new measures of safe work.
A weekend journey from Dublin to Skellig Michael, from camping beside the Atlantic to climbing the island and visiting its ancient monastery.
Success remembers the work and forgets the luck. A reflection on how chance, support, health, and early opportunities compound into very different lives.
Why recurring cross-team meetings reveal hidden system invariants, and when coordination should move into architecture instead.
Why the daily cost of ordinary human interactions matters far more than offer letters, titles, or codebases and how subtle communication friction shapes job satisfaction.
AI agents can produce, review, and merge more work without making the team larger or giving it more shared understanding. The difficult part is deciding what counts as safe, how humans work alongside private agent sessions, and where the automation has to stop.
Some engineers do their best work between the lines of ownership, where handoffs, runbooks, dependencies, and missing context decide whether software delivery gets cheaper or more expensive.
Modern infrastructure made waste too easy. Resource limits that started as temporary safety buffers can harden into requirements unless teams keep asking what the system is actually doing.
Being liked is a nice side effect, not an operating model. Useful managers make trade-offs visible, hold the bar, and disappoint people when the work requires it.
Vibe coding is useful for discovery, but software engineering starts when generated code has to be reviewed, owned, operated, and safely changed.
LLMs made writing code cheap. They did not make understanding it cheap. Why ownership, taste, and judgment matter more now, not less.
Why Crouching Tiger, Hidden Dragon is so good, exploring its martial arts, cinematography, love story, philosophy, class system, and meaning of freedom
Why correct advice often fails to land until experience gives it weight, and why useful advice needs the scar, the context, and the cost behind the lesson.
Why telemetry explodes into cost and noise, and how to fix it: treat every signal as a decision, not exhaust, and govern ownership before it's too late.
Why engineering teams turn one trusted person into a decision bottleneck. How informal authority, hidden context, and single points of failure slow delivery
How org charts miss the real execution paths: expertise, decision rights, institutional memory, trust, and boundary-spanning people
Why I moved from WordPress to a static, markdown-first blog, trading platform convenience for ownership, searchability, and archive control
Starting a new job means starting a reputation. Your first PR, meeting, design document, or presentation shapes how people see your standards and value.
Why trial by fire onboarding hurts engineering teams, turning integration debt, missing context, and unclear ownership into talent problems
The Big Lebowski grows funnier and sadder with age in this reflection on absurd humor, failed masculinity, and the strange comfort of failure.
Headcount is not capacity. Coordination, dependencies, interruptions, and rework make roadmap math far messier than it looks.
Most roadmap problems are capacity problems. Make investment buckets visible, budget interrupts, and force trade-offs into the open.
Why roadmaps fail: the real issue is hidden systems. Decision rights, ownership, and constraints shape delivery long before prioritization begins.
Torres del Paine W Trek east to west in 4 days and 3 nights, staying at Chileno, Francés, and Paine Grande, with lessons from the trail.
Engineering status reporting works only if the system allows truth to surface early. Rules, artifacts, and escalation mechanics explained.
Incentives shape behavior. When value is invisible, proxies become targets, driving bloat, volatility, and rational dysfunction in modern orgs.
How culture actually scales in distributed teams. Why systems shape behavior, goals define incentives, and bonding aligns judgment under pressure.
Define what good looks like in engineering teams. Learn how clear standards, templates, and automation reduce ambiguity and scale execution quality.
Why airport security wait times feel random, using distributed systems, queues, bottlenecks, tail latency, and ownership to explain the delays
When clarity collapses, politics becomes survival. A blunt look at how uncertainty rewires workplaces, incentives, and trust.
A how to work with me guide covering decisions, communication, feedback, and boundaries to reduce friction and improve execution.
Using Janus and the Roman gates as a metaphor for January, this post argues for closing the doors that let old chaos shape the year.
A leadership framework for representing work across different horizons so execution, visibility, priorities, and strategy stay aligned over time.
Quiet execution means low operational noise, clear ownership and stable context, with delivery, reliability and human signals aligned.
Learn how to manage your manager through clarity, influence, early signals and trust. Practical tactics to work better with leaders and avoid surprises.
Why Kingdom of Heaven’s director’s cut works better, restoring character motives, Sibylla’s son arc, moral weight, and the film’s real story
AI erased trust in remote interviewing. Here’s how the system broke and how companies are rebuilding interviews around real human reasoning.
What years of software development reveal about progress, process, and people, reflections on why good judgment outlasts tools, and simplicity always wins.
Vibe coding happens when experience turns into instinct, the art of sensing system failures before the logs ever show them. Managers have been doing it!
Cognitive load, not hours, kills productivity. Cut distractions, tame complexity, and free brainpower for real engineering work.
Over-engineering slows delivery, raises costs, and kills products. Learn why it happens—and how to build simpler, stronger software.
Learn about Prisoner’s Dilemma. Learn why generosity, trust, and long-term cooperation lead to better outcomes than short-term competition.
Why staying at terminal levels like Senior Engineer or Engineering Manager can be a deliberate, fulfilling choice rather than a stalled career.
A simple weekly logging habit that makes performance reviews easier, preserves real achievements, and reduces the scramble of reconstructing a quarter.
A personal reflection on growing from childhood memories of Mevlana candy to a deeper appreciation of Rumi’s words and the lessons inside them.
How to brew authentic Turkish tea (çay): the right teapot, the right steep time, and the one mistake that ruins the flavour.
Practical, people-first guide to onboarding an engineering manager so they ramp fast, build trust, and lead with impact.
How engineering managers should handle technical deep dives: show system ownership, trade-offs, impact, and lessons learned.
2025’te bilgisayar bilimi okumak hâlâ mantıklı mı? Tech balonu sonrası CS kariyerinin riskleri, fırsatları ve stratejik tavsiyeler.
Discover no-nonsense strategies for setting up new international hubs, tackling cultural shifts, and ensuring long-term success.