Paul Neumann
20
COW Coins
Forum Replies Created
-
I’ve pulled MB Looks off all of my machines. Better results and more fun to do it all in Speedgrade. Even just a single clip. So easy.
-
[Jeremy Garchow] “I’m not saying it’s not preventable, but as more and more people get used to getting more and more updates, and those updates contain more and more content and not just bug fixes, this seems to perpetuate the beta state.”
And that’s the thing there Jeremy. It’s not (nor should it be) perpetual beta anymore. It can and should be a brand new release with features and fixes released with absolute confidence that it will do what it’s supposed to do. If it’s two releases in the month of May and not another til July then that’s 3 releases that quarter. Not 3 beta iterations of what you first got in March. Any CTO will tell you he wants more developers more than anything. Not because he needs more people to fix all things that are wrong, but because he wants more people to make more and better products (through software) so they can be current and a leader in their business.
More and more people ARE getting used to it because more and more people DEMAND it. And they should.
On this very FCPX forum there’s a thread about when is the next update and what we all hope it will contain, while Adobe can tell you when the next update is coming and what’s going to be in it. That doesn’t make the current version of FCPX et al and CC beta versions. But it is pretty illustrative of different development methodologies in action.
-
[Jeremy Garchow] “This is because developers can’t possibly test across all devices and OS”
Yes, they can. It’s old methodologies and processes that they’re using that keep them constrained. That and the technology they need to do so is something they don’t use. Virtualized development environments (not machine virtualization but Service Virtualization), automated testing, continuous delivery and continuous validation are all available today.
-
But this shift in software cycles has also required an adjustment in consumer expectations as well. When a product releases early, there’s now an implicit understanding that what’s broken will soon be fixed. And barring a security exploit or privacy issue, that’s not a big deal. When a problematic update rolls out for an app, its not unthinkable to see changes in a matter of days.
This may be the reality for a consumer purchased piece of software, but on an enterprise scale it’s really not true. If my bank’s software keeps me from my money then I change banks. If my car insurance constantly has billing errors due to their software, I change insurance companies. And I do that with full understanding that there’s a massive stack of composite applications inside each one of these companies trying to get 2014 tech to work in concert with mainframe tech from the 80’s and everything in between. When customers leave it costs these companies revenue. And the heft of social media in regards to a company getting it wrong on this enterprise level is a major concern for the people who run these businesses.
-
In today’s “Application Economy” you have to be continually validating every part of every release, automating your testing and virtualizing your development environments. You can’t “break fix” your applications like you could in the past. Agile workflows never really got to where we thought they could be, but that is changing with recent DevOps methodologies. It’s such a mindset change though that older development organizations are slow to embrace it. “My problem is I’m only doing 3 of my quarterly releases a year.”
Meanwhile, facebook, etsy and the like are putting out new releases weekly. Apple is slow to the new way of thinking (trust me, I know) and Adobe seems to be going all in.
The end of massive scheduled, deadlined releases is here. You have to know what’s broken before your customer does because that’s how they talk to you these days…through your applications.
-
Insurance company, telco, hospital network, automaker, airline, bank, retailer, DMV, utility, satellite network…every business today is a software company. The CTO of Bank of America gleefully states he has more developers than Microsoft. And he does. All to keep up.
-
Build a Custom sequence setting with Quicktime/ProRes as the Preview File Format.
-
Select any 2 clips in the project bin, right click and choose create new multicam clip. Highlight the new Multicam clip and choose Open in Timeline. Delete the clips from this timeline. Select all the clips from your 82 clip timeline, copy and paste into the Multicam timeline you just emptied.
Now highlight the Multicam clip in the Project bin and select New Sequence from clip.
-
Bridge Brain! Man, they got a step up the messaging on that product.