News for hackers. Stuff that matters.

kevinpfab

Re:Ask HN: Who is hiring? (January 2020) on Thursday January 02, 2020 @11:53AM (#21937009)
Omnivore | Full Time | REMOTE or ONSITE (Tampa, FL) | USA or Canada

Omnivore is a universal API for restaurant point-of-sales. Our API integrates hundreds of apps directly into the brains of the restaurant, without the app developers having to worry about the fragmented POS industry. Our recently launched menu management product makes it easy for restaurants to create their perfect (and integrated!) digital menu for delivery, online ordering, and more.

We're API obsessed. All of our products are served via carefully crafted REST APIs. All our forward technology is built in Go, and we have a substantial amount of Python and Javascript/Node.js running in our cloud and deployed into restaurants.

You should give us a look if these problems sound interesting to you:

  * Building a rapidly growing REST API in Go
  * Deploying, updating, and managing an on-prem agent deployed to 10,000+ restaurants
  * Creating an awesome developer ecosystem in an industry notorious for legacy technology
  * Reverse engineering systems built 20+ years ago, and making them easy to use via modern APIs
Omnivore is just over 50 people today, and was built as a remote-first company from day one. We're hiring:

  * Full Stack / Backend Engineers - help build product!
  * Senior Go/Golang Engineers - help support a rapidly evolving codebase!
  * Site Reliability Engineers - help scale our systems and monitoring!
Apply at https://jobs.omnivore.io or email me directly at kevin.pfab [at] omnivore.io.
Re:Ask HN: Who is hiring? (December 2019) on Tuesday December 03, 2019 @09:12AM (#21692350)
Omnivore | Full Time | REMOTE or ONSITE (Tampa, FL) | USA or Canada

Omnivore is a universal API for restaurant point-of-sales. Our API integrates hundreds of apps directly into the brains of the restaurant, without the app developers having to worry about the fragmented POS industry. Our recently launched menu management product makes it easy for restaurants to create their perfect (and integrated!) digital menu for delivery, online ordering, and more.

We're API obsessed. All of our products are served via carefully crafted REST APIs. All our forward technology is built in Go, and we have a substantial amount of Python and Javascript/Node.js running in our cloud and deployed into restaurants.

You should give us a look if these problems sound interesting to you:

  * Building a rapidly growing REST API in Go
  * Deploying, updating, and managing an on-prem agent deployed to 10,000+ restaurants
  * Creating an awesome developer ecosystem in an industry notorious for legacy technology
  * Reverse engineering systems built 20+ years ago, and making them easy to use via modern APIs
Omnivore is just over 50 people today, and was built as a remote-first company from day one.

We're hiring:

  * Full Stack / Backend Engineers - help build product!
  * Site Reliability Engineers - help scale our systems and monitoring!
Apply at https://jobs.omnivore.io or email me directly at kevin.pfab [at] omnivore.io.
I'm a founder of Emergent One, a startup that uses similar agent-based technology to Chartio to access production databases and build out RESTful APIs. Some of our APIs are write-enabled, which makes the proposed risk even higher than that of Chartio's.

We've spent a lot of time thinking about security risks and writing code to reduce them. I thought I'd share a few things we do and that we've learned from our experience:

* The agent approach is the most popular because it allows for a system administrator to easily sever the connection from the database server without having to worry about writing queries to revoke user access.

* We never run unindexed queries without an explicit request from a customer and a manual entry from an Emergent One employee.

* We're currently looking into security consultants to continuously test our production environment.

* We're building an appliance version of our software much like Github Enterprise in order to accommodate the customers that aren't comfortable with their data hitting the cloud.

* We strive to have very quick and personal customer service directly from engineers. The vast majority of the responses are within the hour.

and last but certainly not least...

* The very best thing we can do is be honest and straightforward about the inherent risk behind our platform. Being able to build and maintain a pristine level of trust is the only thing that will keep us in business.

I'm sure Chartio does things very similarly. Direct-database access technology is not for everyone, but it's also proving to be extremely valuable for both Chartio's customers and ours. The cloud advantage that makes most SaaS software great is still there.

Re:Announcing our pricing (including consulting rates) on Wednesday March 06, 2013 @04:20PM (#5334041)
Often times, particularly in enterprise software, part of the terms of a deal include a "source code escrow" clause. This means that if you go out of business, the customer with this term gets your platform's source code released to them so their investment into your technology doesn't implode completely.
The issue with web scraping is that it relies on the scraper to keep up with changes made to the site.

If a site owner changes the layout or implements a new feature, the programs depending on the scraper immediately fail. This is much less likely to happen when working with official APIs.

Re:List of Seed Accelerator Programs and their results on Thursday December 06, 2012 @10:03PM (#4885268)
Yes, the numbers for TechStars Cloud are accurate. If you're interested in learning more about the themed program, feel free to contact me and I'll answer any questions you have!

Source: I was a founder in TSC's first class.

Just chatted with Max over Skype. Had some great suggestions that I'm going to work on implementing right away - would have gladly paid a small consultation fee for the session.
Re:Show HN: Generate REST APIs for Existing Applications on Thursday November 01, 2012 @04:37PM (#4729567)
Apologies for this oversight - we'll fix it ASAP. In the mean time, here are the articles we were mentioned in:

TechCrunch: http://techcrunch.com/2012/04/11/techstars-debuts-11-cloud-s...

Gigaom: http://gigaom.com/cloud/apis-and-data-dominate-techstars-clo...

TNW: http://thenextweb.com/insider/2012/04/11/these-eleven-compan...

Re:Show HN: Generate REST APIs for Existing Applications on Thursday November 01, 2012 @04:01PM (#4729415)
We totally understand the hesitation there. We're launching with the hosted direct-connection form, but we have tons of plans to specifically address this concern.

First, we're actively working on a database agent (like chart.io using reverse-SSH tunneling) for increased security and control.

Second, we have longer term plans to offer this platform as an appliance, so everything stays within your infrastructure. That's obviously a much larger project.

In the mean time, we have the advantage of being able to make constant improvements to your API while being hosted.

Re:Show HN: Generate REST APIs for Existing Applications on Thursday November 01, 2012 @03:52PM (#4729378)
We definitely built the product with existing applications (without an API) in mind. We found it much more difficult to add an API after-the-fact than if you design for one in the beginning. In fact, the idea came to us after attempting to build an API for a 10 year old PHP application at Rackspace.
Re:Ask HN: Who Is Hiring? (November 2012) on Thursday November 01, 2012 @12:25PM (#4728310)
Emergent One - Remote (US) - Full Time

Emergent One automatically generates REST APIs for existing applications and databases. We're a new startup devoted to making APIs better and more prevalent. Although we're a small team, we are growing fast and moving even faster.

We are looking for a Software Engineer that is passionate about developer communities, REST, and of course, building and consuming APIs. The role will be a combination of development on our developer portal solution and our core tech behind generating APIs. You’ll be helping build the API that generates APIs. In fact, that API generated our own private API (so meta!). You'll have a huge impact on the company and customers as a very early member of the organization, and be introduced to a large range of cutting edge API providers.

http://www.emergentone.com/jobs/

===Responsibilities

* Lead development on a robust developer portal solution for APIs we provide

* Contribute to the core solution that generates APIs

* Gain a deep understanding of the Emergent One platform

* Help troubleshoot problems in our customer's API design

* Work closely with customers to design solid RESTful APIs

* Build up a resistance to mildly brain melting meta-ness

===Qualifications

* 3+ years experience as a Software Engineer / Developer

* Experience developing applications built on APIs

* Deep awareness of RESTful API design and HTTP standards

* Strong knowledge of object-oriented design and design patterns

* Experience on a remote team a plus

===About Emergent One

* Ruby on Rack core, js / backbone frontend

* Funded Seed Round, TechStars Cloud Alumni

* Remote organization - work wherever you want!

* Choose your own hours - we're results driven first!

* Regular (friendly) debates and gaming sessions

* Founded by 2 ex-Rackspace developers

Email us at [email protected]

Re:20 lines of code that beat A/B testing every time on Tuesday May 29, 2012 @06:29PM (#4040330)
Conductrics as well: http://conductrics.com
Re:Show HN: Signal Box, the API to your web apps on Tuesday April 10, 2012 @01:02PM (#3823180)
Just to name a couple similar companies off the top of my head:

http://parse.com

http://kinvey.com

http://cloudmine.me

http://proxomo.com

Re:RESTful thinking considered harmful on Friday March 30, 2012 @11:39AM (#3776475)
This configuration can still be RESTful as long as you POST to those endpoints. The complexity I was referring to is the snowball effect of adding different actions.

If you use hypertext in the resources to specify the places the client can go, the complexity is severely reduced. However, properly enabling discovery is where most "Rest" APIs fail.

Re:RESTful thinking considered harmful on Friday March 30, 2012 @10:54AM (#3776189)
Exactly. Having these endpoints instantly turns your API into an RPC-API. This is the start of a snowball of complexity introduced for your consumers.
Re:API Design is UI for Developers on Sunday March 04, 2012 @03:08PM (#3663785)
Documenting every function is great practice.

Masklinn was just stating that an API based on 'functions' is inherently not a REST API, but instead RPC. The documentation sentiment is sound, but your terminology was off.

Re:Why Startup Hubs Work on Wednesday October 05, 2011 @04:04PM (#3077285)
I'm curious at Hacker News' thoughts on what it takes to start a startup hub.

For instance, here in Blacksburg, VA (Virginia Tech) a few local entrepreneurs and Angels are trying to get the startup community here off the ground. We've gone from little activity, to having a populated co-working space and regular meetups. The community is small and close; which is great for all those involved.

However, most companies that start here still aspire to move out to the Valley. The opportunities there still dwarf the opportunities here, and we're constantly in danger of losing what few founders we have.

Granted, Blacksburg isn't exactly a geographically optimal spot for techies to flock to. But is it possible that the larger hubs such as the Valley have too much pull for smaller communities to really take off?

As a Virginia Tech student that is excited about startups, I'm glad to hear you had such a good experience with DayOne Ventures. I'm going to apply for this year's summer session.

Since you guys are still local, I'd love to buy you lunch sometime so I can hear more of your story.

Re:The story behind Instagram on Sunday December 05, 2010 @07:21PM (#1973250)
I applaud their boldness to throw all their previous work away for a simpler idea. Sometimes we get too attached...
Re:Get the New Facebook Profile Now on Sunday December 05, 2010 @07:14PM (#1973233)
I like the change, it feels a bit more like a profile and less like a communication hub. The news feed is where I can find all the random chatter.

Older »