Martin Gogov

CPO @ LogicStar AI. ex CTO | AI Enthusiast | Entrepreneur, caffeine addict.

[Martin Gogov @mgogov]

Dashboards aren't dead.

They're sliding into the legacy slot, somewhere next to Jira and weekly status emails.

The vendors who spend the next two years polishing "open the dashboard" as the happy path will wake up in 2028 wondering where the buyers went.

[Martin Gogov @mgogov]

If your dev tool only ships a dashboard in 2026, you're building for the wrong decade.

10 of the last 50 CTOs and engineers I spoke to said the same thing without me prompting them.

Don't give me a UI. Give me a CLI.

[Martin Gogov @mgogov]

This is the quiet power shift most aren't pricing in.

When the primary IDE is a terminal driving an LLM, every adjacent dev tool either ships a CLI and an MCP server, or it quietly stops being adjacent.

[Arsenal @Arsenal]

The Arsenal. Your Premier League champions.

[Martin Gogov @mgogov]

Smart move. Premium subscriber for ages. The new logo is really bad, so great to revert it 👍 We all make mistakes, kudos for recognizing and owning this one.

[Spotify @Spotify]

@PopCrave Alright, we know glitter is not for everyone. Our temp glow up ends soon. Your regularly scheduled Spotify icon returns next week.

[Martin Gogov @mgogov]

Do you have a superhuman engineer on the team? What happens when they take a week off 😜?

[Martin Gogov @mgogov]

Every team has one.

The superhuman engineer who notices when something's wrong before customers do. They don't scale.

That's not a compliment. It's a single point of failure with a great reputation.

[Martin Gogov @mgogov]

They watch a channel, notice patterns, connect the signals, know which errors actually matter.

That's diligence. Diligence is replicable. The judgement about what to do next is the hard part.

Automate the diligence. Keep the judgement.

[Martin Gogov @mgogov]

The AI tooling market spent a year building autonomous coders. Meanwhile, the bug resolution constraint moved upstream. It's not throughput. It's judgement 🧠

Where does your team's triage workflow break for you?

[Martin Gogov @mgogov]

I spoke to 12 engineering leaders last month about handling software bugs. None one of them said the actual fixing of the bugs was their main problem.

Everyone was like: I have more findings than I can read, more PRs than I can review, more alerts than I can investigate 🤯 .

[Martin Gogov @mgogov]

An enterprise software scanning product vendor says his tool finds 2 million issues. Half a million are red. He asked me, on a call: so my customer now asks me what the heck do we do with all these now?

[Martin Gogov @mgogov]

Severity is a developer's measure of pain. It says nothing about whose pain.

The silent majority don't tell you anything is wrong. They just churn at the next renewal.

How is your team ranking bugs?

[Martin Gogov @mgogov]

80% of your customers were impacted. Only 5% raised their hand.

A real number from a real engineering manager I talked to this quarter.

Most teams triage bugs by severity. Mature teams rank by customer tier and ARR at risk.

[Martin Gogov @mgogov]

The most innovative teams have moved on.

They sync HubSpot into Linear. They tag bugs by customer tier and ARR at risk.

They fix the bug touching their renewal pipeline first, even if its severity is medium.

[Martin Gogov @mgogov]

Most engineering teams triage bugs by severity. P0, P1, CVSS scores.

[Pavel Ivanov @ivanovpavel]

Had a chance to spent the weekend playing with Cursor's SDK ... was so fun! The result?

💻 cursor-cli - Streaming, sessions, model picker etc.

Thanks @cursor_ai and @ericzakariasson 🙏

https://t.co/5TlQo16qcj