kevinpfab
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.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.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.
JQuery Text Cycling
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.
Making things with Maths (Great Math Visualizations)
Source: I was a founder in TSC's first class.
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...
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.
Show HN: Generate REST APIs for Existing Applications
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]
Anonymous positive reinforcement in League of Legends - It's working
World Countries and Time Zones API
The Evolution of an Elevator Pitch
API Types - REST vs RPC
HTTP Methods and Idempotence
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.
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.
Better Ruby Autoload?
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?
Since you guys are still local, I'd love to buy you lunch sometime so I can hear more of your story.