141 karma · joined January 24, 2012
I think my account now showing up as having no facebook or linkedin is a red flag and wish that could be addressed, but airbnb support was not willing to help with that.
I don't see how me making a video is a substitute for fixing a technical problem that has broken the connection between my airbnb account and my linkedin and facebook accounts.
I don't understand how "make a video" is the solution to some technical problem with AirBnB that causes the message "Your facebook account is already being used to verify another account", when in fact it is my primary login credential to the airBnB service.
thanks for the recommendation, will check it out. I got deep in the guts of tastypie and wasn't happy with the way it handles patching and nested objects in particular.
For my kiosk project, as an example, I need to send a nested object graph over the wire. The wifi card in the kiosks isn't very reliable, so doing it in one call is very helpful (only one thing to retry a couple times, vs 10-ish objects, max depth of 4).
From what I can tell, django-rest-framework is read-only beyond one level of depth (you can return a nested hierarchy, but not post it in one shot)
Also, some of my objects are transient (e.g. credit card data), so I don't have a django model for each object that is an input to the api. (I have a plain old python class with some special magic for parsing track data, validation fields, etc for credit card and drivers license in particular, can't ever save that data to the db).
would you use django-rest-framework for that?
(also, is there a django equivalent of ActiveAttr, which lets you make ruby classes that act like active record objects without the persistence? or would you just make models and never save them? probably wouldn't look so good in an audit though)
I want to make some comments on writing APIs in particular, since I've been doing a lot of it lately, as my projects almost always have several interfaces these days, e.g. native mobile apps, angular.js web frontends, and as I mentioned above, fat clients running on kiosk hardware.
Building json apis in rails is a pleasure. My mini stack inside of rails is controller -> request handler -> model layer + external services -> rabl. Very clean, few lines of code, easy to maintain, does exactly what you want.
Doing the same with default django is a little less obvious. Tastypie is cool but when you get much beyond providing CRUD over the web to your models, it gets messy. Forget nesting stuff more than one layer deep. In the end, I build a controller layer that matches the way rails works and it's just about as nice, but I have to know and follow the conventions myself.
In particular, i'm copying rails style validators for models, I've built something similar to my rails request handlers using django forms to handle input, and i've built a simplified controller layer that handles routing, paging, filtering, sorting, etc. Instead of rabl, I just write a to_dict function to package data into a response. not quite as slick, but roughly equivalent.
I had to do more on the django side to get there, but at this point both are equivalent for me in terms of building APIs.
I understand that these days there are compelling arguments for building APIs in neither of these languages. However, for speed of development, ease of also putting up a vanilla web interface, and richness of the ecosystem as a whole, I still like django and rails for building mvps.
What would be an example of something you encountered with django that required getting creative quickly, that rails handles more routinely?
For me, the trickiest thing in either ecosystem to get a handle on was probably rspec. I tried to learn it by osmosis and that was probably the wrong way to go. In the end, it's worth having a DSL for writing tests and leads to nice clean readable code.
When people are trying to learn rails, I point them to Rails 3 in Action and Michael Hartl's online tutorial, but still need a better reference for learning rspec. suggestions are appreciated.
To me it seems like a waste of time to build crud websites in CL, but if people want to write articles about ways to make that experience better, i'm not going to write 'haha wtf' in response. (Yes, all analogies suck)
If you're really looking for a latin equivalent, I agree with the previous posters (a lisp, python, and c all have merit and are worth getting to eventually).
My own early learning path was basic -> dos shell -> c -> c++
I'm glad I learned c, wouldn't really mind having missed C++.
this seems like about the perfect situation for starting over. congrats!
http://docs.python.org/dev/py3k/whatsnew/3.0.html#changes-al...
PEP 3101: Advanced String Formatting. [...] The plan is to eventually make this the only API for string formatting, and to start deprecating the % operator in Python 3.1.
As far as I know, interpolation is not actually deprecated yet though.
Studies like this have shown that herniated discs and other types of damage once thought to be the cause of back pain are present in pain-free people with a high rate of incidence.
Further, it's not known what the tradeoffs are in terms of risking damage vs the benefits of increased strength.
I do think extra research is needed.
FWIW your definition of heavy and mine seem to be about the same: A weight the subject can lift with perfect form for a small number of reps, e.g. <= 5. With training, likely to be in the range of bodyweight x 2 and up.
all people should stay away from heavy deadlifts until they have mastered good form of course.
As an aside, GPs tend to give bad advice on all matters of sports medicine.
I've had a couple of jobs where support reported to me. In those cases, our end client had a help desk of some form that was escalating to us, so it wasn't unusual to get small laundry lists of whatever their admins couldn't deal with.
I greatly prefer to have those lists split out into individual tickets.
Granted, our systems provided the ability to pull up a view of all tickets associated with a specific POC or client, maybe that's all you are asking for. I just wanted to point out that i haven't seen any shops where it was obvious that what you're asking for was easy or correct.
If you have an example i'd love to hear about it!
Small teams of motivated people can make just about anything work. For everyone else, support makes project schedules more predictable and can avert certain painful scenarios.
EXE files were larger and had to be rebased by the OS on load.
Someone tell me if i got this wrong, it's been a while!