On Sunday 23 Aug 2009 7:24:12 pm Roshan Mathews wrote: > Okay, looks like I got your goat, didn't think it was > possible or I would have been more circumspect. So let me > start off by saying I meant no offence, not in the past and > not in the future in my discussions related to this website. > But politeness only makes it more difficult to talk about > things, so please don't be offended at the following > remarks, as it's just a fast technical response to the > website. If you actually are offended I hope I can make > amends by buying you a cuppa coffee when we meet at the > Pycon in September. :) > > So, then now I can call out your bullshit.
feel free > > 1. all files which the projects depends on should be in the > repository. Because: > > a. it's totally irrelevant whether you use these files > for other projects, or if it would break things on > your computer. I don't care and neither does > anybody else. everybody else cares - if you want to be spoon fed - just ask > > b. anyone setting up the code on their machine should > be able to run it by just cloning the repository. no > > c. if and when you do upgrade the third party > libraries/themes, you will have to add a note to the > commit log saying you did upgrade them and for what > reason. no > > d. even binaries like images should be in the > repository, what shouldn't be in the repository are > generated files like the .pyc ones ... use .hgignore > to ensure that they don't show up in your hg st > commands. Add the .hgignore to the repository. all relevant images are there > > 2. the app is not media agnostic, the app is what people > see on the website, so it's pointless to say that this > way it is flexible because if someone is playing with > new images/styles/colors, they try that out and push you > an update/patch. bullshit > > 3. I already have it running using sqlite3 on my machine, > and the default settings.py in the repository should be > the same too, so that people don't have to install > and/or configure postgresql on their machines. Python > 2.6 comes with SQLite and that means that that is the > most obvious choice for having in the repository. bullshit > > 4. People in your lab might have high pain thresholds from > working with crappy software, it is not crappy software > but that doesn't mean that > you inflict that on the world at large. If there is a > simpler way to do it, then you better give a technical > reason why you wouldn't want to do that. more BS > > 5. Code never gets clean in time. It either is clean from > the start with a conscious effort to keep it that way or > it stays messy. I say this now, because it can still be > done. Six months from now the only option will be to > start over from scratch. it looks like you have never written production code > > 6. A more delicate flower than me would have wilted under > the charge of spoonfeeding, but that's not what I want, > what I want is to work on the site without having to > wade around in ankle deep ... muck, lets say. then why are you suffering where any django novice would be contributing? > > 7. I can work with django/firebug, so thanks but no thanks > on the pithy unhelpful advice, also when a coworker > points out that your work is messy, it's not very useful > to say that 'but see, my earlier work was messy too, and > others have messy work too'. have you ever written production code - url please. > > My two cents, please feel free to disagree, but please don't > walk away with your ears plugged saying 'nanananana...'. > > Roshan > > PS: remember the coffee is on me, take a deep breath and > flame me if you must, but don't get all upset. :) > > PPS: the site doesn't work, another friend tried to create > an account and failed. I see from the logs that a lot of people have tried to create an account and succeeded > > PPPS: I can add the media files to the app at my end and get > hg to ignore them, but I'd rather do that only if I'm > sure that you aren't going to add all dependencies to > the repository. I am not going to add them - learn django and stop whining. > _______________________________________________ > To unsubscribe, email [email protected] with > "unsubscribe <password> <address>" > in the subject or body of the message. > http://www.ae.iitm.ac.in/mailman/listinfo/ilugc -- regards kg http://lawgon.livejournal.com _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
