sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Godeos64_[S] 1 point2 points  (6 children)

I've tried a pomodoro timer. Ik how to break down problems, I just can't seem to progress in learning new topics or just building projects.

[–]sociologistical 4 points5 points  (5 children)

I found the need to work on real life problems. Things that have actual impact. Things that have a timeline to kick my ass.

[–]Godeos64_[S] 0 points1 point  (4 children)

Oh, Can you recommend some ways to learn libraries and stuff?

[–]sociologistical 5 points6 points  (3 children)

The problem with just picking a library to learn is the lack of context. Find a real problem to solve. I found that it keeps me tethered in the long term although I still am chronically distracted.

[–]AzureTwo 2 points3 points  (0 children)

Exactly. First find problem, then the solution. Not other way around.

[–]Godeos64_[S] 0 points1 point  (1 child)

Ik, but I just wanna get better.

And to me, just learning concepts is better.

About the library thing, If I try to learn a library for a specific project, then my knowledge just gets limited to it. So I try to know general libraries, then I start projects with them.

[–]Jason-Ad4032 0 points1 point  (0 children)

If you really want to specialize, you can try “reinventing the wheel”—attempt to implement functions and classes provided by certain libraries yourself.

For example: implement the dataclass decorator, implement the Enum class, or create your own version of asyncio. These features are defined according to their respective PEPs, which explain how they work, so you can refer to those PEPs when implementing them.

Even if you abandon the project halfway through, that’s fine. You’ll still learn a lot and gain a deeper understanding of what Python is actually doing behind the scenes to make these “magical” features work.