There's a lot wrong with this design. It is perhaps reasonable to use on new wine with pristine corks. But corks are a natural material, so they have a lot of variability, and they do degrade over time. If you open a lot of wine (e.g., if you are a waiter or sommelier) or you drink wine at many ages (e.g. if you are an aficionado or collector) then you need more control in where you place the worm in the cork and how you control the extraction of the cork (for instance giving lateral pressure). This is why you will never see people who routinely open wine as part of their jobs with a wing corkscrew.
(Even worse, wing corkscrews are most likely to have an auger type of worm rather than an open helix. This is not inherent in the design of the corkscrew, of course; many wing corkscrews have open worms. Just something to watch out for if you are buying one.)
They appear functionally similar, but the coffee made is very different. A standard french press requires a coarse grind and you can only adjust extraction by changing the steep time. The Aeropress pushes coffee through a paper filter with an airtight seal. You can vary both grind size and steep time. Not only that, but you can vary extraction across the brew by very slowly pushing the coffee through the filter. (This is a very important feature of pressurized brewing methods such as espresso.)
These controls allow you not only to better tune for different beans, but to successfully make different styles of brew for a single type of coffee. (For instance, you can adjust those variables to successfully make a shorter, more espresso-like brew or a taller, more pour-over like one from the same coffee beans.)
SwiftStack | Software Engineer, Cloud | San Francisco | Onsite | Full-time
At SwiftStack, we are building a storage platform that makes data easily manageable and portable between public and private clouds. In the process, we’re tackling some incredibly difficult and interesting data management and storage problems.
SwiftStack is the primary contributor to the OpenStack Swift object storage system, and the team behind 1space multi-cloud and the ProxyFS filesystem. We strongly believe in open source and develop these core systems in the open. To support our customers, we have developed a commercial product based on these projects to provide a powerful combination that gives our customers a scalable, modern storage system with object and filesystem capabilities that integrates with public cloud services.
We’re looking for strong developers with experience in distributed systems, storage, or cloud infrastructure. It’s a plus if you have delivered complex systems in Python. If you decide to work with us, you’ll contribute significantly to open-source software, work with developers around the world, and deliver important features to customers quickly and regularly.
Software Engineer | https://swiftstack.com | SF Bay Area | Fulltime, ONSITE, VISA transfer
We’re a small team developing a distributed filesystem built on top of our widely deployed object storage technology.
Are you an experienced distributed systems developer looking for an interesting new challenge? Perhaps you have filesystem or file protocol development experience, and would like to bring that to bear on a brand new system? Or maybe you are an experienced Golang developer who wants to make an aggressive step in career growth? If so, we’d love to talk to you.
Some information about us:
* We have a small team of great people that punches way above its weight class.
* We love open source. We are big open source contributors.
* We're hiring for the team in our HQ in San Francisco.
This is absolutely correct. Hotels are optimized for a very particular pattern of travel: individuals or couples who use the accommodation solely to sleep. Many, many other use cases are actually more economically serviced by vacation rentals, mainly due to the availability of a full kitchen and comfortable, aesthetic, and private common spaces such as living rooms, pools, decks, and hot tubs as part of the offering, and greater flexibility with location.
Consider, for instance, the following:
* 3 or more couples wish to travel together. They'll be doing some touristy things during the day, perhaps, but half of the fun of the vacation will be hanging out and bonding in the evenings, having wine in the hot tub, deep personal conversations in the living room, whatever it is they do. A 3+ bedroom vacation rental will accommodate this more economically than any similar hotel situation, even when they do exist.
* A family wishes to travel together. They have an infant, a small child who is a picky eater, a ten year-old boy and a thirteen year-old girl who refuse to share a room, and one of the parent's mother who will take care of the infant at "home" while the rest of the family does some of the more challenging activities. This group probably doesn't want to eat out for every meal and needs a comfortable and pleasing space for the grandmother to stay in for long periods of time during the day.
* Three or four bikers have found a beautiful route in a less-travelled semi-rural area. The nearest hotel is 15 miles away with no bikeable route, but there is a vacation rental just one mile away on rural roads. No need to bring the bikes into the hotel room, no need to rack the bikes on the car to get to the trailhead. Get the bikes from the garage and go.
* A small startup team is attending a conference. They'll be having business meetings all day, so it is important for them to be together to prepare their pitches in the morning and be together in the evening to review the results and strategize. Local hotels and restaurants are full of their competitors, and a private space will help them to focus.
* A couple has always wanted to visit an amazing locale. One of them has a significant food allergy to an ingredient commonly used in local cuisine, and the area is not known for being accommodating in this way. Because of the allergy, they are used to cooking for themselves, and would prefer to do that rather than, say, eat hamburgers every day at the hotel restaurant. Having a well-equipped kitchen is important to them.
I could keep going. The vast majority of my travel is in situations like the above that are more possible, economical, and/or pleasant in vacation rentals than in hotels. I've been using them 3-6 times a year for the past 15 years. (I used VRBO before AirBnB.) I can't imagine going back to staying in hotels for most of my travel.
Software Engineer | https://swiftstack.com | SF Bay Area | Fulltime, ONSITE, VISA transfer
SwiftStack helps companies address the rapid growth of valuable but unstructured data. We build an object storage system capable of safely storing many petabytes of data and effectively managing the ecosystem of machines, devices, and drives that it takes to do so. We do all of this on commodity hardware so that companies can build out storage behind their firewall in a way that is both cost-effective and optimized for them personally.
Some relevant info:
* Our stack is primarily Python with some Go, but we know you can learn those things if you don’t know them already.
* Our headquarters is in San Francisco, and we have a small office in San Jose as well.
* We have a small team that punches way above its weight class.
* We love open source. Our storage engine is based on OpenStack Swift, and we’re big contributors to it as well as other open source projects.
We’re looking for talented engineers of all stripes. If you have a strong background in storage management, distributed systems, or devops, then we’re particularly interested, but many of our number began as very gifted web developers with a hunger to learn something new.
Our interview process: (1) intro with founder + entertaining technical phone screen, (2) onsite, technically focused interview that's mostly small work-sample programming that you perform on your own computer, + meeting the team (3) there is no number 3.
We create large-scale object storage systems based on OpenStack Swift. We help companies who need to store massive amounts of data to do so easily, safely, and cheaply in their own data centers. We’re committed to open-source; everything we put into Swift we push upstream. We also develop a valuable proprietary orchestration system that’s our core revenue driver.
Reach out to us if you have any of the following:
* Experience writing high-performance server software (Python/C/C++/Go)
* A deep and abiding interest in distributed (storage) systems
* Vision that simplifies complex user workflows (front end/UI/UX)
We aren't asking for much here at SwiftStack. All we need is someone that's
* An experienced, opinionated crafter of scalable distributed systems
* Possessed of a deep and abiding knowledge of Linux
* A brilliant Python developer, steeped in the Web
* Excited about deployment and knowledgeable about packaging and
the infrastructure that goes into getting nontrivial software systems
from "here" to "there"
* Oh yeah, and it would be peachy if that person was really good at
front end development so they could give our users a smooth,
comprehensible experience that masks the inherent complexity
under the hood.
(We'll supply the horn.)
OK, maybe that is a big ask. It’s true, at a small (but growing) company, we do wear many hats, so the more you fit the above description, the better. But what we're really looking for is a smart, talented, intellectually curious engineer with a strong background in at least one of the above skills and aspirations to grow in one or more of the others.
We've got a multi-talented engineering team and a host of compelling software-related challenges in many different arenas, and by the time you're done here, you'll have broad and deep enough experience that you'll have earned your unicorn horn, and no can take that away from you. Because you'd stab them. With your unicorn horn.
Who the heck are we?
At SwiftStack we're building software to help people create petabyte scale object storage infrastructure in their own data center instantaneously. At our core, we use Swift, OpenStack's object storage technology, but we're building an orchestration layer that does the easy things for you, makes the hard things easy, and makes the impossible possible.
Why join SwiftStack?
* You'll be part of a small team of highly skilled people who are also
very nice folks and would totally help you out in a pinch.
* You'll be joining a company at a perfect size -- just big enough to
have momentum, but small enough that the decisions you make will have
a real impact on its course.
* You'll get valuable experience building a product meant to manage massive
amounts of data. At scale, there are no easy problems.
* Swift is Open Source technology, and part of one of the most important Open
Source initiatives in recent history: OpenStack. You'd be writing code that
people all over the world would use, including the likes of Wikipedia and CERN.
If you've ever wanted to write code that has an impact, and we know you have, this is a good place to do it. Drop us a line at jobs@swiftstack.com, take a look at http://swiftstack.com/jobs/, and/or check out our puzzles at https://swiftstack.com/jobs/puzzles/. Thanks!
Hi, HNers. I worked with Orion a few years back and wanted to say publicly that he's awesome. Smart, chill, reasonable, and funny. I'll definitely be passing this along to friends.
I propose that, what with unicorns numbering one-third of the population in many areas, we simply cut to the chase by declaring that our firms will henceforth only hire demigod alicorn princesses. This will convey exactly the desired degree of hyperbolic rarity we intend.
The fact that there are only four known alicorn princesses ever isn't going to stop every firm insisting that each and every candidate hoping to interview provide strong evidence that he or she is one of the four alicorn princesses.
You’ll work on a product that touches millions of people’s lives even if they don’t know it. The number of businesses using OpenStack in general and Swift in particular grows and grows, and it includes big names that make products that are used by both your little brother and your grandmother. You’ll work on a product that makes core OpenStack technology accessible to businesses of all kinds.
You’ll get open-source experience in a big way. At SwiftStack, we’re committed to strong participation in the OpenStack ecosystem in general and to contribution to Swift in particular. You’ll be a contributor to one of the most important Open Source projects currently active.
You’ll confront interesting problems every day. Writing a system like Swift and building a software ecosystem to surround it is the road less traveled. We aren’t writing yet another glorified CMS or social app or phone game. Whether it’s figuring out better algorithms for data placement, confronting a firehose of monitoring data, or determining how to integrate most flexibly with customers’ systems, there are always new and unusual problems to solve.
Interested? Send us an email at jobs@swiftstack.com. Send us your github profile, your LinkedIn account, a link to your website – whatever will best display the work that you’ve done. Tell us in a few lines of text why you’re interested in SwiftStack, and why we’ll be interested in you. We’ll be back in touch shortly to get the conversation started.
(Even worse, wing corkscrews are most likely to have an auger type of worm rather than an open helix. This is not inherent in the design of the corkscrew, of course; many wing corkscrews have open worms. Just something to watch out for if you are buying one.)