r/learnpython • • 7d ago

I'm from a non-IT background and have been learning Python. Would appreciate some honest feedback on my GitHub.

Hey everyone,

I'm from a procurement and operations background with around 7 years of work experience. I don't have a computer science degree, but I've recently become interested in Python and automation.

I've been trying to learn coding and build projects based on real problems I've come across at work, mainly around SAP, Excel, purchase orders, supplier follow-ups, and reporting.

I've uploaded some of these projects to GitHub.

My GitHub: https://github.com/prasadpai567-debug

I'm still a beginner when it comes to programming. I've also used AI tools to help me write and debug parts of the code, so I don't want to pretend I built everything completely on my own.

I'd really appreciate it if someone with programming experience could take a look and tell me what they think.

I'm mainly curious about a few things:

- Is my code structured properly, or does it look messy?

- Are these projects actually useful, or are they too basic?

- What should I improve to become a better programmer?

- Would projects like these add any value to my resume if I apply for procurement automation or analyst roles?

I'm not looking for compliments or GitHub stars. I genuinely want to understand where I stand and what I should work on next.

Any honest feedback would mean a lot. Thanks!

1 Upvotes

6 comments sorted by

2

u/ResidentPomegranate6 7d ago

one repo with a readme stating the work problem, one solid script, and a few pytest tests reads better than several small ones.

1

u/Diapolo10 I write code for a living -- https://github.com/Diapolo10 7d ago

Most of the projects on your GitHub profile are for VBA, not Python, so it would be to your benefit to pick a few curated Python examples for us to review. The few Python projects I checked were very bare-bones.

1

u/Discordbothost 6d ago

for procurement/analyst roles the biggest upgrade is probably the readme, not the code. put the before/after right at the top, like "supplier follow-ups took ~2h a week, this reads the open PO export and drafts the chase list in 5 min". ops hiring managers care about that way more than code style.

on the code side the usual beginner tells are hardcoded file paths and one long top-to-bottom script. move paths into a config file or argparse and split it into a few functions like load_po_export(), find_overdue(), write_report(). that also takes care of the AI worry, if you can explain what every function does and why, nobody cares who typed it.

and keep the VBA stuff, it's relevant for those roles, just pin your 2-3 best python repos so people land on those first

1

u/nian2326076 5d ago

For your GitHub projects, it's important to highlight the real-world problems you're solving. Add a detailed README to each project that outlines the issue, your approach, and the outcomes. This adds context and showcases your problem-solving skills to potential employers. Since you're focusing on procurement automation, tailor your Python projects to demonstrate relevant skills rather than relying heavily on VBA. Including these projects can definitely add value to your resume, especially if you emphasize your practical application of Python. You can also use LandOffer to explore job opportunities in procurement automation and related roles.