dencold
Joined 13 years ago
Karma
207
Submissions
22
Member since
Mar 12
Recent submissions
Comment · 11 years ago
Siddarth, any word on when the 2015 edition of CTF will be out? I check the stripe blog every week or so hoping for some mention of timeline. I loved CTF3. You guys do a fantastic job on these. THANK YOU.
Comment · 12 years ago
This link is specifically for the chrome extension (which is great), but also worth checking out sourcegraph's main site as well: https://sourcegraph.com/
Their in-browser code analysis is kinda amazing. They index most of the go/python/node libraries in github and make the code browsable as if it were in a local IDE. For example, here's their representation of Flask's app module:
https://sourcegraph.com/github.com/mitsuhiko/flask@cc98ba909...
I've found it super helpful as a way to explore new libraries and see how they are used by other developers. Props to the sourcegraph team. Excited to see what else is coming down the road.
Comment · 12 years ago
Hahah, fair point. I should of hashtagged the post with #historical :) I loved this look back on the early days of networking and getting a little glimpse of Tom Lane's time at CMU. Reminds me of MIT's coffee cam[1].
[1] http://www.technologyreview.com/article/401059/coffee-cam/
Comment · 13 years ago
Thanks Craig! I missed the legacy pricing page and edited my post to reflect this. To make this more clear and transparent, I would include a link to this directly on your blog post. It certainly would've helped me.
If you wouldn't mind me asking, why the removal of the Kappa/Fugu/Zilla price points in the new tiers?
Comment · 13 years ago
Wow, talk about hiding the ball. Heroku Postgres 2.0 is changing the cost structure in a dramatic way. Gone is the 1TB of storage on all production plans (now the "standard" tier). Instead, you are limited to 64GB of storage on Heroku's cheapest $50/mo plan. As hoddez mentions above, you'll now need to spend $2000/mo to get the 1TB of storage space that you were able to achieve on yesterday's $50 plan.
What's additionally frustrating is they have made pricing much less granular. Instead of 8 pricing levels based on your ram requirements, you now only have 5. Old price points of $100/$400/$800/$1600 have all been eliminated and now you are stuck choosing between $50/$200/$750/$2000. These are steep price jumps between each level.
I understand that Heroku wants to highlight the new features here, but when they bury the pricing at the bottom of the post, and even include language like this:
"For those already familiar with our pricing our new standard tier is very similar to our now legacy production tier. For some of you this means migrating could actually provide over 45% in cost savings on your production database."
It strikes me as a bit disingenuous. For reference, here is the old pricing structure from the archive: https://web.archive.org/web/20131003031924/https://www.herok...
And here is Heroku's legacy pricing page: https://devcenter.heroku.com/articles/heroku-postgres-legacy...
Comment · 13 years ago
BART goes directly into the SFO airport. If you are taking a flight from the international terminal, it is a direct walk to the check-in counters. Otherwise you connect to the airtrain which is an escalator ride up from the BART platform.
I've found it extremely convenient getting to/from flights from San Francisco, although I'm lucky to be within walking distance to a BART station from my apartment.
Comment · 13 years ago
One thing I wish Github would do is allow for a more granular permission structure. It would be fantastic if we could allow people without github accounts do things like submit issues, or allow certain users (e.g. non-technical staff) only have access to the wiki and issue tracker.
Right now the permissions are centered around what you can do with repositories, it's very developer-centric. I think there is a lot that GitHub could do here to expand their service to be more applicable to an entire organization.
Comment · 13 years ago
Long-time user of boto[1] here. It has been the go to library to hook your python code into AWS and has a fairly active following on github[2].
One API point that I've found lacking in boto is a "sync" command for S3. Take a source directory and a target bucket and push up the differences ala rsync, that's the dream. Boto gives you a the ability to push/get S3 resources, but I've had to write my own sync logic.
So, the first thing I went digging into is the S3 interface of the new CLI, and to my surprise, they've put a direct sync command on the interface[3], huzzah! Their implementation is a little wacky though. Instead of using some computed hashes, they are relying on a combination of file modtimes and filesize. Weird.
Anyways, glad to see AWS is investing in a consistent interface to make managing their services easier.
[1] http://boto.readthedocs.org/en/latest/index.html
[2] https://github.com/boto/boto
[3] http://docs.aws.amazon.com/cli/latest/reference/s3/sync.html...