salsakran

16 ms·

91.
by salsakran 11y ago
re:dash is very cool, and we actually used an early version way back. The primary difference is audience. Most of the impetus to build it came from the difficulties we had getting non-analysts to do their own data pulls and ad hoc queries.
92.
by salsakran 11y ago
Thanks for the kind words! Would love to hear what you think of the codebase.
93.
by salsakran 11y ago
Think they missed editing out the final "Text Magic now to get started:" at the bottom of the page.
94.
by salsakran 11y ago
https://cloud.google.com/prediction has been out for years.
95.
by salsakran 12y ago
They're already starting to lock down all the data that was originally Creative Commons. They've stopped allowing you to download snapshots as spreadsheets, and generally hobbled the API.
96.
by salsakran 12y ago
The easiest way to get them to use a CRM is to only pay commissions on deals marked as closed in the CRM. Run all meetings off the CRM, and if someone's lead status isn't updated make a point of asking why. Requires a bit of disci
97.
by salsakran 12y ago
Acquihires are bought not sold. Your acquirer will have some sort of price formula they use for these things and will have a price in mind usually. It's also hard to pin down exact numbers as they vary wildly by who is doing the acquir
98.
by salsakran 13y ago
Not sure I agree with fat models being a "rarely seen, alternative code organization strategy". It's a natural state which most django codebases tend towards. There's a natural Views use ModelForms use Models data flow w
99.
by salsakran 13y ago
We were thinking of writing something like this. Awesome!
100.
by salsakran 14y ago
"nor did we give anyone incentive to make shell accounts" vs "We offered our community free tickets to our next event if they helped us with up-votes" Cognitive dissonance much?
101.
by salsakran 14y ago
Smoking weed is not a crime in CA, which is where PyCon was held this year.
102.
by salsakran 14y ago
Wait ... a hack day where the devs have to buy tickets? On top of the event having 3 big name sponsors? What gives?
103.
by salsakran 14y ago
Maybe I'm just being harsh but I'm not quite ready to give my banking credentials to a barely styled bootstrap site.
104.
by salsakran 14y ago
http://sites.kauffman.org/pdf/angel_groups_111207.pdf ends at 2007 http://www.willamette.edu/~wiltbank/jbv_angels_2009.html was published in 2008 and http://www.nesta.org.uk/publications/reports/assets/features... was published in 20
105.
by salsakran 14y ago
Is there any way to autogenerate playground schema from tastypies's schemas?
106.
by salsakran 14y ago
NEVER ask a VC who said no for a referral. You're better off going to the next investor cold (or just do the leg work and get to them from a different direction) than via an introduction that reads "here's this deal I passed on".
107.
by salsakran 14y ago
I actually really like getting other people's lists of their favorite ST2 features. It's more digestible than getting the entire list in one go. I find I tend to get one or two features that I put into "rotation" in reading these, while loo
108.
by salsakran 14y ago
Dremel, as described in http://research.google.com/pubs/pub36632.html
109.
by salsakran 14y ago
The question isn't 1MLOC vs 1KLOC. It's a stable, well understood DB vs an immature, not well understood DB AND 1KLOC to deal with not being consistent. To be clear, I'm not saying any given DB is the OneTrueWay, just that people seem to be
110.
by salsakran 14y ago
Uhm..... no. This is backwards. Multi-DC capability is a feature. Eventual Consistency is an explicit tradeoff in a desired characteristic (Consistency) to allow other features.
111.
by salsakran 14y ago
I sorta get that, but it's not like Postgres/MySQL/etc are operational nightmares. It's just that going from one barely proven DB to another barely proven DB in a migration that involves a boatload of application side code seems heavy hande
112.
by salsakran 14y ago
I was reading along and nodding my head until I got to the 1000 line haskell program that handles issues stemming from a lack of consistency. I'm not exactly a SQL fanboy, but maybe ACID is kinda useful in situations like this and having to
113.
by salsakran 14y ago
To be fair, customers should be comparing PaaS pricing to their own fully loaded cost to roll-their-own. If a PaaS can't beat the internal price (including time, hiring ops people,etc), they're fighting a losing battle.
114.
by salsakran 14y ago
Ditto. People drastically underestimate the effort required to make a PaaS platform and drastically overestimate people's willingness to pay. It's a dogfight of a market with brutal economics.
115.
by salsakran 15y ago
Uhm, it involves cutting open your scrotum. The idea that people will casually do this is ... hilarious.
116.
by salsakran 15y ago
It seems truly bizarre to me that in 2012, there is a major operation that is still trying to vertically scale such a trivially shardable DB. Scaling a static Q/A site with a few widgets that require user info/counters should be table stake
117.
by salsakran 15y ago
You're not going to like hearing this, but unless those numbers are in kg's you're not likely to be "jacked". The reality is you're probably carrying significantly more fat than you think you are.
118.
by salsakran 15y ago
Here's the thing -- I (and a great many people I've worked with, interviewed, and was interviewed by) don't believe things like reversing a linked list are facts . They're basic skills that are either present or absent. If you aren't abl
119.
by salsakran 15y ago
I completely disagree. If you view data structures as something that you "remember" from your university days, then you are more of a "tool user" than a programmer. No matter what a candidate has managed to accomplish using their IDE and co
120.
Recurly raising prices.(recurly.com)
3 points by salsakran 15y ago|1 comments

More ›