ironically one of the reasons i've entertained the idea of quitting twitter is b/c of annoying things that showed up in my feed from the author(and others). But I just un-followed him instead. the technical things I'm interested in, but I dont care for the politics so much.
great advice here, I would have liked to see some code examples for #4, b/c I am currently struggling with a ng codebase where the controller are doing way too much in my opinion. using ui-router helps some, but, I would love to see more ways to keep the controllers slim.
"stake holder" is not mentioned once in this article. PM tools, help with the communication that leads to trust between the doers, and those putting the cash up for it. it's either use PM tools, or suffer micro management hell and lack of focus until the $$ runs out.
I can sort of empathize, with having too much focus on the planning/pm process, I've been there, done that, it's a potential problem. But not a reason to disregard the tools or the need for them.
There's flaws in accounting processes too, but I believe sane people would all agree that accounting processes are needed.
If there are problems in the way you are measuring, deciding that measuring is bad is just silly.
(1) Men and women of full age, without any limitation due to race, nationality or religion, have the right to marry and to found a family. They are entitled to equal rights as to marriage, during marriage and at its dissolution.
(2) Marriage shall be entered into only with the free and full consent of the intending spouses.
(3) The family is the natural and fundamental group unit of society and is entitled to protection by society and the State.
It seems the UN is against gay marriage so that's where the next witch hunt should go
my $$ is on a node runtime, assuming google is interested in increasing the # of people that use it. python 3 would be nice but it probably wont get people interested like node would.
> I believe there is a plugin for working with the App engine.
You believe it, I tried it, and it failed, the non-rel project isn't even under active development anymore. And if appengine had not introduced cloudsql as an option, django would be useless on that platform.(IMO)
> And also Django is modular enough that you only need to use the parts you require.
As I said before, without the django orm, there's not much useful stuff left in django that will work without it. There's better request routing options than regex based IMO. There's better form libs and validation libs. There are certainly better performing template engines, what is left of django that's a better choice over something else?
> b) There will be consistencies between the libraries.
depends
> c) Magic things like the Amdin interface will work.
true
the workflow for this particular project seemed to go like this...
* get requirement from client
* search google for plugins/modules/etc
* choose some
* try to get them to work
* use them or fork them or find others
which to me seems a pretty roundabout way of getting something accomplished if you already know what needs to be done. it doesn't feel like programming, it feels to me like assembling things and testing/hoping there are no issues. I'd rather be programming.
i just finished up a django project that also had "8 million" dependencies, the difference was a lot of them started with "django-" and some dependencies I would have liked to use were off the table.
> five years ago in Python you put together a lot of small pieces (and e.g. Turbogears was a nominal framework that was actually a lot of small libraries being composed together).