Shared publicly  - 
Does anyone deal with "automation skeptics" at work?
Robert Butterworth's profile photoKevin O'Neal's profile photoTeck Lee Tan's profile photoTim Luther Lewis's profile photo
What programmer would be against automation? A good programmer is a lazy programmer ;)
Don has a point - do you mean programmers against automation, or artists against automation?
Granted I can see people against tools if you go outside of their workflow. As an example I created a tool that attempted to detect where chroma crawl would occur in art assets. To make it easier for the artists to use I went with a Photoshop plugin that the artists could run. It was more of a pain in the ass for me to write but if it was its own separate application the uptake would be non-existent.
There can be maintenance issues depending on the expected lifetime of the system, and the number of layers of automation. I'm generally in favor of automation though.
Yes-ish, rarely and not nearly as bad as other studios I've worked at.
No joke: I was not to have any code up on my screen when I first started at one studio. A techArtist writing code?! Who would have thunk it?
right monitor = code. If I heard footsteps, I would minimize my code lol
I finally explained that automation and scripting came "second nature" to me. That's how I take notes. What better way to take notes than in the language the computer / DCC will already understand.
Finally I rolled out a toolset (most of which I had actually done from home), and the benefits where apparent and immediately well received. From there on code = ok
Yes, I have. Although it always is a bit of a toss up between 'time it takes developer to write, debug and maintain system' vs. 'cost of the person doing the thing to just do it'. I suppose it depends on how many times you're doing a given task (and how complicated, error prone and fiddly it is).
+Don Olmstead yes I've run across similar situations very often. So the need to be flexible (restraining from the overuse of buzzword "agile") and compromising is important. Even though it may be a pain in the @$$, if we accept it as the challenge that it is, we can benefit as well by broadening our knowledge & skills.

And we probably wouldn't make many friends by imposing protocols where we don't have to or just because we're too lazy/stubborn to pursue better alternatives for the end user.
A programmer who isn't an advocate with automation, would make me question how effective a programmer they are. Generally I find skeptics among artists or QA people. Every company has a few...
I find it comes out of ignorance and fear, like most sources of resistance to change.  The argument of "it would take longer to write" than do it by hand is often used and then the next time the argument is, we don't need a tool, we had a person do it just fine last time.. and it continues to be a manual labor task.  Fight to automate it first because it is rare that the problem won't show up again, and when it does it will still suck to do by hand.  
Automation skeptic? you mean a luddite :) I've never met one. If something can be automated it means that someone can get on with something unautomatable like making lovely artwork, which they enjoy far more than being a human robot
What Brad said, I'd rather work smarter than brute-force grunt work harder. We know that even if it seems like a one time task now, something later will cause you to revisit the task with minor changes, causing you to redo it all anyway. One hour now, five minutes every subsequent time, or one hour every time. Then when time becomes more critical the closer to release you get...

I think part of their skepticism is due to working at prior studios which had poor or buggy automation tools, so they create a resistance to it.
+Brad Clark +Brian Chung agreed. A phrase I have sworn myself never to accept again is "this is the only time it's gonna be used" whether it be tech within the engine or pipeline / workflow.

"once is an instance. Twice might be a coincidence. But three or more times is a pattern." « will be framed above my desk and possibly etched into my tombstone. =P
the one negative thing about automation, is that some people don't know how it works, and since they have a tool to do it for them, they woln't take the time to figure it out.  This becomes an issue if it breaks in a critical time, and people aren't trained to solved it the manual way.

the solution to "automation skeptics."  Rogue Programming!  don't tell anyone, just code it!
"is that some people don't know how it work"

I feel the complete opposite. The way it works is in code, not in someone's head! You can always reverse-engineer what the code does, and do it by hand. You can't do the opposite if that person gets hit by a bus.
I've normally had pushback from artists out of fear of being made to look less relevant (daft) in past but the odd programmer as well which is always more concerning to me.
+Dean Ferguson I Agree, I get the feeling from some people in the past, "I don't want to think about new stuff, I have my way and yes it's slower but it don't have to think, plus it takes more time to do the job so I work longer hours and look like I am dedicated". Meh, when someone else does the same work in half the time and goes home at the end of the work hours, that person appears to be not committed to the company.
lol +Alexander Morano 
+Robert Butterworth exactly! but to echo what +Shawn Kirsch said, "Do it anyway" whenever time permits, or is made. Although they may seem uninterested, stubborn and stuck in their ways (thinking they've found the formula to success and it should not be changed),
"Every great idea is eventually the wrong idea."
If its a useful automation it will catch like wildfire.
Well by the end of it, we got management to agree that if someone did not use the exporter/procedures they would be warned.
We had a guy try to race it once in the beginning b/c he felt it was too slow (mobu automation can't run headless)... He's now one of the biggest supporters. Our largest push back is from those people who want to cowboy through the data, and don't have enough information on how our automation system works to use it and still be effective. Always our problem on a small team, balancing how much time coding and how much time documenting and educating.
I almost have the opposite experience at my studio. Here, automation is almost seen as a magic bullet, at least by art and production. On numerous occasions, I've gotten emails asking "hey, can you do something to batch this?"

Where 'this' is sometimes a completely art-driven process like tweaking textures by eye that has no place being automated.
Add a comment...