Hacker News: yusufaytas

Breaking Up with WordPress After Two Decades

yusufaytas — Thu, 16 Apr 2026 09:53:19 +0000

Article URL: https://yusufaytas.com/breaking-up-with-wordpress-after-two-decades

Comments URL: https://news.ycombinator.com/item?id=47790885

Points: 12

# Comments: 0

New comment by yusufaytas in "Ask HN: What Are You Working On? (April 2026)"

yusufaytas — Sun, 12 Apr 2026 20:49:08 +0000

I’ve started moving off WordPress to Yapress. It’s a Git-managed static setup with a migration script, though I haven’t run the full migration yet. Right now, I’m testing the setup and validating the workflow.

The trade-off seems reasonable so far. By going static, the main thing I lose is comments.

The project is still in progress, but I made solid progress over the weekend.

The project is here: https://github.com/yusufaytas/yapress

Work Introduces You

yusufaytas — Thu, 09 Apr 2026 14:07:42 +0000

Article URL: https://yusufaytas.com/your-work-introduces-you/

Comments URL: https://news.ycombinator.com/item?id=47703982

Points: 11

# Comments: 0

Trial by Fire

yusufaytas — Thu, 02 Apr 2026 13:44:30 +0000

Article URL: https://yusufaytas.com/trial-by-fire/

Comments URL: https://news.ycombinator.com/item?id=47614397

Points: 11

# Comments: 0

The Dude

yusufaytas — Sun, 22 Mar 2026 12:46:58 +0000

Article URL: https://yusufaytas.com/the-dude/

Comments URL: https://news.ycombinator.com/item?id=47476959

Points: 34

# Comments: 4

Why Headcount Math Lies

yusufaytas — Thu, 19 Mar 2026 20:44:53 +0000

Article URL: https://yusufaytas.com/why-headcount-math-lies/

Comments URL: https://news.ycombinator.com/item?id=47445803

Points: 7

# Comments: 0

Capacity Is the Roadmap

yusufaytas — Mon, 16 Mar 2026 09:54:38 +0000

Article URL: https://yusufaytas.com/capacity-is-the-roadmap/

Comments URL: https://news.ycombinator.com/item?id=47397001

Points: 12

# Comments: 0

Show HN: OpsOrch – a unified API for incidents, logs, metrics, and runbooks

yusufaytas — Sun, 15 Mar 2026 12:57:05 +0000

Hi HN,

I built OpsOrch because operational work is spread across too many tools.

Incidents might be in PagerDuty, logs in Datadog, metrics in Prometheus, and runbooks somewhere else. Each system has its own API and data model, so cross-tool workflows usually turn into glue code.

OpsOrch is my attempt to standardize that.

It defines a common schema for things like incidents, logs, metrics, alerts, services, and runbooks, then uses adapters to connect different providers behind one interface.

The goal is simple: instead of writing vendor-specific logic, a client can ask for:

- incidents affecting a service

- related logs and metrics

- associated runbook context

I am especially interested in feedback on whether this abstraction is actually useful, or whether it becomes too generic in practice.

Happy to answer questions about the schema, adapter model, and tradeoffs.

Comments URL: https://news.ycombinator.com/item?id=47386975

Points: 3

# Comments: 0