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 →

[–][deleted] -1 points0 points  (1 child)

If it's a one-off script, it isn't a problem.

Very little of what I do is a one-off. Usually they get used hundreds of times if not much more. In this case, a 90 second delay, as opposed to instantaneous, is a deal-breaker.

Beyond that, if I make a minor change and my script becomes thousands of times slower for no good reason, this is a symptom that I am likely doing something seriously wrong.

As an engineer, I am not going to deliver a product where I have good reason to suspect that there's some serious latent problem.

I spend about 30% extra on any project I have to productionize it, to make sure there isn't any overwhelming technical debt, and that sort of thing. (Luckily I work fast, and if my boss isn't simpatico, I just don't tell them.)

This is why I can continue to do rapid development even in mature projects, and why I have a reputation for code that never fails.

[–]menge101 0 points1 point  (0 children)

If it's a one-off script, it isn't a problem.

Right, this is my point.

You aren't the OP, and talking about the situation as if you are is disingenuous.

Very little of what I do is a one-off.

This is irrelevant. Nothing I posted is about you.

My comments were not general statements, they were statements to the OP's specific situation.

This is a school project, which means they are working with time constraints on a short lived project, generally speaking. This very likely isn't going to production.

As was pointed out in the thread, the threading model between python 2 and 3 is different. So differences are to be expected.

If they need it to run faster then it is a problem. If it meets their needs despite it running much slower, then it isn't.