Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Programming

Journal Helmholtz Coil's Journal: Perception Of Python 2

This one's been bothering me for a while, and I'm sure I'm not alone. I do a fair amount of software development as part of my job-at first it was just to support projects I was working on, but more and more I get the call when others need work done. I've even got "Software Developer" tacked on to my job description/title, but I still don't think of myself as one.

Anyway. Most of the development I do is in C for embedded devices, but I also get to use Python a fair amount as well-I especially like using it when I'm working on a new algorithm before I hard-wire it in C. The issue I'm constantly facing is the perception 'round the workplace that somehow working in Python != software development:

"It's just a script, right? Like a batch file?"

Bothersome mostly because the perception is that it shouldn't take me more than an hour or two for even the most complicated program / algorithm. I've tried showing the Python code to the Powers That Be but it still reads like a batch file to them. Any insight?

This discussion has been archived. No new comments can be posted.

Perception Of Python

Comments Filter:
  • Comment removed based on user account deletion
    • Thanks for the ideas, I think I'll try the "prototype" approach you suggested. You know, the funny thing is I've delivered compiled executables a few times with the same results. The last time the higher-ups were "surprised it took so long," because I'd done a completely unrelated Tcl/Tk compiled GUI for 'em years ago and they thought I'd only have to change the name or something. The weirdest part is my boss is always saying how glad he is I like to do the software, because he remembers how painful Fort

According to all the latest reports, there was no truth in any of the earlier reports.

Working...