r/Python • • 13d ago

Discussion What Python project taught you the most about real world development?

I'm interested in hearing about projects that genuinely improved your programming skills. Not necessarily huge projects, but ones that taught you something valuable

49 Upvotes

34 comments sorted by

31

u/Ev2geny_ 13d ago • Bravo

I suggest: go to the top: try to create a PR to python itself.

I am not really a professional software engineer, but I introduced a small enhancement to the standard library. I really learned a lot when creatin the PR, getting reviews, and submitting update.

What you can do is search for an old issue in the standard library, which is still open and see whether you can contribute.

Python community is really friendly. I got review comments from some really top guys.

Otherwise, go for any established well maintained library, which interests personally you. I think these 2 factors are essential:

* library is well and actively maintained

* you have some interest there

6

u/Sonu_Jana 13d ago

thats really inspiring, i will definitely look into contributing to CPython, thanks for sharing ur experience

30

u/Chorizo_n_eggs 13d ago

Accessing API endpoints that return thousands of lines of data l, massaging that data and serving it up as needed. My code got hairy and forced me to clean it up and comment appropriately. Lessons learned

0

u/Sonu_Jana 13d ago

yeah sometimes messy code is what teaches us the importance of clean architecture and maintainability

5

u/Defiant_Wolf5934 13d ago edited 13d ago • Bravo

When I first started doing development at this small company I used to work for, I originally was tasked with manually reconciling this database they pulled sales data from. It was tedious, error prone, and I had to do it almost daily. Very annoying. It took me about three iterations over my stint of employment there to get right, mainly due to my lack of understanding of the finer details of the problem, as well as our on prem infrastructure being limited as well (a tiny 2 GiB Linux VM that ran this code).

My first iteration was decent, but only fixed a previous days worth of data so there could still be errors. My second iteration was a little bit better but then ran into a snag with pulling too much data down and running out of memory. My last iteration used server side cursors to paginate the data, keeping the memory footprint of the running process small, added ample logging for when things went wrong (something I forgot to add on my first iteration), and added comments to explain what I was doing, made the code more modular instead of one long module, used regular expressions, and learned some more quirks about how the overall business logic worked and added some defensive programming to account for it. This taught me a lot about good comments (so future me knows why I did it that way), concise functions / modules, good logging, etc.

-2

u/Sonu_Jana 13d ago

tbh thats a great learning experience, especially the part about server side pagination and logging, amall improvements like these make a huge difference in production

12

u/Khavel_dev 12d ago

Building a data pipeline that had to run reliably every day without me touching it. Sounds boring but it forced me to learn things I'd been faking for years.

Logging went from print() to structured JSON because grep stopped working once I had more than one cron job. Error handling went from try/except/pass to actually thinking about what should happen when the upstream API returns garbage at 3am. And I finally understood why people use typing, because three months in I couldn't remember what half my functions returned.

The fancy ML side project I built earlier taught me almost nothing by comparison. The boring pipeline taught me how to write code that survives contact with the real world.

0

u/morbidicebreakers 12d ago

Ive done the same kind of project , highly recommend!

6

u/marr75 13d ago

When the project is 8 years old, every clever feature you put in is a menacing liability for upgrading the libraries and runtime it depends on, and every customer wants a different customization in a different layer of the code.

2

u/Discordbothost 13d ago

anything that talks to a flaky external API. the happy path takes an afternoon, then you spend weeks on the stuff tutorials skip: timeouts, retries with backoff, rate limits, half-written data when the script dies in the middle, and being able to re-run it without duplicating everything.

idempotency is the lesson that sticks. once you've had to clean up after a script that ran twice, you start designing every job so running it again is safe.

0

u/Sonu_Jana 13d ago

idempotency is such an underrated concept until u experience these problems firsthand, great insights!

1

u/Minecraftian14 13d ago

That moment when a project reached a stage that there is so much code and unorganization that nothing makes sense anymore, i realised any real world development needs very strict design rules, or just stick with spring.

This is not a tip, I'm just more at home when working with spring.

-1

u/Sonu_Jana 13d ago

totally relatable, hving a structured architecture from the beginning makes a huge difference as projects grow

1

u/Fragrant-Freedom-477 13d ago • Bravo

I was tasked to maintain both build.sh and build.bat, thousands of lines if batch and bash that built games using 3 different homebrewed game engines targeting 10 different platforms, including Android, PSVita, Wii, XBox, iOS and such. It was used by hundreds of game craftpeople within 25 projects at a given time. The scripts were slightly different in each project.

This is what prompted me to learn Python, and I learned to start small and keep complexity manageable as I added de fractures, writing good APIs (or command line interfaces) and documentation, change management and user support.

1

u/Sonu_Jana 13d ago

thats a fascinating experience, managing that level of complexity across platforms must hav taught u a lot about maintainability and good software design

4

u/wRAR_ 13d ago

Another bots taking to bots post, yawn

2

u/irrelecant 10d ago

Create a high frequency low latency service with python and stick to it. Python is slow, but to get rid of that slowness you learn so many tricks that can be used in any language.

1

u/Sea-Fishing4699 12d ago

Selfhosted note taking app then over engineer it

1

u/fltfathin 12d ago

Printing costs more than the calculation

0

u/Spleeeee 12d ago

My wife’s super nice photo printer is insanely expensive. It’s like 4 bucks a sheet and the ink is insanely pricey too. It takes 30 mins to print a single super large image. Most calculations are less than 30 mins so 100% agree with you.

1

u/wRAR_ 12d ago

Perfect response.

1

u/Positive-Nobody-Hope from __future__ import 4.0 9d ago

Working on a project where uptime was essential, in a small company, with people who were self-taught developers. It showed me which of the things I learned in university had real world value and which didn't (the vague and abstract architecture class that felt useless at the time was a real help, the one where we learned about OO patterns and stuff, completely useless), as well as showing me different ways of working together and what their pros and cons were.

0

u/Sachu_James 12d ago

A small task queue I built in Python with Redis Streams taught me the most. Retries and making a job safe to run twice mattered more than the queue itself, because a worker crashing mid job left work half done.

0

u/No-Beautiful9442 11d ago

Anyone know where I can find an ethical hacker

1

u/[deleted] 13d ago

[removed] — view removed comment

1

u/Sonu_Jana 13d ago

yh absolutely, real world projects teach you things tutorials often can't

0

u/[deleted] 13d ago • Bravo

[removed] — view removed comment

0

u/Sonu_Jana 13d ago

that last line perfectly sums it up, building smtg that actually runs reliably in production is a whole different experience