4 ms·

Creating “digital mock-ups of new designs” isn't programming. Programmers make programs, which the designers can then use to create their mock-ups. Unless I mi

by rue 15y ago

Creating “digital mock-ups of new designs” isn't programming. Programmers make programs, which the designers can then use to create their mock-ups. Unless I misunderstand what programmable mixers are, it's not really programming so much as defining preset profiles or sequences. I don't mean to imply it's easy, but it's not what programmers consider programming. (Again, some programmer created the software that the sound engineer uses). Writers use word processors. Yes. I'm sorry, but are you just trolling? If your argument is that everybody needs software, that's true. There's no need for everybody to write their own, though. Diluting the term programming is downright dangerous.

gbhn 15y ago
To an extent, yes, but surely there's no clear line between a small excel macros and monstrously complex excel macro systems that are dreadfully abusing the Turing-completeness of excel macros and should use a better tool. But the latter comes from people playing with the former. I think that as information tools become more sophisticated, they necessarily develop programming-esque characteristics. Figuring out a way for that to happen naturally, intuitively, and broadly is a hard problem that seems like it would probably have huge rewards.
- rue 15y ago
  I think there exists the possibility that the complexity may force more people to learn ‘proper’ programming. However; Given the current UI/UX research and trends, I'd hold it more likely – and certainly preferrable – that the hard work happens behind the scenes, and users can perform more and more complex tasks reasonably intuitively.
mjwalshe 15y ago
Audio engineering Abeltron live can get down and dirty and I rember a high end reverb in sound on sound where you efectivly implimented custom reverbs in asembly language.
- jakejake 15y ago
  The difference to me is that you have to be a skilled operator of these devices, not a programmer. Absolutely, they can be very complex to operate but the main difference is that you are using these tools to do your task, rather than creating the tools. It is true that they sometimes have plugin APIs, but so do most applications. A writer would not typically write plugins for MS Word. But he might buy one for his needs. The API is not necessarily intended for the end user to become a developer.
  - mjwalshe 15y ago
    Well that was the point SOS is a very high end mag they run articles by industry experts that start out "when I where a lad working for Georg Martin on Sargent Pepper" I was boggled that they reviewd audio equipment which you had to write your own algorithms in Assembly though - now thats hard core

by rue 15y ago

gbhn 15y ago

To an extent, yes, but surely there's no clear line between a small excel macros and monstrously complex excel macro systems that are dreadfully abusing the Turing-completeness of excel macros and should use a better tool. But the latter comes from people playing with the former. I think that as information tools become more sophisticated, they necessarily develop programming-esque characteristics. Figuring out a way for that to happen naturally, intuitively, and broadly is a hard problem that seems like it would probably have huge rewards.

rue 15y ago
I think there exists the possibility that the complexity may force more people to learn ‘proper’ programming. However; Given the current UI/UX research and trends, I'd hold it more likely – and certainly preferrable – that the hard work happens behind the scenes, and users can perform more and more complex tasks reasonably intuitively.

mjwalshe 15y ago

Audio engineering Abeltron live can get down and dirty and I rember a high end reverb in sound on sound where you efectivly implimented custom reverbs in asembly language.

jakejake 15y ago
The difference to me is that you have to be a skilled operator of these devices, not a programmer. Absolutely, they can be very complex to operate but the main difference is that you are using these tools to do your task, rather than creating the tools. It is true that they sometimes have plugin APIs, but so do most applications. A writer would not typically write plugins for MS Word. But he might buy one for his needs. The API is not necessarily intended for the end user to become a developer.
- mjwalshe 15y ago
  Well that was the point SOS is a very high end mag they run articles by industry experts that start out "when I where a lad working for Georg Martin on Sargent Pepper" I was boggled that they reviewd audio equipment which you had to write your own algorithms in Assembly though - now thats hard core