Used to live in Brunswick, now we're living in middle Georgia but my wife and I still love to fly our C182 down to grab some BBQ at Southern Soul (or cheesesteak at Skinny Pete's) every month or two. SSI is gorgeous and the airport is in a great location and staffed by some great folks.
best glide (converting altitude into the maximum distance) speed is quite a bit higher than the stall speed and found at the lift/drag max. minimum sink (converting altitude into the maximum time) is usually found about halfway between best glide speed and stall speed.
Audiomack (http://www.audiomack.com) is a fast-growing music sharing and discovery website. We are looking for a generalist engineer to work with us in a contracting role on a full-time (or nearly FT) basis. You would be welcome to work out of our SoHo NYC office, remotely, or some combination. We are looking for candidates who can contribute immediately to both backend and frontend projects.
Between destkop & mobile sites, embeds on other sites, plus iOS and Android apps we generally have 5-20k simultaneous users, 2-3 million streams per day, resulting in 30+ TB daily bandwidth use. We are looking for someone who is passionate about designing and implementing efficient systems that millions of users will interact with daily.
Skills & Requirements:
- excellent coding skills and proven track record of delivering value
- several years of experience with full-stack web development: backend, frontend, database
- (if working remotely) proven telecommuting skills: self-motivated, highly productive, maintains open lines of communication with the team
- able to make sense of existing code and seamlessly integrate new features without breaking current functionality
- good coding habits: writing tests, matching existing coding style, intelligent decision-making on when to refactor, etc.
Key Technologies:
- PHP / Zend Framework
- Redis / Redis Cluster
- The usual frontend technologies (HTML5, CSS3, JavaScript + common libraries, AJAX)
- AWS (EC2, CloudFront, S3, etc)
- Git / Github
Bonus for candidates with experience in:
- music fingerprinting
- extensive HTML5 audio/video development
- soundmanager2 or some other audio API/framework
- redis clusters
- sysadmin-related tasks
If interested, please contact us: management at audiomack.
don't really know what the power requirements are for his device as it currently stands. generating enough power in space would probably weigh enough to make the effects of the current device they've built all but unnoticeable over a reasonable amount of time. if they can advance their modeling of the effect and figure out what effects efficiency they'd likely be able to design and launch a device that could deliver much more convincing results.
There's quite a few.. super fast networks, network based elb (i assume cause it scales up smoothly and instantly), persistent volumes that can be attached to multiple machines at the same time (read only).. etc.
Watched the video, don't think they mentioned it... any idea how fast it is? They said it can fly for up to 5 days, but without knowing cruising speed it's hard to say how useful it could be for moving people and cargo around when there's other options.
So best-case scenario it can go 2400 miles, assuming it can refuel on arrival. While it could hop and be managed at any local field with a fuel dump, I do wonder how well it can handle the elements if kept outside at a stretch. Crossing the Atlantic would be tricky, for example.
So while "disaster relief" is a good use for this thing, rapid response is not. It's in for the long haul - you set up in a neighboring city and use it to ferry goods back and forth. But by the time it arrives, the existing disaster-relief structure may have more conventional approaches to shipping in goods/personnel (rail/train/ships/runways)
... this thing really seems to be a solution looking for a problem. If the technology could be made cheap, I could see the worth of a low fuel-to-weight ratio for air-freight in servicing remote areas (places above the arctic circle come to mind) but that's a mass-produced fleet of flying trucks, not a lone relief ship.
I see the major advantage in being shuttling between a field (or port) in which conventional transport can be utilized, and a specific disaster locale in where you cannot land a 747, C130, or dock a PANAMAX ship. Utilize those for the long-haul, then use the airship to shuttle between your full-service port and the specific locations which are cut off.
When you're talking about the difference between getting supplies to a region that's cut off from the rest of the world, even a 10km or 100km haul can be hugely useful, and the airship can cover that distance in 6 - 60 minutes.
regarding #1, I don't believe he's talking about someone who has chained together a bunch of jobs spending a year at each. Having "The same year of experience X times over" generally means you didn't grow as a developer from your experience because you were doing the same thing in the same way for a long time.
For example, if your job is cranking out CRUD apps or "online brochure" websites for various clients and you do it for 5 years, there's a good chance that while you're very good at those things now, it hasn't really gained you the same experience as if you'd been doing something a bit more demanding.
could easily knock multiple thousand bucks off of that by just reserving the ec2 servers you know you'll need, plus reserve the cloudfront bandwidth you know you'll need (for the amount of data served I believe you should be able to cut CF costs by at least half).
3 year heavy EC2 reservations pay for themselves in ~7 months, cloudfront reserved bandwidth is just a 12 month agreement so that costs nothing up front. You might want to experiment with some different instance types though, depending on your resource utilization. Personally I really like using the new c3.large instances for my web servers and anything else that needs more CPU than memory, proportionately. If the standard instances suit your needs better you still might want to move to the m3 class.
Aside from those two items it looks like you are sending out a considerable amount of stuff from EC2->internet (27 TB transfer out from US-East to internet). I'd recommend looking at whether you could set up a cloudfront distribution with your EC2 servers as its origin.
sure, all of that is possible. but honestly how likely is it that some or all of those things are the case on the direct path from netflix/youtube through the ISP in question to so many people's homes? and yet the problem spot is mysteriously avoided when using a VPN (not any particular VPN, but pretty much any of them, judging by most of the people who have spoken out about this problem recently). the problem so effectively avoided by changing the route from the optimal(ish) path to one that is almost guaranteed to be worse from a network flow standpoint.
sorry, I don't buy any apologizing for comcast/verizon failing to deliver HD video from netflix/youtube yet somehow able to do it under the same network conditions (same time) just this time through an encrypted VPN. if it was an isolated report... maybe. this is far too widespread to be anything but intentional.
Well, under-provisioned backhaul, peering, and/or transit would cause exactly this. And the blame trail could be quite complex. I'm not apologizing, but commentary by almost anyone other than the network architects and peering coordinators of these organizations are pretty baseless speculations.
Disclaimer: I work for a major CDN. Netflix is trying to ween off of us and our competitors, which has contributed to lesser experience. Their model of co-locating gear for free doesn't make much sense to ISPs in the grand scheme of things.
