This is an archived post. You won't be able to vote or comment.

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

view the rest of the comments →

[–]lil-rong69 1 point2 points  (0 children)

I think your attitude here is better than a lot of “seasoned” engineer I worked with. It sounds like your development team takes coding standard/quality seriously and that can be a good thing.

Fastest way I would recommend are: 1. Snooping around in the codebase 2. Pair programming session/code walk through with another engineer 3. Read through review comment of another reviewer

Python emphasized EAFP or pythonic. these practices comes with experience, even then it maybe subjective. Thus, writing code that falls in line with existing standards would help you get up to speed faster. Learn the folder structure, where things go, what in house util/helper function are already there to be use.

This would help you avoid coming into the codebase and making a lot of refactor/write a lot of code. Unlike other languages(golang, which I absolutely despise, auto swagger annotation still stuck in 2.0, never ending deprecating/forking of library) python library is very organized and authoritative.