3,269 karma · joined July 21, 2009
When you want to use a tuple as a key in a dictionary, Python checks if all members of the tuple are immutable. If one or more of them aren't, you'll get an 'unhashable type' error.
I'm sure the author means contrails ?
https://skeptoid.com/episodes/4027 "Chemtrails, real or not?"
and a secondary one: the app ecosystem isn't worth it anymore:
"With well over 2 million apps by now (officially 1.5M as of July 2015), the iTunes App Store is an incredibly crowded place where it’s almost impossible to get noticed. Despite the persistent myth of the app developer millionaire, it’s extremely hard to make a profit — let alone a living — as an iOS app developer. The Google Play Store is a similar story, except with the added bonus of rampant piracy and a zillion devices to support. There really isn’t gold in them hills, at least not anymore, and independent app development will soon be in sharp decline, if it isn’t already.
Essentially, there’s a massive oversupply of apps, and the app markets are now saturated and suffering from neglect and short-term thinking by the companies who operate them. As competition has intensified, developers have resorted to giving their apps away, often at the urging of the app stores themselves. Consequently, the willingness of users to pay for apps, even unique apps like Just Landed, has declined sharply, while expectations of what an app should deliver have never been higher. Developers have been forced to get absurdly creative with their business models and marketing strategies just to make any income at all, rather than making the best product for their users. Just Landed, being a paid app with high running costs, has been on the wrong side of these trends, and what worked in 2012 no longer works in 2016."
"The model part in an MVC application is where all the business logic is kept. Those are all the classes like ‘Post’ and ‘Category’ and ‘Author’ and all those things –say if you're making a weblog– you'd keep all that stuff in the Model. And you'd have all the logic about whether the author is allowed to make a post and how the relationship between posts and comments work together. Those are all sitting in the model, so that's all the business logic, very often backed by a database in some sense, not always, but most of the time. And that's where in Rails we're using something called ‘ActiveRecord’. Which is this way of mapping database tables to objects, and then decorating those objects with logic."
[0] http://www.transcribed-interview.com/dhh-rails-david-heineme...
"One example I always pull out is “what you gonna call the primary key in your tables?” When I was working with PHP and Java, every single shop, almost every single application, would have its own naming scheme. Some would say they have the ‘Products’ table and then they'd have ‘productid’, others would have ‘product_id’, some people would have ‘prod_id’ or ‘p_id’ or ‘P_id’, and every time somebody made a new design decision it meant configuration. You now have to tell your models, your objects, how they're going to talk to this database table. Because it needs to know what the hell you called the freaking primary key column, and it just doesn't matter! Who cares what the primary key column is called? It just doesn't matter. It's going to have zero impact on the usefulness of your application."
and
"‘Dont repeat yourself’ is all about not having the same intentions spread out in multiple places. Don't have one configuration. If you're calling something, let's again take the example of the primary key. If you're calling that for ‘id’ you shouldn't have to configure that in three different places that all have to work together and all have to be changed together. You should just pick one authoritative place to have that information stored. And then you can make changes from there. It also goes with the the whole Ruby idiom: we don't want those Java boilerplate ten line things: that's repeating yourself. If you have the same idiom, if you have the same intentions, that should really be exceedingly a short expression. And that goes up throughout the entire framework. Just keep one place to change those things, and keep the idioms very short."