Yusuf Aytas
yusufaytas.com · Personal blog · on HN since 2012
Yusuf Aytas writes about software engineering leadership, API design, incentives, and over-engineering.
What HN saysHN links it for its posts on leadership in tech; one commenter notes the author addresses unclear Jira epics and customer pain points in another post.
56HN people shared it
3linked it in comments
194stories submitted
1.2Kstory points
3 months agolast shared
2012people per year2026
Most-shared posts
- 1Most of What We Call Progress5 people · 42 points · first shared 2025 · 1 comments on HN
- 2The Mirror Is Part of the Machine4 people · 33 points · first shared 2026 · discussion on HN
- 3Good APIs Age Slowly – Yusuf Aytas4 people · 30 points · first shared 2026 · 1 comments on HN
- 4Incentives Drive Everything4 people · 19 points · first shared 2026 · discussion on HN
- 5Stop Wasting Brain Power3 people · 30 points · first shared 2025 · 1 comments on HN
- 6Why Over-Engineering Happens3 people · 26 points · first shared 2025 · 1 comments on HN
- 7Managers Have Been Vibe Coding All Along3 people · 25 points · first shared 2025 · 1 comments on HN
- 8Trial by Fire3 people · 23 points · first shared 2026 · discussion on HN
- 9What Good Execution Looks Like3 people · 16 points · first shared 2025 · discussion on HN
- 10What's wrong with Agile Frameworks (2019)3 people · 12 points · first shared 2019 · discussion on HN
- 11Capacity Is the Roadmap3 people · 11 points · first shared 2026 · discussion on HN
- 12Message Brokers Are Modern Grids(2020)3 people · 7 points · first shared 2026 · discussion on HN
- 13Why We Ignore Advice2 people · 27 points · first shared 2026 · 1 comments on HN
- 14Reflecting on Software Engineering Handbook2 people · 24 points · first shared 2025 · 1 comments on HN
- 15When Too Many Maps Overlap on One Person2 people · 22 points · first shared 2026 · discussion on HN
What HN people wrote when they linked it
yusufaytas · 2026-01-14
https://yusufaytas.com
on leadership in tech and software development
Pr0ject217 · 2022-02-07
EDIT:
Paste this hacky snippet into your browser's console to save all of the links into your clipboard:
(() =>
{
let result = [...document.querySelectorAll('td a')]
.map((link) =>
link &&
!link.href.includes('ycombinator') &&
!link.href.includes('javascript:void')
? link.href
: ''
)
.filter(Boolean);
result = [...new Set(result)];
result.sort();
copy(result.join('\n\n'));
})();
Just to help, here's a compiled-list of all of the links shared here so…
subhobroto · 2026-04-05
> One point I didn't see on there is lack of clarity of the objective of the JIRA Epics and Stories and verify that those underlie actual customer painpoints.
Interestingly, the author addresses this in a different post: https://yusufaytas.com/what-good-execution-looks-like/
I quote:
> Clarity of Direction
> If people don’t know where they’re going, they create their own destinations. It’s as simple as that. That’s when you get alignment issues, rework, and endless questions
> ... You can start simple. Here’s what matters. Here’s what doesn’t. Here’s where we are going. Here’s why. When you miss these, inevitably, your execution cripples down.