NovoLabs | Dallas, TX | Full-time | Onsite or REMOTE
NovoLabs is a small team focusing on Conversational Commerce in the Restaurant Industry. Our vision is to provide a world class product that allows users to transition from an analogue channel like a Phone or Drive Thru to digital channel.
We're 18 months old and have recently begun taking Transactions from well known restaurants!
As we are still small, we are looking for highly capable, high impact, deep generalists or expert level React / Graphql people.
Our current stack includes: Clojure, React, Graphql, Scala, Finagle, Google Cloud, Kubernetes, Postgresql.
We offer a highly competitive package and would love to hear from you! If you're interested please email me with any questions: [email protected]
I've been jumping between AWS and Google Cloud ( with a bit of Digital Ocean sprinkled in ) for the last several years. I chose Google as our cloud platform when we founded our company last August. I could War and Peace a bunch of things but that article does a very nice job in the details. Instead, I'll give a one liner:
AWS is to Linux as Google Cloud is to FreeBSD. "Rock solid performance and everything is exactly where you think it should be"
I'm happy for the guys at Bouyant, they've been great to work with in the past.
There's a very large complexity payment inherent in the new "cloud native" architectures that fundamentally isn't worth it for a large swath of use cases. Conduit, at first glance, appears like it might solve a large portion of it. If there's anything the last 10 years have shown us as an industry, it's that convention and programmer ease of use are the most important qualities of a new framework or way of working.
Rails / Go / K8S dominating Mesos / Containers over Jails / Maven over ANT / on and on. ActiveRecord is great, and Rails routing is great. Together they are magical for what they provide a user. Envoy is great. Istio is great. But there isn't a simplistic way to unify them even though for 95% of the industry it appears their functionality should go hand in hand.
Nokona gloves are almost comically well made. I've used mine for over 20 years at this point and outside of a once a year oil'ing it has held up remarkably well. My dad has his from the early 60's and while it looks worn ( he hasn't taken care of it ) it's still very usable.
Alan Jacobs has a pithy overview of Morton, and the following is taken from a recent post on Morton by him:
This strategy of employing familiar language in unfamiliar contexts gives the appearance of being radical but may not be quite that. It strikes me as being largely a reversal of Skinnerian behaviorism: the behaviorists said that human beings are nothing special because they're just like animals and plants, responding to stimuli in law-governed ways; now the object-oriented ontologists say that human beings are nothing special because animals and plants (and hammers and black holes) all possess the traits of consciousness and desire that we have traditionally believed to be distinctive to us. The goal of the philosophical redescription seems to be the same: to dethrone humanity, to get us to stop thinking of ourselves as sitting at the pinnacle of the Great Chain of Being.
It's hard for me to take Morton too seriously because our ( by which I mean his and mine ) Metaphysics are so diametrically opposed. Hyperobjects are so ontologically complex as to give the feeling they have been invented solely to justify the philosopher's pre-existing beliefs ( though in fairness, you can write that about a lot of things ).
You're 100% correct. Sorry about that, my fingers didn't translate what I had in my head in regards to pkgng replacing the old separate multi-component way of handling binary packages.
My understanding was that pkgng is a architectural overhaul in addition to a simple client clean-up - configuration is different for example. What I was trying to get to was that the newer design is barely two years old in production. I should have written this more clearly and did not, thanks and sorry.
That's a good overall article - I've been switching back and forth between FreeBSD and Debian for several years now, and I never spend more than a couple of month without using one of them.
The one thing that surprised me was his take on FreeBSD's package management system, pkg. PKG is relatively new, having been released in late summer 2012. Prior to that, FreeBSD relied on the ports collection, which was (is) a vast tree of Makefile's allowing you to create custom builds of virtually any software imaginable.
While pkg is still raw on the edges, I VASTLY prefer it to Debian's hodgepodge of package management tools that all do 90% of the other, though none of them do it cleanly and none of them have straightforward interfaces. Am I using dpkg here? What about aptitude? Or should I just roll w/ apt-get? All of these tools combine the ease of use of git with the flexibility of a Maven build. If you know how to use to descend deep into the depths of git or Maven, this isn't an issue ( and for the author, it certainly is not ). Yet there are numerous simple tasks ( like say, searching for a package remotely when you aren't sure the exact name ) which still require hitting up google and settling in for a Click-Your-Way-To-Adventure session.
PKG, in contrast, is both simplistic and flexible ( it reminds me of a industrial grade version of Brew in some sense ). It's a tool that I find myself integrating into my workflow beyond simple installs / updates, particularly it's seamless integration with jails. Configuration of remote repositories is vastly simplified as well.
PKG is not perfect by an means - it definitely has worts that need to be taken care of. I'm also sure that PKG probably feels a tad inadequte to some hard core sys admins - pkg has the look and feel of a tool designed by a programmer looking to handle normal cases than a tool designed to provide a sys admin with an atom bomb if necessary. Yet the system is still relatively new and as the bugs continue to get ironed out it's a reminder to me of why I love FreeBSD in a lot of ways - the abstraction point is flawless and it gets out of my way.
NovoLabs is a small team focusing on Conversational Commerce in the Restaurant Industry. Our vision is to provide a world class product that allows users to transition from an analogue channel like a Phone or Drive Thru to digital channel.
We're 18 months old and have recently begun taking Transactions from well known restaurants!
As we are still small, we are looking for highly capable, high impact, deep generalists or expert level React / Graphql people.
Our current stack includes: Clojure, React, Graphql, Scala, Finagle, Google Cloud, Kubernetes, Postgresql.
We offer a highly competitive package and would love to hear from you! If you're interested please email me with any questions: [email protected]