gojkoa

5 ms·

31.
Why "Yes" Is Overrated(votito.com)
3 points by gojkoa 3mo ago|1 comments
32.
by gojkoa 3mo ago
For a SaaS we launched about 7 years ago, the initial people came from LinkedIn, so my suggestion would be to look for people on linkedin that fit your target profile and ask them for a bit of time to discuss their workflow/issues and
33.
The Value of Understanding Code(ian-cooper.writeas.com)
2 points by gojkoa 3mo ago|0 comments
34.
by gojkoa 3mo ago
ultimately product success metrics such as market share and revenue, but those are lagging and might not be measurable over a 4 month period (the original study duration). beyond that, behaviour changes for users (is the product more useful
35.
by gojkoa 3mo ago
PRs measure effort, not outcome, so it’s a measure that their developers+ai spent 24% more effort than just devs previously (assuming the average work that went into a PR didn’t change, which is also a big assumption. maybe those PRs were s
36.
by gojkoa 3mo ago
A big shift over the last year or two seems to be market access for small/indie products. I built and launched two SaaS systems (one started 13 years ago, one 7 years ago) sucessfully getting customers through organic search from Googl
37.
by gojkoa 3mo ago
The study unfortunately looks only at individual productivity, not any org gains, and the big claim in the PDF is that adopters "merge roughly 24% more pull requests" over a four month period. not exactly headline-making material.
38.
by gojkoa 3mo ago
(using claude code) I force the agent to work in steps where each step changes no more than 4-5 files, where each step has some observable result, ideally unit testable or e2e integration testable, and do a quick git diff/git add after
39.
by gojkoa 3mo ago
0. product developer/consultant 1. macbook pro, generally maxed out spec at time of purchase 2. 5-6 years
40.
by gojkoa 3mo ago
combining idea banks/feature request boards with popular product management surveys, with the idea to help people discover better signals from the noise of user feedback, and then follow up with interested users for in-depth research.