ankrgyl

10 ms·

61.
by ankrgyl 5y ago
The question wasn't administered with the "script" laid out in the blog post. I understand why if you were just reading that, you might get confused. In practice, we had a script that walked the candidate through how to use t
62.
by ankrgyl 5y ago
tl;dr False positives: we hired a few folks who could prototype changes but struggled to ship them. This question wasn't solely to blame for it, but it wasn't enough of a signal on someone's ability to _thoroughly_ work withi
63.
by ankrgyl 5y ago
You hit the nail on the head. We explicitly did not care about how "well" the solution was written (some solutions were very surgical, others involved a lot of copy/pasta, some folks wrote very detailed comments, etc.), altho
64.
by ankrgyl 5y ago
At the time I developed the question, I was employed by MemSQL as a full time software engineer. Eventually, I became the VP Eng. I spent 5.5 years there. It was an incredible experience.
65.
by ankrgyl 5y ago
We gave candidates a heads up before the interview that they'd be working on a live coding question, and that they should familiarize themselves with editing code over SSH. Some candidates felt uncomfortable with this, and we were able
66.
by ankrgyl 5y ago
I'm not sure where the three hour thing is coming from. During my tenure, we gave candidates one hour.
67.
by ankrgyl 5y ago
We experimented quite a bit. Since it was relatively inexpensive to administer (almost anyone could ramp up to conducting it), we were able to test it in a variety of scenarios (even for intern candidates). It ended up being _after_ the ini
68.
by ankrgyl 5y ago
That's a great point! We didn't actually think of this question as much of a "measure" (and I think the blog post alludes to this as well with a "Fizz Buzz" analogy). We thought of it more like a filter — if yo
69.
by ankrgyl 5y ago
Author of the interview question here. I came up with the idea after working at the company for a couple months and realizing that the skill of "diving into an unfamiliar area of the code and quickly figuring it out" was very impo
70.
by ankrgyl 5y ago
I think you recognize this already, but to add a bit of color, in highly regulated industries (e.g. financial services) and B2B settings with lots of peers (e.g. supply chain), "going back to the source document or database or whatever
71.
by ankrgyl 5y ago
I'll just throw my hat in the ring and mention that at Impira, we are one of those startups wholly dedicated to (4). We happen to use Google's OCR engine (1) under the hood (for raw OCR), and what you said resonates for sure: ther
72.
by ankrgyl 5y ago
If you're looking for something that's robust and easy to setup but a bit more expensive than Textract, check out https://www.impira.com/ (Disclaimer: I am the founder/CEO there).
73.
by ankrgyl 6y ago
I’m the founder of a company called Impira ( https://www.impira.com/ ) which specifically solves this problem. We don’t scan the documents for you, but we do solve the other steps you mentioned. Feel free to sign up on our we
74.
by ankrgyl 7y ago
Pilot is amazing! They have delivered on exactly your quote for us, except that I do often think about how helpful they are :-).
75.
by ankrgyl 8y ago
Fair enough, the "classic serverless" vs "neo-serverless" distinction directly addresses my point. I have added this clarification in my original point.
76.
by ankrgyl 8y ago
Huh? It's literally in the "Serverless Database Engine" section. I can update the quote to include the header.
77.
by ankrgyl 8y ago
This is a good example of someone twisting the term "serverless" to capture attention: > Serverless Database Engine > Most NoSQL database engines (i.e. MongoDB, Redis, CouchDB) are implemented as a separate server process
78.
by ankrgyl 8y ago
I may be missing something... but how is that clearer than for item in report(): for event in item['events']: if event in events_we_care_about: act_upon(event) break
79.
by ankrgyl 9y ago
MSSQL has been compiling plans to bytecode, but not in a manner which can be directly or JIT compiled to machine code. There is a big difference in compilation & runtime performance with an LLVM-based approach, which can be directly or
80.
by ankrgyl 9y ago
> I wonder if AWS will incorporate these improvements into Redshift, which is Postgres forked for OLAP use cases where this is far more prevalent. In the past, they haven't done a great job at this (ran into a float bug fixed upstre
81.
by ankrgyl 9y ago
You're right, but I don't think the use case you mentioned (as a competitor to B+ trees for direct lookups) is the target use case for a hash index. A hash index can be a big win for nested loop joins, especially at high concurren
82.
by ankrgyl 10y ago
> The problem with standard'ish SQL+RDBMS and their schemas is that types are not enforced well in SQL and most libraries and language integrations, thus we end up with the quagmire of static schemas that can not be reliably type ch
83.
by ankrgyl 10y ago
You can flip this argument and make a similar point: "What's wrong with using something like Postgres LISTEN? I don't get the obsession of redis pubsub, or implementing this kind of thing outside the database. I suppose its a
84.
5 Years(blog.ankurgoyal.com)
4 points by ankrgyl 10y ago|0 comments
85.
by ankrgyl 10y ago
> That's a silly explanation. A smart JIT would be able to take successive Python opcodes and optimise them together as one operation, so how much time it spends interpreting individual instructions has nothing to do with the "
86.
by ankrgyl 10y ago
This article is a follow up to an earlier post ( https://blog.pyston.org/2016/06/30/baseline-jit-and-inline-c... ) which provides additional context. In short, python opcodes are inefficient because they must s
87.
by ankrgyl 11y ago
If you are referring to indices on expressions, MemSQL definitely supports them. In MemSQL you do it by creating a computed column ( http://docs.memsql.com/v5.0/docs/persistent-computed-columns ) and creating an ind
88.
Investigating Linux Performance with Off-CPU Flame Graphs(blog.memsql.com)
22 points by ankrgyl 11y ago|0 comments
89.
How MemSQL is helping push streaming data forward(techrepublic.com)
2 points by ankrgyl 11y ago|0 comments
90.
Show HN: Build Real-Time Data Pipelines with Spark Streamliner(blog.memsql.com)
20 points by ankrgyl 11y ago|0 comments

More ›