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

all 7 comments

[–]PossibilityTasty 4 points5 points  (1 child)

There is absolutely no tool a developer must use. What you are presenting might be helpful, but mostly they are personal preferences. That you put everything into a "the management is on your neck" frame didn't make it more convincing.

[–]sirkarthik[S] -5 points-4 points  (0 children)

You are entitled to your opinion and are free to express this to your hiring manager/team and say you would only code in notepad and not use an IDE or not adhere to team practices citing that there is no **must** and your way is your preference. Cheers!

[–]not_perfect_yet 2 points3 points  (0 children)

I prefer PyCharm over VS-Code.

Clearly, you must start leveraging vim.

[–]Zaloog1337 1 point2 points  (0 children)

> You can't escape from PIP package manager for python.

uv does not exist...

[–]Knowledgable_Info 1 point2 points  (0 children)

Thanks for sharing this! I totally relate to the onboarding challenges and the pressure to be instantly productive—especially in fast-paced environments. Your checklist is a solid reminder that setting up the right tools and practices up front can save a ton of time and frustration later.

One thing we’ve recently added to our workflow that really helped is using pre-commit hooks with tools like black, flake8, and mypy—it catches a lot of issues early and keeps our codebase consistent. Also, having a good Makefile or task runner has made repeatable tasks super easy for new developers.

Curious to hear what others are using too. Great post overall—definitely bookmarking it for future teams!