Subject | Re: converting raw images from Canon EOS 600D |
From | Eric Stevens |
Date | 12/01/2013 09:56 (12/01/2013 21:56) |
Message-ID | <a6ul99d0qg6ttigh1q2p9phkkcfci6lcca@4ax.com> |
Client | |
Newsgroups | rec.photo.digital |
Follows | J. Clarke |
J. ClarkeFloyd didn't say "architects, engineers, etc have to write a lot of code to do their jobs" but he did say they have to learn programming. This is a question within my sphere of competence. If you are an architect or engineer who doesn't understand programming you can't direct those people who develop the computer programs which play an increasingly important part in what the professions do today. --
In article <2013113018523314486-savageduck1@REMOVESPAMmecom>, savageduck1@{REMOVESPAM}me.com says...SavageduckJ. Clarke
On 2013-12-01 02:25:27 +0000, Eric Stevens <eric.stevens@sum.co.nz>said:Eric StevensSavageduck
I first learned Fortran (II it was) in 1961. I really only gave up on serious programming about 7 years ago.
Aah! FORTRAN, I started out in punchcard heaven back in 1971, as just one of the myriad things I was doing back then. I was also fooling around with physics, math, anatomy & physiology, micro biology, chemistry (physical & organic), and a few other obscure trains of thought like archeological anthropology because it was suggested to me.
...but somehow I have managed to stumble through life without actually being compelled to write any sort of code. Not in micro-biology or path labs, or during 25 years in Law enforcement.
For me it was WATFOR, then I discovered APL and wondered why anybody would want to use FORTRAN. But I did get paid to write code for 10 years, five of it incidental to engineering (I was the only engineer in the place who did programming) and five of it for a software developer. But I have to say that the notion that all architects, engineers, etc have to write a lot of code to do their jobs is just plain bullshit.