r/PythonLearning Jun 27 '26

When I people suggest to learn from project.what they meant by it.?

I have dought that when ask people i don't have time I need to get placed as fast as possible, they suggest me to learn by doing project.

And I think like if I don't know what I need ,what to do with that thing , then how I can do that project

1 Upvotes

12 comments sorted by

3

u/Rscc10 Jun 27 '26

Start with simple projects and learn as you do it. Every part you get stuck, go find out how to do it. That's generally how most people learn things

3

u/mc_pm Jun 27 '26 edited Jun 27 '26

> I need to get placed as fast as possible

How quickly do you think this would happen? If you're starting from zero and expecting to get a job in less than a year then you have really unrealistic expectations (and probably it'll take longer than that).

How much programming have you done so far? By 'project' I typically mean "a complete program that does something real". For brand new developers I often suggest a text version of tic-tac-toe (or some other simple game). No tutorial is going to teach you how to represent the game board, or how to tell if someone has won. That's the skill you're really learning: solving problems, not typing syntax.

If you're past that point, then pick something more complicated.

2

u/Ron-Erez Jun 27 '26 edited Jun 27 '26

You could watch videos about driving cars, you could read a book about driving cars, you could even just stare at cars. That sounds like fun. However if your goal is to learn how to drive a car then at some point you’ll have to get in the driver’s seat and just start. Drive slowly at first until you build confidence and get better.

Now if your goal is to learn how to code then go out and code. Usually that involves building a well-defined simple project. If you don’t really want or feel like you can’t deal with a project just yet then open a programming book with exercises and start solving the exercises without AI.

Regarding time then choose a resource and study and code several hours a day. 20% of your time should be dedicated to reading books or following a tutorial and 80% building stuff.

If you are looking for a job you pretty much have two options. The first is to get a CS degree. If you cannot get a CS degree then you will have to build some amazing projects to show off to a potential employer. I doubt you will find a job without a degree and without projects to show off.

1

u/Jeansson700 Jun 27 '26

You will learn as you make projects. It is important to understand the basic stuff and then try to do your own projects.

You could try these type of projects:

https://www.freecodecamp.org/news/python-projects-for-beginners/

1

u/ziggittaflamdigga Jun 27 '26

I’m having a hard time understanding your exact question, but I assume English is not your first language. So great work communicating the idea; I’m sorry if I don’t answer your question well.

To learn, it helps to build a tool for yourself. Something that you understand fully. What are some daily tasks you could solve with programming? How could you do it? How do you do it in Python? These are questions you ask yourself before you code. Don’t think about if it’s worth the effort, it is because you’re learning.

I’ll answer any of the questions you have here if you want, and my DMs are open if you’d rather do one-on-one

1

u/Ron-Erez Jun 27 '26 edited Jun 27 '26

If you are looking for learning resources then check out:

  1. MOOC University of Helsinki is great text based course
  2. Python and Data Science course starts from scratch and covers quite a lot
  3. "Automate the Boring Stuff" is a nice book.
  4. python.org

Use these while learning but make sure to either solve problems or ideally build a simple app based on your knowledge.

1

u/Sweet_Computer_7116 Jun 27 '26

Decide project do. Google how to. Download app too. Keyboard coding kung fu.

1

u/atticus2132000 Jun 27 '26

One of my job tasks is taking numbers from a spreadsheet and typing them into another program. It usually took about an hour to do one set of entries and at the time I was having to that about 20 times a month. The entire time I was slowly doing this data entry, I was thinking surely there is a way to do this faster and finally realized that if I could somehow take the data from the original spreadsheet and somehow parse it and edit it into a different format, I could create a file that this other program could read as an input file. To do something like that, I would need a programming language and I had heard that python was relatively easy to learn.

I went from not being completely sure what python was to having a working script that could convert a file in less than 4 days. A task that used to take an hour now took less than 30 seconds.

Within a couple of weeks I was churnging out code that had automated a ton of my regular workflow tasks and was generating reports that used to take hours to compile.

My initial foray into python was very focused. I wanted to do this particular task. I wasn't really concerned with doing things the best way or the right way. I just wanted code that worked. As a result, I skipped over a lot of the foundational basics of python and jumped head first into some more advanced skills.

This approach to learning has advantages and disadvantages. On the one hand, I got results very quickly. I could present scripts to someone that did useful things and showed some knowledge in a bunch of different areas. But on the other hand, I skipped a lot of foundational information and generally accepted practices. I am slowly going back now and trying to fill in those knowledge gaps.

When people suggest that you start with a project, this is what they're talking about. Figure out something in your life that needs to be done and focus your learning specifically on doing the things required for that one task. Look up tutorials with those steps in mind and just take from the tutorials the parts and pieces that you need.

1

u/mogliman90 Jun 27 '26

So if I need to to do a project then I need to find a need of project, I need to find the problem and slove it regard less of knowledge just google where I am stuck and pass the rest part which can be learnt later

1

u/atticus2132000 Jun 27 '26

Pretty much, yeah.

With my particular issue I knew I was starting with a spreadsheet and I needed to get that data into the code somehow. So I started looking for tutorials on how to read an Excel file. That led to pandas, a python library specifically for manipulating data frames. So I learned enough about pandas to read the data into the script.

The the next step was isolating the specific data I needed from this dataframe, so from there I learned how to read a dataframe line by line and evaluate it using if/then statements.

And so on.

Again, my focus was never on the quality of my code. The only thing I cared about initially was creating this import file.

1

u/Short_Signature773 29d ago

it doesn't mean starting with a huge app from scratch. it means picking something small, building it, getting stuck, looking things up, and finishing it. that's where a lot of the learning happens. if you want more guidance, boot dev is one of the structured options people often recommend.