Re: Django advocacy in a commercial environment
Rob Hudson <[EMAIL PROTECTED]> writes: > Python and Django wouldn't be my concern when hiring new employees > since they are easy to learn. It's all the other stuff that comes > with web development that together is harder to find (eg: valid > (x)HTML, CSS, Javascript, database, source control, unix/linux, HTTP, > etc.) I agree with this. I'd be happy to teach anyone django and python. But finding people who know about CSS differences between browsers - now that is hard. -- Nic Ferrier http://www.tapsellferrier.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django advocacy in a commercial environment
On Jul 20, 2:09 am, "Jon Atkinson" <[EMAIL PROTECTED]> wrote: > I don't mean to pry, but at your workplace have you had any difficulty > hiring into Python/Django roles at your company (compared to PHP)? Do > you get less applicants? A better quality of applicant? We only have 2 developers and because of Django, that's all we need. We hired the 2nd awhile ago and he had some Python experience and picked up Django very quickly. The good documentation helped a lot in that regard. That in itself is another point -- a home grown CMS in PHP with no docs would have taken much longer to figure out and get up to speed with. The MVC model, I think, would also help. As the new employees are learning they can work in something less technical like templates. As they learn, they can then do views. And the senior devs can do things like model design, middleware, new features, whatever. Python and Django wouldn't be my concern when hiring new employees since they are easy to learn. It's all the other stuff that comes with web development that together is harder to find (eg: valid (x)HTML, CSS, Javascript, database, source control, unix/linux, HTTP, etc.) -Rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django advocacy in a commercial environment
On 20-Jul-07, at 2:39 PM, Jon Atkinson wrote: > I don't mean to pry, but at your workplace have you had any difficulty > hiring into Python/Django roles at your company (compared to PHP)? Do > you get less applicants? A better quality of applicant? my experience is: no qualified applicants - they have to be trained/ learn on the job as far as python/django is concerned -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django advocacy in a commercial environment
Thanks for your reply, Rob. Personally, the reason we're looking to push Django is that our business needs very much match a statement Simon made in the talk I mentioned above: 'Web development on journalism deadlines' (that might not be entirely accurate). I was also considering putting together a report, but we all know the problems with code metrics - do we measure LoC, speed of development, or the very nebulous 'simplicity' concept which will be quite difficult to communicate to management. I don't mean to pry, but at your workplace have you had any difficulty hiring into Python/Django roles at your company (compared to PHP)? Do you get less applicants? A better quality of applicant? Cheers, --Jon On 7/19/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > > On Jul 19, 1:19 am, "Jon Atkinson" <[EMAIL PROTECTED]> wrote: > > If anyone has any good resources which show off the power of Django > > (and by association, the benefits of PHP), then please share them with > > us. > > Where I work we migrated away from PHP to Django with great success > but it depends on your environment. > > For us the Django admin was a huge factor since we have teams entering > content and the default Django admin was way better than anything we > had going so far. > > There are some performance articles and blog posts, for example: > http://wiki.rubyonrails.org/rails/pages/Framework+Performance > > We benefitted from the Django workflow with its built-in web server. > > There's also the fact that Django is improving everyday which > translates into free new features or things that were hard to do are > easy now. For example, databrowse or djangosnippets. > > And we love Python and also love our jobs more because of the > switch. :) > > Those aren't really resources for you but depending on your in-house > requirements it's not hard to find resources online to help guide the > decision. When I had to convince my superiors of the choice, I wrote > a PDF document looking at the best choices in each language (Ruby, > PHP, Python) and Django won out for our particular needs. > > -Rob > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django advocacy in a commercial environment
On Jul 19, 1:19 am, "Jon Atkinson" <[EMAIL PROTECTED]> wrote: > If anyone has any good resources which show off the power of Django > (and by association, the benefits of PHP), then please share them with > us. Where I work we migrated away from PHP to Django with great success but it depends on your environment. For us the Django admin was a huge factor since we have teams entering content and the default Django admin was way better than anything we had going so far. There are some performance articles and blog posts, for example: http://wiki.rubyonrails.org/rails/pages/Framework+Performance We benefitted from the Django workflow with its built-in web server. There's also the fact that Django is improving everyday which translates into free new features or things that were hard to do are easy now. For example, databrowse or djangosnippets. And we love Python and also love our jobs more because of the switch. :) Those aren't really resources for you but depending on your in-house requirements it's not hard to find resources online to help guide the decision. When I had to convince my superiors of the choice, I wrote a PDF document looking at the best choices in each language (Ruby, PHP, Python) and Django won out for our particular needs. -Rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django advocacy in a commercial environment
Oops, a quick edit - that last sentence should of course read: ...'benefits *over* PHP'... --Jon On 7/19/07, Jon Atkinson <[EMAIL PROTECTED]> wrote: > Hello, > > Having just finished a couple of large projects in PHP4, our > department (of 5 programmers) is looking to move to PHP5 - but me and > another on the team have been pushing towards using Python/Django in > future. > > While everyone sees the benefits of moving to Python (namespaces! > enforced syntax! and more!), it would help us immensely if we could > find some resources to wow the other programmers here. > > I was fortunate enough to attend Simon Willison's excellent talk at > LUGRadio Live 2006, which really inspired me to start using Django, > but short of inviting him here (and probably paying him), I'm not sure > I could recreate that kind of convincing argument myself. Which leaves > us with online resources, presentations, screencasts and suchlike. > > If anyone has any good resources which show off the power of Django > (and by association, the benefits of PHP), then please share them with > us. > > Thanks, > > --Jon > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Django advocacy in a commercial environment
Hello, Having just finished a couple of large projects in PHP4, our department (of 5 programmers) is looking to move to PHP5 - but me and another on the team have been pushing towards using Python/Django in future. While everyone sees the benefits of moving to Python (namespaces! enforced syntax! and more!), it would help us immensely if we could find some resources to wow the other programmers here. I was fortunate enough to attend Simon Willison's excellent talk at LUGRadio Live 2006, which really inspired me to start using Django, but short of inviting him here (and probably paying him), I'm not sure I could recreate that kind of convincing argument myself. Which leaves us with online resources, presentations, screencasts and suchlike. If anyone has any good resources which show off the power of Django (and by association, the benefits of PHP), then please share them with us. Thanks, --Jon --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
