RE: [rant] "Never mind the quality, feel the width!"
RE: [rant] "Never mind the quality, feel the width!"
- Subject: RE: [rant] "Never mind the quality, feel the width!"
- From: "Jacopille, David" <email@hidden>
- Date: Tue, 02 Dec 2014 23:29:23 +0000
- Thread-topic: [rant] "Never mind the quality, feel the width!"
'has' wrote:
> Well, 30K'd be a more meaningful measure put into context - there's a big difference between 30K of tight, mission critical code that can't be done any other way versus 30K of rambling odds-and-sods that could be replaced by 3K C# tomorrow.
Doesn't matter to Apple. Most of our workflow code is in Perl, C#, Objective-C. Far more than our 30K of AppleScript. And it is tight. Still doesn't matter to Apple.
> I agree. What's really important isn't the AppleScript language, it's the philosophy behind it: that users should have the ability to extend and customize and tailor their machines to be what they want or need them to be. Which may anything from a million-dollar automation workflow at a Fortune 500, or a more efficient way to follow their Likes status on Facebook or Twitter.
I don't think workflow automation should be the domain of developers. Now that I have developed hundreds of workflow automations I have discovered two things:
1. We are still only automating 5% of work in our company. Workflow automation is too time consuming. I'm shocked at how much unfulfilled promise there was in computers helping us more than they do.
2. It shouldn't be necessary to use code to build a workflow. We keep building the same workflow patterns repeatedly.
This is because there are only 43 ways to go from one state of work to another. No matter what you are doing. http://www.workflowpatterns.com/patterns/control/
The steps in the workflow are what might need some code, but we should have moved past having to code the workflows themselves by now.
I see an opportunity for Apple to build a workflow framework the right way - something that you can drop in AppleScripts, or Perl Scripts, Swift scripts, even C# scripts that run on Windows servers.
It should be very visual and fun to use.
A single workflow should allow steps to process on both Mac and Windows machines.
It should be headless - not a Master-Slave system.
It should have perfect load balancing across all systems.
It should be zero configuration.
The community of developers that builds work modules should be able to post them and sell them or give them away on a special store that supports the workflow tool.
That's what it would take for us to automate more than 5% of our work.
Dave
MFS Mail Relay Service made the following annotation on 12/02/14, 18:12:59
---------------------------------------------------------------------------------------------------------------------------------------
This email communication and any attachments may contain proprietary, confidential, or privileged information. If you are not the intended recipient, you are hereby notified that you have received this email in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. The sender does not waive confidentiality or any privilege by mistransmission. If you have received this email in error, please notify the sender immediately, delete this email, and destroy all copies and any attachments.
==============================================================================
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden