3 ms·
I'm a scientist who uses programming as a problem solving tool. Before learning Python, I spent upwards of a decade using Visual Basic. My workplace has mostly
by analog31 13y ago
I'm a scientist who uses programming as a problem solving tool. Before learning Python, I spent upwards of a decade using Visual Basic.
My workplace has mostly C#, whereas I'm not part of the software development team, and am free to choose my own tools.
For me, a problem with proprietary IDE's is that the forced distinction between "development" and "run time" environments encourages centralized development, which invariably becomes bureaucratic. When I need something from the programming department, they hand me a program which I have to carry to the target computer, test, and report back to them on any bugs or further changes. This cycle can take days or weeks if they're busy with other projects at the same time.
In contrast, most of my work happens to be decentralized because it occurs in labs where the physical problem to be solved is located. Some of this work now occurs overseas. Much of it is done on computers that are off-network because the IT department rations connections. Locating the full development tools on each computer lets me quickly write and debug programs. And if I share a program with somebody else, it's not prohibitive for them to learn how to make their own changes. I had a total non-programmer say to me: "I think I found a bug in your code, and fixed it."
My situation is one where I actually have a reason to keep and share my programs in the form of source code rather than as an installable / executable package.
As well, I found Python to be easy for an old geezer to learn, and to write reasonably bug free code. And I love the packages.