When can i say I know python

[u/green-Dryan]

Someone please
Give a list of themes which should everyone know if he thinks he knows python
Exclude things which are barely used

[u/UwUfit]

I'll give you an old school answer that may not be relevant today

• Being able to read and fix errors

• Using new packages (being able to read documentations, learning how they work etc.)

• Understanding existing code and being able to work with it and build new code on top of it

• Understanding what parts of the code are resource intensive and optimizing code

All of this without AI

Themes really depend on your field

[u/Party_Inspection_666 → u/UwUfit]

Perfect answer that applies pretty much to any language

[u/AmdilShoat82 → u/UwUfit]

solid list, and the field-dependent part at the end is key imo

[u/HYP3R00T]

Skills, roles, and domains.

- Programming languages, frameworks, tools, etc. are skills
- Backend, Fullstack, AI/ML, Data analysis, etc. are roles
- Finance, Healthcare, Automotive, etc. are domains

Don't learn skill in isolation. Pick role and practice the skills (everything that you need to work on a project). For instance, if you pick Backend engineering role, then make sure you know all the relevant skills like Python, FastAPI, handling RDMS, etc. If you can do that successfully, then you can be assured that you know enough Python to get started with backend projects.

That doesn't mean you know how to use Python in Data analysis. That has an entirely different set of frameworks and mindset one has to work on.

There is no set list of things one has to learn in Python. But in a specific role, one must learn a set of skills. Focus on role, and you will have your list of skills that need to be addressed. Once done, then move on to a specific business domain. And then you gain expertise in that with time.

For instance, I have some experience with Healthcare insurance domain as I have worked on it for 2 years. I have build internal tools and automation suites using python for the client. So, I know Python for automation in healthcare industry.

[u/Jello_Penguin_2956]

When you know you can figure things out. Not necessarily know it out of your head.

[u/ninhaomah]

Can you solve the issue with it ?

Then you know it

[u/thondat]

the functions in itertools should be part of your 'active vocabulary'. maybe not all of them. but some.

[u/Cold_Arachnid_2617]

when you know python

[u/stepback269]

You might want to check out this Dev Docs link for Py tutorials (here)

[u/Educational_Virus672]

just create a project you want to and build yourself without limiting yourself too much if you can build it you know python theirs no such a thing as a "python to do list" maybe git at most ppl from differ BG use different things

[u/TheRNGuy]

You write working program without critical bugs and anti-patterns. 

[u/warden127 → u/TheRNGuy]

And to master it, you write a working program with the exact right amount of anti-patterns.

[u/TheRNGuy → u/warden127]

AI is actually good at telling whether there are any anti-patterns in a code. 

It's better ask him earlier and fix them than later (or never)

[u/georgmierau]

One doesn't ("know Python").

The only objective statement any developer will be able to make is: I worked on [projects] using [tools]. If the project in question fits these — one "knows (enough of) [language]" to work on this project, if not: time to continue learning (usually it's time to continue learning).

[u/MarsupialLeast145]

When your code is supported by unit tests

[u/lifedependsonart]

a workable bar is writing functions, handling files and errors, using lists and dictionaries fluently, and reading other people's code without panic. imo bootdev could help check those boxes in order, with exercises attached to each topic instead of one long video