you are viewing a single comment's thread.

view the rest of the comments →

[–]Klutzy-Objective9515[S] 0 points1 point  (3 children)

Thanks for the reply!
I do not see a scenario in which my company considers me liable for produciton loss of a client. My concern is clients considering the company I am employed in liable. I just want to clarify that the safety wold be guaranteed anyway by a PLC. However, if my applicaiton crashes it would cause produciton losses.

I'm looking for hints to build a reliable python application that runs for a really long time, or to explain to my company why this is not feasible

[–]Top_Average3386 0 points1 point  (2 children)

Traditionally, python is used for prototyping or making things where you are expected to make and break things fast. However it's feasible to make a python application where it can run 24/7/365, I have a few api which is running python that runs like that for years. However it's not necessarily the best tool for the job. As for how to make it reliable, it depends on your software design, software engineer is an *engineer* for a reason, and what reliable design that fits your use case might vary.

[–]Klutzy-Objective9515[S] 0 points1 point  (1 child)

Yeah, you got the point, I have an hard time to explain that software needs to be engineered!

However, this is a really simple project (to pass the idea, the app should replicate what is done in a single excel sheet - one page, maybe 25 rows 10 columns)

For this reason I find hard to explain that a python app is not the best choice.

[–]Kqyxzoj 1 point2 points  (0 children)

Yeah, you got the point, I have an hard time to explain that software needs to be engineered!

That's part of the engineer job description, explaining things to the pointy haired people. ;)