Edit.
They also connect to unprotected wifi networks to send data without your permission.
1,039 karma · joined March 28, 2007
[ my public key: https://keybase.io/hoov; my proof: https://keybase.io/hoov/sigs/hm9nAgg2PANOmcuiat4cL6ujLA1r9lNsPfB59ajd9Ng ]
Edit.
They also connect to unprotected wifi networks to send data without your permission.
Well, Amazon shows you the percent discount. I can't imagine that there are too many items over, let's say, $1000 that are at a 90% discount at any given time. Seems easy enough to flag those for manual review, especially if they are being sold by Amazon directly.
First of all, requirements.txt is for development requirements. Runtime ones belong in setup.py.
Also, the "extras" feature is already in setup.py via extras_require.
I see no need to use this nonstandard tool when the standard tooling works.
While I like Elixir a lot, I'm not sure that it's the best place to start. I'd find an ecosystem that is more stable and has more reliable resources available. Try starting with Rails or Django, maybe.
> I don't mind waiting in line for 3 minutes. Or 5. It's never longer than that, even if the cashier discusses the latest news with the old lady.
If I go to the Stop & Shop, I spend about fifteen minutes in line on average, and the cashier is consistently rude.
That being said, when I go to the more "local" stores, I have similar experiences to what you've described.
I lived with Drew through college and a bit after. The thing that grew into Dropbox was started in an apartment that I lived in while Drew and I were working at a different startup.
While I would say that I regret not being in the financial position to quit my job and help Drew out early on, I don't think he was able to do it because of his privilege. I also want to call out that I'm struggling justifying that last statement, because I know what a privilege being white, straight, and upper-middle class in America is. That privilege totally helped getting into MIT (by virtue of going to a good high school and so many other things). But, I'm pretty sure he didn't rely on his parents for cash. He probably just stole my leftovers out of the fridge. :)
The fact of the matter is that he's scrappy and smart. During college, we were both presented with an opportunity to make some side cash. Drew took more advantage of it than I did, and it was smart of him. He banked his own cash and lived cheap. Maybe he graduated with less debt than I did, and maybe that helped, but I think that would be the only leg up that he had.
But, I'm a curious individual. I'd love if the academic Python community (to try to put a label on it) would all write code that was "idomatic". I know that "idomatic" is a problmatic term, but specifically I'm asking for people to follow PEP-8 and generally follow the ethos of `import this`.
Once we're speaking a common vernacular, we can better share ideas.
InsightSquared is a well-funded Boston startup. Our SaaS app helps businesses make data driven decisions by pulling their sales, marketing, financial, customer service & other data from APIs like Salesforce, QuickBooks, and Google Analytics and presenting over 400 beautiful visualizations and powerful analytics.
We assemble in small product teams that work fast, have fun, and ship often. Your team of engineering, product, and creative peers will drive the operational and strategic decisions needed to move forward. We build on a modern platform (Python/Django). We ship code to production not just daily, but a dozen+ times per day. We test quickly, learn fast, iterate fast, and focus on code that matters.
We're hiring three engineers:
- Software Engineer
- Senior Software Engineer
- Systems Architect
http://jobs.insightsquared.com/mperry at insightsquared dot com
I run the tech side of a decent sized startup right now. Having joined ~4 years into the venture, one of my immediate concerns was the lack of visibility into how our system works. Keeping tabs on the performance of several hundred ETL pipelines is not super easy. I decided to double down on InfluxDB, changing the road-map of my infrastructure team.
Then, InfluxData introduced the TICK stack. I can get monitoring and alerting as well? Let's double down again!
I bought hardware, set up a cluster (painful), we filed bug reports, learned what sorts of queries not to run, and we were in good shape. I purchased tickets for a training session and a flight (out of pocket; we don't have travel budget). And then I saw the blog post last night.
All along, I knew that the promise of all of this great technology for free was too good to be true. There was always a little voice in my head asking me about how they actually made money -- I knew that a paid offering + professional services was not sustainable.
I'm angry, but we'll be fine. We're going to break apart our cluster and shard. We've already got code written to do a backup/restore that actually works (slowly) from one cluster to another. If we hit the point where sharding doesn't work, then it'll also probably be financially viable to pay the $399/month (on top of server costs). I'll still go to the training, but I'm not sure what I'll get out of it. The reason why I was going to the training was the section on "Cluster Administration".
The only thing that I'm raw about is the lack of apology. You have to make money, and you had to do a bait-and-switch as a result. I totally understand, but the tone of that blog post was too defensive and unapologetic.