[Info-vax] Python for x86?

[Scott Dorsey]

=?UTF-8?Q?Arne_Vajh=c3=b8j?=  <arne at vajhoej.dk> wrote:
>On 4/17/2023 3:00 PM, Scott Dorsey wrote:
>> Now more likely we have SMEs writing code and I hate to say it but this is
>> often a very very bad idea.  "It's okay, I can use Matlab for the database
>> engine!"  I wish I were joking about that but I am not.
>
>"shadow IT" is a real problem. Adhoc hacked code with no
>development process that is impossible to maintain, contains security 
>vulnerabilities, performs poorly etc.etc..
>
>But it is not all types of programming that requires a formal
>development process.
>
>Sure for the major application that are doing something important
>and are expected to live for 10-20-30-40 years years, then it
>should be a given.

I'm not talking about a formal development process with structured 
walkthroughs and unit tests and descriptions of the expected use across
the software lifecycle.

I'm talking about having skilled programmers writing code, sitting next to
and working with subject matter experts.  Instead of the SMEs writing something
up in Matlab and then wondering why it is so slow and doesn't always work.

>But there are other types of programming:
>* the finance person that need to automate some stuff
>   in Excel and do it in VBA
>* the finance person that want to see how various
>   interest scenarios impact the budget and do it
>   in Python
>* the sys admin that need to automate some processes
>   and do it in shell/Python
>* the sys admin that need to move a lot of stuff around
>   as a one time thing and do it in shell/Python
>* the data person that need to export a lot of data from
>   some data sources and load them into a DWH and do it
>   in Python
>* the data science person that need to try out hundreds
>   of different forecast models to find the best model and
>   do it in Python/R/Matlab

Yes, these people should have a Python/R/Matlab expert on hand instead of
going it alone.
--scott

-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."