125 karma · joined March 21, 2014
This doesn't make sense to me. How is an A/B testing mentality at fault for this? It has nothing to do with the incorrect datasets... you don't A/B test your data structure... I hope. A/B tests are blamed later in the article too, not really sure why.
But linking to data for 5 months and then only using the 4 you want to use to skew numbers seems pretty ridiculous to me.
And then in the same page there's data for drug/narcotics violations which isn't even mentioned because it is going up (21% more) even though there are supposedly plummeting marijuana convictions. Also they stated that the crime rate in Denver is going down, yet the data shows the exact opposite.
Whole article seems like cherrypicking at its finest.
If you are unable to follow a city or county's laws, then you either need to go about trying to change those laws in that city or country, or not operate there. They released an app specifically to do something that is not legal in a specific city - look at that twitter post.
You can't do something illegal in one city just because it's legal elsewhere - why should an app be allowed to?
>The subject matter of the post drove businesses with real money to our site.
...from Hacker News? Anyone else find this rather contradictory?
Less shipping supplies ($5,811)
Less storage lease for 5 months ($690)
Less postage ($4,701)
Less temporary help ($741)
Less charity: water contribution ($2,000)
$13,943 in addition to his $15,000 loan, as well as Kickstarter taking 5% and the 5% merchant fee, which would have come out to ~$1000. I don't think people would have received the poster.
From the first bullet point in the "Grid System":
>Rows must be placed within a .container (fixed-width) or .container-fluid (full-width) for proper alignment and padding.
Different stacking in mobile and desktop: http://getbootstrap.com/css/#grid-example-mixed Nesting Columns: http://getbootstrap.com/css/#grid-nesting Column Ordering: http://getbootstrap.com/css/#grid-column-ordering Lead class: http://getbootstrap.com/css/#type-body-copy Block Quotes: http://getbootstrap.com/css/#type-blockquotes Inline Lists: http://getbootstrap.com/css/#type-lists Inline Forms (helping screen readers): http://getbootstrap.com/css/#forms-inline Images: http://getbootstrap.com/css/#images
I guess you might not think to look for it in the documentation, but if you don't think to look for it, that means you probably aren't using it, and don't need it... I still wouldn't really call any of these things tips or tricks, it's just actually reading the documentation of what framework you're using, which apparently people don't do?
Maybe you should have said "Some people," then.
I guess that's great for people that have a sweet Github profile...
I don't think it was meant to be taken the way you portrayed it at all.
So going from a platform where random developers don't have access to _all_ of my contact info to one where they do is safer, in your opinion?
I get that you are trying to produce a better developer API, but I don't think users have any more control over their data with your product than they do with LinkedIn. Now they're just at the mercy of a different company's business decisions, which is how it will be in the majority of cases, as I see it.
And if you can plug your company as one of the Good Guys(tm) at the end I guess that gives you even more incentive to write about it.
A good DI container can make it much easier to follow a pretty good amount of general best practices. Single Responsibility, DRY, and Open-Closed Principle to name a few.