Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kenrose
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
kenrose
5y ago
As a founder, you have to get comfortable with doing sales. It’s how you get, you know, money and revenue. But you don’t have to be an “incredible” salesperson. Be able to explain the value prop of your product. Know your customer and know
62.
▲
by
kenrose
5y ago
I did it at 37 with two kids. As others have pointed out, the key is focus. You have a family and they demand / deserve some amount of your time. So make that time. Prioritize it. There will always be more to do in your company than yo
63.
▲
by
kenrose
5y ago
I agree. Something about imitation and flattery. :) Having a service catalog is a best practice for eng teams. No surprise to see Atlassian enter the ring here. I'm obviously biased, but I think if you're running more than 10 thi
64.
▲
by
kenrose
5y ago
Cries in GraphQL (where you generally POST, even for queries).
65.
▲
by
kenrose
5y ago
I made this jump in 2019. To some of the points made here: 1. You need to understand why you want to do a startup. "Building something of my own...": why do you want to do that? Why is that important to you? 2. Find a problem (m
66.
▲
by
kenrose
5y ago
tl;dr: when you leave a company, you generally have a 90 day expiry on your options. If you exercise, in some jurisdictions (like the US), you also have a tax burden. Some more forward thinking companies (including mine) offer 10 year expir
67.
▲
by
kenrose
5y ago
Two hard problems solved: 1. Cache invalidation 2. Decent project name Joking aside, this is great. Traditional CDNs + GraphQL always felt like an impedance mismatch.
68.
▲
by
kenrose
5y ago
> but seems basically the same if not quite as polished. That describes many of GitLab's features.
69.
▲
by
kenrose
5y ago
Thanks Roman. Founder of OpsLevel here ( https://www.opslevel.com ). A lot of companies build their own internal microservice tracking tools. Not just for release/deployments, but also for tracking service owners and product
70.
▲
Validating Kubernetes Best Practices
(opslevel.com)
1 points
by
kenrose
5y ago
|
0 comments
71.
▲
Stripe Webhooks / Emails are delayed
(twitter.com)
2 points
by
kenrose
5y ago
|
1 comments
72.
▲
by
kenrose
6y ago
Previous submissions over the last few days: https://news.ycombinator.com/from?site=twitter.com/ryancdoto...
73.
▲
It turns out you can put terminal escape sequences in the Git commit email field
(twitter.com)
15 points
by
kenrose
6y ago
|
1 comments
74.
▲
by
kenrose
6y ago
How much time was given in this instance?
75.
▲
by
kenrose
6y ago
Similar questions from last time there was a Webhooks as a Service on HN [1] 1. How do you deal with endpoints that are down or 500'ing? What kind of retry policy or backoff occurs? Related, how do you notify clients when their endpoin
76.
▲
by
kenrose
6y ago
My own experience ([1]): the biggest different between "startup inside BigCo" and an actual startup is availability of resources. "Startup inside BigCo" generally revolves around spinning up a new team that's produc
77.
▲
by
kenrose
6y ago
Congrats on the launch Feroot folks! - an old 111 neighbour
78.
▲
by
kenrose
6y ago
More on Carta from last year: https://www.nytimes.com/2020/08/30/business/carta-workers-in...
79.
▲
by
kenrose
6y ago
Also, you have a dead link to: https://gowebhooks.github.io/learning-lab/tailwind-starter-k... when I click on your logo.
80.
▲
by
kenrose
6y ago
Hey there, in a previous life, I led the team that built the "new" webhook delivery system at Shopify (now 2+ years old). A few notes / questions: 1. How do you deal with endpoints that are down or 500'ing? I saw "S
81.
▲
by
kenrose
6y ago
I'm probably piling on, but wanted to echo a lot of what's been said. On-call responsibilities are supposed to be a two way street between an employee and an employer. Employers expect employees to be on-call and handle production
82.
▲
by
kenrose
6y ago
Call me old fashioned, but I remember using stow in 2003/2004, about a year before git existed. Yes though, use a repo for sync, but stow takes care of at linking your dot files in the right place.
83.
▲
Ross Intelligence is shutting down after lawsuit from Thomson Reuters
(blog.rossintelligence.com)
111 points
by
kenrose
6y ago
|
45 comments
84.
▲
How to organize your early-stage SaaS marketing organization
(mkt1.substack.com)
2 points
by
kenrose
6y ago
|
0 comments
85.
▲
The Macro Problem with Microservices
(stackoverflow.blog)
1 points
by
kenrose
6y ago
|
0 comments
86.
▲
by
kenrose
6y ago
Your description sounds like the definition of financing. Yes, with financing there’s a trade off. In exchange for paying interest, you have the item that much sooner. Slightly tongue-in-cheek, but this is missing in your before example: A
87.
▲
by
kenrose
6y ago
Here’s how I’ve typically structured deals I’ve done. 1. Use a SAFE. It’s simple (literally what the S stands for) and defers granting the actual equity until the company is further along and has some kind of major event. 2. Agree on a disc
88.
▲
by
kenrose
6y ago
Two things come to mind. 1. At the end of the day, investors are people too. They may care that the team ends up whole. 2. 800k is non-trivial money, but it’s a small percentage of, say, a $100MM VC seed fund. The economics of VC are that s
89.
▲
by
kenrose
6y ago
“it’s strange how legal fees are just under the cap or way over the cap with copious discounts, but we never see legal fees significantly under.” Correct. My own experience: whatever value you negotiate the legal cap on your term sheet, tha
90.
▲
by
kenrose
6y ago
Calling yourself the first two is fine. Calling yourself the third without paying a bunch of money will get you a C&D from your local professional engineering body.
More ›