this post was submitted on 02 Feb 2024
9 points (100.0% liked)

Programmer Humor

32400 readers
432 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 9 months ago (2 children)

I would swap Python with C++. Constantly dealing with stupid runtime errors that could’ve been easily captured during compile time.

Did you forget to rename this one use of the variable at the end of the program? Sucks for you, because I won’t tell you about it until after 30 minutes into the execution.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

you need a linter, bro

when integrated into the editor it'll highlight stupid mistakes as they're typed

I recommend Ruff for real time checks, and pylint if you need a comprehensive analysis.

[–] [email protected] 0 points 9 months ago (2 children)

sure, but thats just outsourcing the problem.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

As if that's a bad thing... it means you're not locked in with a tool you don't like and the language itself doesn't dictate your workflow.

There's very little benefit and a lot of potential problems in using a single tool for everything.

[–] [email protected] 1 points 9 months ago

It's also a solution...

[–] [email protected] 0 points 9 months ago (1 children)

My brother. That's why you do unit tests.

[–] [email protected] 1 points 9 months ago (1 children)
[–] [email protected] 1 points 9 months ago

👆 definitely linting first 👆

finding errors as you type is even better than finding errors at compile time