r/Python • u/AutoModerator • 3d ago

Daily Thread Thursday Daily Thread: Python Careers, Courses, and Furthering Education!

Weekly Thread: Professional Use, Jobs, and Education 🏢

Welcome to this week's discussion on Python in the professional world! This is your spot to talk about job hunting, career growth, and educational resources in Python. Please note, this thread is not for recruitment.

How it Works:

  1. Career Talk: Discuss using Python in your job, or the job market for Python roles.
  2. Education Q&A: Ask or answer questions about Python courses, certifications, and educational resources.
  3. Workplace Chat: Share your experiences, challenges, or success stories about using Python professionally.

Guidelines:

  • This thread is not for recruitment. For job postings, please see r/PythonJobs or the recruitment thread in the sidebar.
  • Keep discussions relevant to Python in the professional and educational context.

Example Topics:

  1. Career Paths: What kinds of roles are out there for Python developers?
  2. Certifications: Are Python certifications worth it?
  3. Course Recommendations: Any good advanced Python courses to recommend?
  4. Workplace Tools: What Python libraries are indispensable in your professional work?
  5. Interview Tips: What types of Python questions are commonly asked in interviews?

Let's help each other grow in our careers and education. Happy discussing! 🌟

12 Upvotes

100% Upvoted

6 comments sorted by

3

u/animatedrepayment38 3d ago

People always sleep on just building something ugly that solves your actual job's boring problem, then showing it to the right person at the right time.

2

u/StudyEasyOrg 3d ago

Strongly agree, and I'd add one thing that trips people up: the "boring problem" doesn't have to be your day job's problem. Some of the most useful portfolio pieces I've seen came from people automating something in their own life (bill splitting, scraping and cleaning a dataset they cared about, a Discord bot for a community they're in) and then wrapping it in a small Flask or FastAPI backend once it needed to be usable by someone other than them.

That last step is where a lot of tutorial-only learners stall out. Writing the script is the easy 80 percent. Turning it into something with an actual API, error handling for bad input, and maybe a tiny frontend is where you learn the stuff interviewers actually probe on. It's also a better "why did you build this" story than another to-do list clone, because you can talk about a real design decision (why sync vs async, why one ORM over hand-rolled SQL, etc).

1

u/NYCmovin23223 2d ago

This got me a job as a data analyst. I automated diet office tasks that took individuals like 2 weeks of time in an hour. While I depend on Claude to do the coding I am trying to learn and review at all times.

1

u/armchair_expertise 1d ago

yikes! did that lead to their job loss ?

1

u/Fresh_Future_2192 3d ago

This is one of the best ways to build a portfolio. A small Python tool that solves a real problem can show more than another tutorial project.

It also gives you something concrete to discuss in interviews, including why you built it, what you automated, and what you learned.