Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kevinmobrien
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
kevinmobrien
6y ago
As a CEO, this sounds like an incredibly broken company model. It’s obviously working in a lot of ways, but why would you make it so hard to get things done once you’re at scale?
2.
▲
by
kevinmobrien
6y ago
I switched to a self-hosted (on AWS) inspircd instance with The Lounge running in front of it for friends earlier this year. It’s nice. The biggest issue was getting a native-like experience on iOS and Android phones, and discovering that s
3.
▲
by
kevinmobrien
6y ago
This is a very close-minded view. Professionals with psychological and/or therapeutic training can offer insights that you don’t have. Would you refuse to work with a trainer if you were trying to improve at a physical activity? Would
4.
▲
by
kevinmobrien
7y ago
This is pretty darned cool. Really strong example of how to walk through a set of slides exploring why to build a new form library, too.
5.
▲
by
kevinmobrien
9y ago
Interviewing is subjective. It’s about sitting down in a specific context and extrapolating, based on incomplete information, about a future set of conditions that will likely change when time catches up to them. If we can start with the id
6.
▲
by
kevinmobrien
9y ago
Adding on the personal note side: I am the CEO and co-founder of GreatHorn. Happy to chat 1:1 if anyone's interested in learning more, either about the company or the role - or help find any answers I can't provide directly.
7.
▲
by
kevinmobrien
11y ago
Went through Techstars with this team; their mail plugin alone saved us countless hours on answering common questions with keystroke-driven responses. Excited to see what they're working on!
8.
▲
by
kevinmobrien
11y ago
GreatHorn ( http://www.greathorn.com ) • ONSITE (Boston, MA + New York City, NY) • Software Engineer • Full time GreatHorn (Techstars '15) is a new kind of cybersecurity platform that secures cloud-based communication systems
9.
▲
by
kevinmobrien
11y ago
Agreed.
10.
▲
by
kevinmobrien
11y ago
Amen here, as well. I've spent the last 17 years working for (and now running) tech startups in Boston; the worst of them ceded all fun to cube farms, but the best of them never went all-in on the culture described here. Perhaps there
11.
▲
by
kevinmobrien
11y ago
With tremendous respect to Linus, this isn't a fair characterization of the "security community", whatever that means. There are both practitioners and vendors who take the view that security should enable business, not block
12.
▲
by
kevinmobrien
11y ago
Very excited to see this - I had a chance to see their early product, and was impressed by its flexibility and their approach to making it secure.
13.
▲
by
kevinmobrien
11y ago
The "traditional" answer is to identify the VCs you're interested in, and network your way into an introduction if you don't know them yourself. Accelerator programs can also be a way to become involved. Have a clear, cl
14.
▲
by
kevinmobrien
11y ago
Agreed on all points, and thanks for weighing in from the VC side of the table. For clarity's sake, I've sat on tremendously effective boards at the companies I have either run or had a senior role at, and I think there's inc
15.
▲
by
kevinmobrien
11y ago
One of the frustrating things about early-stage in my experience is that there is little correlation between VC and market interest; our experience (also cybersecurity) has been that we're generating a significant amount of interest fr
16.
▲
by
kevinmobrien
11y ago
Agreed on this. My CTO and co-founder is a friend from highschool (~18 years ago, at this point); we've weathered being teenagers together, and stayed closed through the trials of young adulthood, kids, marriages, and mortgages. It doe
17.
▲
by
kevinmobrien
12y ago
We're using a combined data pool from multiple companies (i.e., customers) to predict security breaches before they occur, and provide a usable set of notifications rather than the long list of "possible alerts" that so many
18.
▲
by
kevinmobrien
12y ago
>> "API keys [...] need to be in your committed code" > No they don't. A better approach is what the rest of the comments here are suggesting: (1) store your secrets (API keys, certs, credentials, whatever) in a high