496 karma · joined October 24, 2014
* Beds frames can be made cheaply and if they break, you can still put your mattress on the floor (bullets don't work well if just thrown)
* You need to sharpen knives pretty often, which is wearing them out, but it is true that good knives will last a good while. (But when was the last time you heard of a knife lobbying group pushing to prevent laws from limiting the knife industry's ability to sell product)
* File size. Not a big matter now-a-days but single text file can store many times more information than a binary file.
I don't think the author knows what a binary file is.
https://arstechnica.com/tech-policy/2016/04/whatsapp-is-now-...
Ordoro makes it easy for e-commerce businesses to ship orders and manage inventory. Everyday our software helps thousands of small businesses save lots of time and make more money by simplifying and automating their shipping and inventory management. It's not a glamorous space, but we do our best to make it awesome. We're well funded and have strong revenue.
We're looking for an experienced engineer to join our team. You'll help us speed up and scale our services, integrate with third party APIs, and upgrade our infrastructure as we transition to GCP and Kubernetes.
We're a small team so you'll have the opportunity to make a huge impact. Our developers code hard to make Ordoro awesome. We're serious about having fun while we work and equally serious about taking time off to enjoy life. Bonus points if you can make us laugh or cry.
You'll get the normal startupy benefits: - A paycheck - Equity in the company - Health, dental, and vision insurance - 401k (though we don't match yet) - Unlimited time off - Whatever gear you need for the job
In our dream world, the person we'd hire would love: - Using Python, Postgres, Redis, and exploring other technology that would make Ordoro awesome - Tuning SQL queries to keep the API fast - Automation and testing - Using 3rd-party APIs and figuring out all the fun little landmines their docs fail to mention - Deploying containerized applications on Kubernetes
In the first 2 days you'll commit and deploy code to production. In the first 2 weeks you'll commit and deploy a feature to production. In 3 months you'll completely own part of our codebase. In 6 months you'll be running the company :)
NodeJS has `npm` or `yarn`, and they basically do and setup the same thing. You can switch between the two without headache. As a new user (or one who has tried on multiple attempts to get into it), python is hard to start.
The second part of the system, is that, normally, no one customer will use more than one of the three load lines. That is why most houses only have one transformer on the pole out side their house. The power company makes sure they balance connections evenly within a given area. If they do this properly, the common 4th wire has no load on it.
Some buildings do use all three phases, but they would be running large industrial machines that benefit from having that type of power.
I tried to find the Wikipedia article that covered all this, but can't seem to locate it specifically.
Onsite
We just decided to open the position and didn't want to miss the HN posting this month. One will be up shortly.