|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
81.153.90.212
In Reply to: Just making sure posted by E-Stat on March 24, 2007 at 07:28:09:
"With my first job out of college, I was the IT department of a small company. We used a standard package, but I wrote countless modifications to meet our particular business needs. During this period, I supported my own development.A dozen years later, I joined the developer of that package in tech support. When we found bugs in current code, we gave it back to development for correction. When it was found in older versions or in custom modifications, then I fixed it.
Fast forward another fifteen years to present, I now work in a sales capacity.
"
And you refer to yourself as a SOFTWARE ENGINEER, I should guessed. Your commentary on so much stuff did not add up, Software engineering is one of the most mathematical involved endeavours in computing, your aversion for 'numbers' was odd for a software engineer.
Music making the painting, recording it the photograph
Follow Ups:
HowdyAfter working for decades in software engineering I still remember many professional software engineers stopping and gawking when they walked by our offices and asked if we were really talking about Singular Value Decompositions when we were saying SVDs. I don't think many software engineers use all that much math on a daily basis in the industry. They use some specific forms of math informally a lot (e.g. big and little O estimations), but most of them would have no idea what you are talking about when you mention Dedekind cuts or Stone spaces... Heck even numerical analysis isn't taught that thoroughly to undergraduates much anymore either, a lot of people stair at me blankly when I talk about Runge–Kutta methods or Jacobi rotations.
and the enjoyment of working out algorithms to achieve some goal.When I was young and stupid, however, I believed in Julian Hirsch and the value of all numbers. Obsessed with them. I could quote chapter and verse of distortion specs for quite a few receivers, amps, preamps, etc. I had my AR integrated amp measured by Dave O'Brien himself. Got the chart. As a result, I decided that I had to have some Crown gear. Why? Because they had "virtually unmeasurable distortion". Yep, that's what I want. Fortunately, the dealer talked me out of the dreadful sounding ICK preamp. The D-150 was a decent amp, but was hard on top and had no image width or depth. Very closed in. Maybe they couldn't measure it, but distortion free they were not. I learned that lesson when I was 17.
Numbers are great when they correlate to real world performance. I value the frequency measurements I've recently performed on three systems. With a forest of bass traps, the main one achieves a very flat response in the first four octaves. Measures good and sounds dead neutral. You'll definitely hear me preach neutrality.
You missed the point of my post i.e. you are NOT a software engineer in the traditional sense of the word nor to the best of my knowledge were you trained as a software engineer by extension did not train in the mathematics of software engineering. And you really ain't that old, at least not in comparison to me.
Music making the painting, recording it the photograph
You may choose to ignore the definition of a software engineer if you please. Specifically, I am an applications developer. Yes, I took many math related courses.So, how old are you? More importantly, what relevance does that have?
rw
Audio Hobbyman is trying to say that he was around when ENIAC was the industry standard. While not that old, I did work on some UNIVAC stuff while in school.
ENIAC certainly was the toast of the forties. Gee, I didn't realize that TAH had such seniority. Perhaps he knew Admiral Grace Hopper. :)
This post is made possible by the generous support of people like you and our sponsors: