Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ironchef
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
ironchef
8y ago
Name and email are usually considered PII in most of the compliance world, no?
62.
▲
by
ironchef
8y ago
what I inferred from the other post was that governments are complex... and each government has some things they do well.. and some things they do poorly (not necessarily just re: asset forfeiture). For example one could argue that the US
63.
▲
by
ironchef
8y ago
"If you want to avoid challenges in life and just get a job so you can retire 50 years later with nothing remarkable in between, that strategy works." I find this to be hyperbolic. Compliance and presenting yourself as having mor
64.
▲
by
ironchef
8y ago
"Maintenance of other peoples code is usually more difficult than understanding what you wrote yourself." This is true. Often the types of things that folks look for though are nuances and style that come through with what someon
65.
▲
by
ironchef
10y ago
I know one nice thing was last I knew they were like ... half female executives. So they would appear to be doing better on diversity issues than most of the valley. Anecdata I know...
66.
▲
by
ironchef
10y ago
Not having pricing on your page (or .. having the "up to 10 users -> free", "more than 10-> call us") is a non-starter imo. I need some idea of pricing before I spend any time looking. $10/user/year? $
67.
▲
by
ironchef
10y ago
tldr: 83b isn't just for RSUs. You _may_ be able to perform an early exercise on ISOs and perform an 83(b) election at the same time. I've done that twice now .. the first time worked out very well. The second time I'd anti
68.
▲
by
ironchef
10y ago
"few people with _serious_ technical chops want to play on Facebook's side of the garden wall" I fear you suffer from some form of bias. Or maybe I do; however, I know some folks there who, in the devops or data engineering
69.
▲
by
ironchef
10y ago
"Five years is not enough time to think about how we should make any money in a way congruent with our founding values? That just doesn’t compute." Sure it does. "they sweat the details like nobody else" It sounds to me
70.
▲
by
ironchef
10y ago
No offense but you're wasting time. It doesn't matter if it's PDF vs doc vs whatever. You _need_ to offer something very compelling (not the brochures / leave-behinds.. the service). You (usually) either need to take a
71.
▲
by
ironchef
10y ago
Normally it's based on (roughly) multiples of revenue, future earnings, etc. Their revenue this year was estimated to be like 370 million. Let's compare that to recent IPO darling Nutanix. Nutanix had revenue of approximately $2
72.
▲
by
ironchef
10y ago
I see tons of them. If you're interested in ML, you're probably more looking towards data science. Data engineering (in general) is more about getting the data in a state where it can be used (extracted, cleaned, moved, transfor
73.
▲
by
ironchef
10y ago
One thing we've done in the past is included the feed name / source in the document (just an fyi...not sure if applicable to your use case or not).
74.
▲
by
ironchef
10y ago
I think this can be true in some cases; however, it's also nice to look for things like: * Does this person think they're above grunt work / taking out the trash? * Does this person work better in a position where they take o
75.
▲
by
ironchef
10y ago
The only original IRR which was semi-published was the first fund (300 mil). If I recall it was a 200 ish % because of Nicira, Skype, Instagram, and FusionIO. You can get somewhat of an idea of the IPOs and acquisitions here: https:/
76.
▲
by
ironchef
10y ago
The main issue isn't the gmail or what not has been breached. It's that lots of users tend to reuse passwords. So...once they know you signed up using foo@gmail.com to service Alpha (and they have that password)..then they start
77.
▲
by
ironchef
11y ago
"You can't stare at somebody's code and know if you'll like working with them." Sure...and there's not mutual exclusion between the two. Looking at someone's work product is simply another set of data po
78.
▲
by
ironchef
11y ago
"Why not just bypass the bullshit challenges and just _have a conversation about code_?" Because talking and doing can be different? _Do_ they actually write test cases? Do they write documentation? Do they make output machine
79.
▲
by
ironchef
11y ago
Ok. I guess the difference is I would never suggest RBAC to be "relatively simple". There are so many considerations (are negative permissions required? are there many to many required? separation of duties?) that without maki
80.
▲
by
ironchef
11y ago
And you basically laid out a recipe for incurring technical debt. What's wrong with instead looking at some established best practices / suggestions and using those for guidance. What if they said they were looking to do this wit
81.
▲
by
ironchef
11y ago
Unfortunately (and as you know) the world is more complex than this and, in some cases, you will not meet legal requirements. Yes, what you suggested is _a_ best practice; however, I'd suggest some of the more "standard" dir
82.
▲
by
ironchef
11y ago
Gaius, Studies are mixed on the pros/cons of office vs remote. For example a Stanford study showed productivity increased 9 to 13% for remote office workers. Some have shown that collaboration can increase as well as communication wa
83.
▲
by
ironchef
11y ago
The first fund's were around 50% if I recall (as they included Skype and Nicira which were both _great_ returns).
84.
▲
by
ironchef
11y ago
Part of the thought was to also reduce transport cost. So if you have effectively the harvest and distribution localized one would reduce footprint in other ways. That being said I'm not saying "expensive urban rooftops" are
85.
▲
by
ironchef
11y ago
From what I recall reading some of the newer indoor hydro systems (plus LED) were getting greater than 20x increases (I think the lettuce/basil warehouse in Japan was getting over 60 heads of lettuce per square foot in comparison to tr
86.
▲
by
ironchef
11y ago
I'm sorry. I didn't mean to imply employee 500. Employee #10, for example or even employee #50 could still do substantially well (similar to what you allude to in saying "the number in which employee 3 gets rich is higher&q
87.
▲
by
ironchef
11y ago
"92% of startups fail. For most, it's not going to turn out pretty." And if you're a founder you have those same odds, no? With more skin in the game, being a founder in those cases is probably even worse, too. I think
88.
▲
by
ironchef
11y ago
"you're not going to get rich by being an employee" I disagree. If you're looking at every little startup idea, then yes...you probably won't get rich. Also, you won't get as rich as the founders; however, I
89.
▲
by
ironchef
11y ago
@ryanmickle: Same. I'll PM you the main person I've worked with in the past. I've worked with her for basically 15 years. She's probably pretty familiar with Barry; however, I don't generally want to share her wi
90.
▲
by
ironchef
11y ago
"I am not saying the numbers you provide are inaccurate, but they reflect the data of a special interest group who is trying to raise money." - That's a fair criticism; however, like any other data, trying to find "true&
More ›