gvinter

Joined 13 years ago

Karma
57
Submissions
21
Member since
Sep 19
product, logrocket

previously: engineer / product, wistia founder, projectpulse.io / clientflow.com

[ my public key: https://keybase.io/gvinter; my proof: https://keybase.io/gvinter/sigs/63fgWE7LORQ0xW-PGiziwa2ZRuxPchzdCMHZBlCU_wM ]

View on Hacker News

Recent submissions

Comment · 4 years ago
How quickly is the data accessible? Are sessions viewable realtime?
Comment · 5 years ago
Yes! Readerly (readerly.com) delivers on what Goodreads doesn't - it doesn't rely on the 5-star rating system and learns what you like to give you better recommendations. This means it's a social network that improves for users as it grows, it doesn't weaken as Goodreads does.
Comment · 7 years ago
I've really enjoyed watching Rik build this library. Congrats, Rik!
Comment · 11 years ago
Yes, and although I won't say to always trust that "feeling you get".. there is a feeling that you get when you organically come to that realization and it's very different from sitting in a brainstorming session and thinking of 20 ideas in a row. Can't replace first-hand experience in a space.
Comment · 11 years ago
Plenty of projects just need to be built to test. My apps would never be built and then rev'd if they were built to be "rock solid" in their first iteration. It's important to have frameworks that get apps off the ground quicker.
Comment · 11 years ago
Start with a really good spec. I started ProjectPulse.io by clearly defining the problem, and what the solution would look like. Then I dove into defining the needs of all the MVP features. From there, it wasn't hard for me to make wireframes and get awesome designs from a designer. Then, I also made a list of features I'm going to want to add, but not for the MVP, so they felt like they were on paper, but not the same as MVP features.

Once you have a list down of things that need to be built because you know the sum of those things is an MVP, put your head down and work until it's done. Don't question anything until you have an MVP. Stop second guessing the product or the market and just build it.

I'm leaving out the whole "research and learn from potential users" - that comes first, but that's not what we're talking about here.

TL;DR: Write a detailed spec for an MVP, then put your head down in code until you have an MVP.

Comment · 11 years ago
Maybe, but this isn't the issue at hand. The issue is that it's easy for employers to take advantage of employees. Just because you're in a startup doesn't mean you MUST be taken advantage of since that's the cross to bear for engineers. That's not sustainable and it's a bummer so many people in the industry think that being abused is the only way to make it to the end zone.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton