Wow thanks very much for sharing the numbers. I've also found this mechanism supremely useful for little internal buses or services.
1,242 karma · joined November 4, 2013
At Arctype, we're building the best collaborative SQL client for PostgreSQL and MySQL. We are backed by Social Capital and Chamath Palihapitiya, and other great angels.
Arctype is looking for a software engineer interested in building a truly great SQL client. We're a team of engineers who have worked at cutting-edge startups and enterprises. After struggling with terrible query interfaces at every job, we set out to build a best-in-class SQL client with built-in collaboration, version history, sharing, and more!
As a software engineer at Arctype you will work on every part of the product, from the database connectors to our visualization tools, to our SQL language parsers. You'll get to chat with users every week and see your changes go live and have an impact. Feature suggestions and product breakthroughs come from everywhere. At Arctype, if you can dream it you can build it (as long as users love it!). Compensation for this role includes a competitive salary, equity befitting an early-stage employee, and benefits.
Required Skills: Javascript, React, Node, Git, SQL
Nice to Have: Cool projects, Figma, CSS
Email: jobs@arctype.com
At visitorX we're building a fairly large bank of comments and a tagging system and Humanloop looks really great for that.
The second guy more or less taught me how to use Vim. And not just use it, but move buffers around and navigate the filesystem so fast that it seemed he was wired directly into the computer. Up to that point I had not worked with a very very experienced programmer who was still practicing. He would write very complex regexes directly in the vim prompt to find the right parts of log files.
The overall team had been acquired by HP 18 months before I arrived and you could tell that people were beginning to move along. However many of the folks there had worked with Stonebreaker at MIT and then at C store. There was a feeling that they all knew things about column store databases that were not widely known. In particular the engineering manager once walked us through the very first project he implemented at Vertica, which was backup and restore. He more or less derived the whole system from a few principles of when data should be saved over the course of 2 hours.
It was an extremely technical place to work with data sizes and problems I had never encountered. It gave me a sense of the the sheer scale that some companies operated at and what was possible by starting with C++ and building the system out bit by bit over years. Many of the approaches there actually mirrored architecture work I did later on a multi-camera tracking system.
I actually laughed. What kinds of applications do people think IS&T is building? Supply chain management, HR, support software (Apple forums anyone?)... I don't see how Apple sticking its core engineering resources or at all innovating within IS&T helps their business.
Steve was the one that coined the 10X rule, or popularized it. That idea must still hold within Apple's executive ranks. I guarantee Apple's top engineers never interface with IS&T and their time won't be saved by improving it. In fact I would bet that managing the deliverable of one of IS&T's projects is a sign that you're not one of the golden ones.
That said, I obviously think these contractors should be treated much better and overworking people for low pay is never okay. Maybe Apple could use some smaller dev shops that treat their people better.
The other issue is that a "great business" and "scale" are not synonymous. In fact many of the current batch of companies of great scale, like Slack, have spent enormous amounts of money to get there, and still lose money after becoming public. Then you have a company like Atlassian, with a confounding mix of enterprise products that are hard to use: but a fantastic businesses that's been profitable since the very beginning.
I do agree with you that the APIs, webhooks, and Zapier integrations solve the problem of customization, although I'd still say it's less customization and more a bevy of options.