Can You Solve This in Python?
Here is A Basic Python Question! DjangoSeries Episode # 02
Are you Full Stack Developer?
What, btw, is A full Stack Web Developer? Answer: Aha! Of Course! is a person who can develop both client and server software, simple like that!
Well, At the last 2 years I have taken Python Course, and here is a new one:
I am not a full-stack developer, yet, but here is my First Site in Django:
https://j3djangoapp.herokuapp.com/In the next episode of this series I will teach you how to Create your website with this award-winning template: Django!
See you around!
Bye!
BTW, thanks to and all my respect Lira, A Real brazilian Harry Potter in Python!
👉 git
Credits & References
Python Django Tutorial: Full-Featured Web App by Corey Schafer
Related Posts
Related Posts
00#Episode — DjangoSerie — Django Intro — How To Build your First App in Python Django Framework — DjangoSeries
01#Episode — DjangoSerie — Django MTV In VS Code — How To Install Django Inside Virtual VS Code
02#Episode — DjangoSerie — Can You Solve This in Python? — Here is A Basic Python Question! (this one :)
03#Episode — DjangoSerie — JUNGLE-DJANGO Webpage! This Is My New Django Netflix Clone Page!
04#Episode — DjangoSerie — A Django Blog In VS Code — Quick Start! — Part_I
05#Episode — DjangoSerie — A Django Blog In VS Code — Database, Migrations & Queries — Part_II
06#Episode — DjangoSerie — A Django Blog In VS Code — Bootstrap, Tailwind CSS — Part_III
07#Episode — DjangoSerie — A Django Blog In VS Code — Forms & Validations — Part_IV
08#Episode — DjangoSerie — A Django Blog In VS Code — Login & Logout — Part_V
09#Episode — DjangoSerie — A Django Blog In VS Code — Upload Profile Picture — Part_VI
10#Episode — DjangoSerie — A Django Blog In VS Code — Update & Resize Picture — Part_VII
11#Episode — DjangoSerie — A Django Blog In VS Code — Class-Based-View & CRUD — Part_VIII
12#Episode — DjangoSerie — A Django Blog In VS Code — Posts Pagination & Quick DB Population — Part_IX
13#Episode — DjangoSerie — A Django Blog In VS Code — Self-Service Django Password Reset — Part_X
14#Episode — DjangoSerie — A Django Blog In VS Code — Heroku Deploy — How To Push Your Site To Productio — Part_XI
Read this article by Nayan:
Is Django still good?No. It’s better and in many cases it’s probably the best. Django is a fantastic framework with thousands of plugins aka apps and has a huge developer community. Whenever you find a problem, you’ll get a solution from SO, blogs and other resources. You don’t like the way Django handles a particular feature? No problem, you can customize each and everything in a very natural way. It was very well designed as a result core concept of the framework didn’t change over time. So if you’ve learned Django 1.1 a long time ago, you’ll be able to start with 1.11 very easily. From https://www.quora.com/ by Nayan
Another good articles by Phillip Oldham
What is Django good at that Flask isn't?Django is good at being able to quickly bootstrap a project. It is a “batteries included” framework: the built-in code generation tooling, database library, templating system, admin website, and testing system help you get a project started easily and lay down the basics very quickly… to the point where you hardly write any code to have a fully working initial system. Django has a powerful plugin system and a plethora of great plugins. Developers can quickly build complex systems without having to get too deep into the inner workings.However, these features can also be problems. If your project doesn’t fit within Django’s scaffolding, with the way Django defines how things should be built, what tooling should be used, you can find yourself impeded by it. It can feel a little bit “paint by numbers”: you generate an app, fill in the blanks, and something is working… but maybe not quite the way you wanted it to. Similarly with plugins; you must follow their guidelines to make them work the way they have been designed. If you need to veer out of their defined way of working, you’re gonna have a bad time of things.Flask is “bare bones”, focusing only on the “web” part of the stack: requests, routing, and responses. You have to do more up-front to get things working, but you’re in control of everything. No “filling in the blanks” with Flask; you’re writing raw Python to do exactly what you need to do — no more, no less. You don’t have to use the prescribed database library, templating system, testing tools… you not even required to have them. Every choice is yours.Flask also has a plugin system, though with fewer plugins than Django. However, those plugins are a lot more focused on fleshing out the features of Flask itself, rather than adding new features that are already available from other libraries. These plugins help move Flask closer to Django’s “batteries included” model, but with one key difference: you can include only the ones you want/need.Both frameworks have their place, their advantages. Developers should try to avoid the… “religious” undercurrents of our craft, and focus on using the right tool for the job. I personally prefer Flask to Django, as I prefer working in a more function-focused style with Python (modules, functions, and composition rather classes, hierarchies, and inheritance). However, I would never discount Django as an option without reviewing requirements of the project at hand.from https://www.quora.com/ by Phillip Oldham
Have the confidence to fail. Persistence is key.
(Quora)
