56 karma · joined June 1, 2009
In California specifically, Labor Code Section 2870 limits an employer's claim over inventions or products created a) outside of work hours, b) without using company resources like your work laptop, and c) not related to/competitive with the company's business.
Even outside of California, it's extremely rare for companies to try to claim ownership of side projects that check all of the boxes above. Legal action is expensive and bad PR unless the employee is clearly infringing or building something competitive.
I think Quora was the first to do this: https://dangelo.quora.com/10-Year-Exercise-Periods-Make-Sens...
... I don't know what to say. At 20pt, too?
It’s up to Adobe to make their own future, not Apple. Perhaps that’s why Adobe recently unveiled Adobe Edge, and a Flash-to-HTML5 conversion tool.
Cursebird (http://cursebird.com/) is powered by Mongo via MongoEngine (http://mongoengine.org/) and Redis via redis-py (http://github.com/andymccurdy/redis-py). None of the Django apps have a models module.
I'd even say consider Flask for larger projects if you have patience, a good head for package/module layouts, and are after a really "no fluff" framework.
Tie it up to Nginx using Gunicorn: http://gunicorn.org/
(Here's the instructions in the Flask docs: http://flask.pocoo.org/docs/deploying/others/#gunicorn)
You will get some killer, low memory performance (many times smaller memory footprint than Django) out of that setup.
Not having a native language version wouldn't necessarily dissuade them from the purchase of the app, but it's certainly appreciated if it has been translated. If anything, it just makes them feel like the developer cares about them and their market.
They would almost certainly choose a localised version of the same or similar app if it became available, over the English version (so it might be worth doing so for competitive reasons).
Many of the people I've spoken to said that they would generally not recommend an app to their non-English speaking friends if it were not localised, even if it was reasonably simple to learn how to use.
I've only spoken to a couple people, and they were pretty tech-headed, so it might be worth speaking to others.
Don't underestimate that, if you're willing to put the effort in and do ad sales.
I prefer to be explicit in the settings for each environment, and create a settings package, with the following modules:
- common
- development
- staging
- production
Then in each of the non-common modules import the common variables, and set your DJANGO_SETTINGS_MODULE depending on the environment. virtualenv makes this particularly easy.
Here's a writeup by Zachary Voase, who I've had the pleasure of working with more than once:
http://blog.zacharyvoase.com/2010/02/03/django-project-conve...
Here's what myself and most people see: http://cl.ly/2SzP
Interestingly, if you search for "cussbird" it will correct you to "cursebird": http://cl.ly/2TPX
I'm not logged in, and people in the U.S. see the same results.
Bingo?
Angles. Angles including Ron Conway.
If it's any consolation, I like the final iteration the most.
After almost a minute of figuring out how I can fit what I want to say into your pre-structured dialog, I gave up.