On 15/11/2018 2:28 PM, Joel Mathew wrote:
The last point is a bit of a sore for me. I'm well versed with some
other languages including perl, C, and javascript. Python seems to
have "pythonic" ways of doing stuff that's at loggerheads with all
other languages. Is there a single resource to learn the pythonic way
of doing things?
Not sure about a single resource for Python. For Django however, there
is Two Scoops of Django which claims to (and I believe) aggregate best
practices for the web framework.
There are lots Python gurus who do presentations at PyCons around the
world. Plenty of blogs and tutorials as well. Raymond Hettinger comes to
mind.
Google python best practices and there are heaps to choose from. You
should pick up a sense of it by scanning a few of those pages.
Like, say for perl, there's Larry's books, which provide a solid
foundation for best practices.
Sincerely yours,
Joel G Mathew
On Thu, 15 Nov 2018 at 08:49, Ryan Gedwill <ryangedw...@gmail.com
<mailto:ryangedw...@gmail.com>> wrote:
No problem!
Also as a side note to the point that you heard django is slow...
Django is extremely scalable, which of course requires speed.
It’s probably the most popular web framework among startups of any
magnitude (at least from what I’ve seen) by a mile.
Django certainly may require some extra optimization compared to
something like ASP.NET <http://ASP.NET>, just like scaling any
python software, but there are ways around a lot of it that are
well understood.
Instagram and Venmo are written in django, which is proof that it
can be scaled with the rest of the big players in the industry.
There are certainly problems with scaling python and Django, a
perfect language/framework doesn’t exist, but there are benefits
to both python and Django that can be worth the tradeoff.
In addition to the fact that both Django and python are so
flexible and stay up to date with modern trends as well as any of
their competitors, I always suggest learning them compared to the
other options out there. Just don’t let python get in the way of
writing good code, because as a beginner it’s really easy to
forget best practices with it.
Sent from my iPhone
On Nov 14, 2018, at 6:46 PM, Arturo Fernandez <afern...@gmail.com
<mailto:afern...@gmail.com>> wrote:
Thanks :)
On Wednesday, November 14, 2018 at 9:41:35 PM UTC-5, Ryan Gedwill
wrote:
I live in the SF Bay Area and there are no shortage of jobs
in Django. It is true there are also plenty of jobs in Node,
but you can’t compare a framework to a backend language. I
see far more python jobs than node jobs.
2 things to keep in mind though (for reference I’m a
python/Django dev but have experience in node and c# as well):
1. Just because something is very popular doesn’t mean it’s
the easiest to get a job in. There may be more python/JS jobs
out there, but there are also way more people applying to
them. There are plenty of .NET jobs out there, and far less
entry level developers who are looking for them. Nearly every
single entry level developer is looking for those python/JS jobs
2. Often times the language and framework you’re experienced
in doesn’t matter. I recently had an interview for a Go
position, and I was allowed to pick which language I wanted
to do the interview in. Most web development jobs are looking
for your understanding of general software and web
development principles. If you understand html/css/js, sql
databases in regards to MVC architecture, MVC architecture
itself, and REST API’s and requests, it probably won’t matter
what language as long as you can prove it. Knowing the
language and framework of the company you’re applying to is
kind of just brownie points and improves your chances. If I’m
amazing at django and web development but don’t know the
language being used, I’ll generally be chosen over someone
who’s shaky on web development who uses the same language as
the company
Sent from my iPhone
On Nov 14, 2018, at 6:18 PM, Arturo Fernandez
<afer...@gmail.com> wrote:
Hello community, today someone at work told me to bare in
mind which tech I use in terms of profitability. As a
backend language, there is no doubt that I'll use Python,
however I'm doubting about the framework, whether I should
use Python or not for web.
I heard that Django is kind of slow, and also there amount
of jobs are decreasing. Is that true? I initiated my web
experience with Node.js, but I don't want to continue it due
to the instability. A friend recommend me .Net, so I have
all this kind of doubts in my head. Can someone help me
clear my mind? This is probably the best/not the best place
to ask it but I need some advice :/
Thank you
--
You received this message because you are subscribed to the
Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at
https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/df1cf01f-a911-493c-aca4-e5a6ac3931d1%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/df1cf01f-a911-493c-aca4-e5a6ac3931d1%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the
Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to
django-users@googlegroups.com <mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/df2eb30f-e34a-40d5-a356-f83850cd246a%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/df2eb30f-e34a-40d5-a356-f83850cd246a%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/93AAA037-BE45-4A29-A9F7-5EA56DD816BE%40gmail.com
<https://groups.google.com/d/msgid/django-users/93AAA037-BE45-4A29-A9F7-5EA56DD816BE%40gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAA%3Diw__EK_Jfa%3DRSudyLvvZPsrvtaUPeQwsaQchLnu1PweCiEA%40mail.gmail.com
<https://groups.google.com/d/msgid/django-users/CAA%3Diw__EK_Jfa%3DRSudyLvvZPsrvtaUPeQwsaQchLnu1PweCiEA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/71816da9-e1ad-52c4-cc4e-3b7e03de5a55%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.
