What I (and you) seem to have assumed was that this was DNS based certificate pinning, which to me would have made a lot of sense.
404 karma · joined April 18, 2012
https://www.auditboard.com
What I (and you) seem to have assumed was that this was DNS based certificate pinning, which to me would have made a lot of sense.
We're building a marketplace for summer camps & after-school classes. While helping parents, we also help the businesses behind these activities manage and grow their business through powerful SAS tools.
We're looking for highly motivated product-oriented engineers who want to contribute significantly to a complex B2B+B2C product. You should be able to work effectively in a startup environment with frequently changing needs, little direction and tight release schedules. Being a part of a small team is a great opportunity to grow & develop yourself through taking significant ownership of the product. If you're looking to have a large impact & join a talented team in working on a product that solves a real problem, this is the place for you.
Experience with Ruby on Rails and/or Bootstrap is a plus, but not a requirement.
We're building a marketplace for summer camps & after-school classes. While helping parents, we also help the businesses behind these activities manage and grow their business through powerful SAS tools.
- We are Series A funded. - Equity & salary per experience. - Ruby on Rails stack -- but direct experience not required. - Looking for smart motivated engineers. - Small but growing engineering team
In fact, in young circles (in the US), this seems to have become the defacto way of transferring money socially between individuals. I don't think I have paid someone I know with physical cash in years.
If you have few dependencies other than Django, the upgrade from South should be fairly smooth. You essentially start your migrations from scratch: Delete the South ones, let Django re-generate migration 0.
Two minor gripes: 1) No replies to comments ... comments with collaboration need to be conversational 2) No ctrl-z / ctrl-y (expected in any editor, and an annoying realization)
Thanks for building this!
Even if you have "auto-play", this is vastly different than the "scheduled content" of traditional TV.
Netflix stops every few episodes because there are per-stream costs, whether bandwidth or licensing (it's a waste to leave shows playing all night while someone's left their computer).
Additionally, as is mentioned, they also support Flash on desktops, which most people already have installed. However, the Flash streaming is not as great -- it most-likely uses RTSP, an older stateful streaming protocol, versus their Silverlight client likely uses Smoothstreaming (or similar), a HTTP-based adaptive streaming format.
1) This is almost true. Anything that is committed to Git is recoverable. When you "re-write" history, Git is creating a new set of commits in the history, an "alternate history path." It does not destroy the original commits, but there is no named reference to them (unless you created a branch/tag pointing to this line of commits).
2) In this case, if you want to actually destroy these unreferenced commits, you must run "git gc". This IS a destructive command. It will remove any unreferenced commits from the repository. (gc = garbage collect). If you never garbage collect, you will always have access to anything that was ever committed. It just might be hard to find since the only reference is the ref-log (if it was recent) or the commit hash.
"Your item must be a non-media product (you cannot send in books, CDs, VHS or DVDs without stickers)."
It seems Amazon actually no longer allows co-mingling of media products.
1) G-WAN is closed source. This means you're tied to their paid support for fixes and improvements. Web servers are pretty critical pieces of infrastructure that are not replaced easily (if you're doing large deployments, custom config, etc.) and so having this risk is huge. 2) Documentation, configurability, support for well-tested integration with various application servers. For example, Nginx supports uWSGI out-of-box. The G-WAN site seems to have limited documentation. 3) Nginx is well proven in production. Sometimes just being incumbent is a good reason. This often takes some large project or company taking a risk on the platform, proving it in the process; this is unlikely due to #1. 4) Other benchmarks indicate otherwise in regards to G-WANs performance; not to say its bad, but the selection of benchmarks on its site is likely biased towards it.
There may be many other reasons...
If you are hiring for someone that will just "do the work" and not care what it is, then it seems like this is sound logic.
However, if you're looking for someone who is creative and passionate about their work, believes in what your business is trying to do, and the work they are trying to accomplish, and will find the best way to accomplish it -- school no longer seems so representative of this, where they know the tasks they are completing serve no purpose other than a "grade."