Even though this is the first time I have heard the term DevOp I used to be one. I would write the code, test the code, install the code, go on-site and train the users, handle the user feedback (errors or just simply whining), repeat, repeat, repeat.
Now I work in an environment where I write the code, test the code, then hand it off for independent testing, installation, user training, etc. I get to fix reported errors - but there are now less of those because I can concentrate on the development and testing processes.
Some losses include getting to know the customers and stuff like that but instead of having a few dozen customers for my work I now have hundreds, perhaps thousands so that isn't practical anymore.
I like it better now and don't have to suffer from telephone twitch while trying to work on something tricky.
- Life in the fast lane is only fun if you live in a country with no speed limits.
- Of all the things I have lost, it is my mind that I miss the most.
- I vaguely remember having a good memory...
Because trying to make your geeky job sound like a real kick ass job is just...lame.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011) "No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)
"It is the celestial scrotum of good luck!" - Nagy Vilmos (2011)
"But you probably have the smoothest scrotum of any grown man" - Pete O'Hanlon (2012)
this one is analogous to like "multitasking", "team", "cloud" blah blah blah
As developer in financial sector, every so often we need to attend to production environment but never "Cloud" - and I'm not aware any big boys in town are too excited to put their apps/data there.
What's with "DevOp"? Does this actually sound cool to anybody? so what now specialist must also be jack-of-all-trades to be any useful? How about "CashOp"? In today's competitive environment it's no longer sufficient for developers to code/deploy/maintain/fix apps+infrastructure. They must also provide their own funding for their projects - thus, "CashOps" or "CashDev", or "Managing Developer" (how about that that sounds good?)
And now "The software also needs to make sense from a business point of view" --- What's this? Since when "Business Requirements" isn't the utmost authority? Is this the first job you're taking, or that you been living under a rock? Any enterprise developers knows they are not the boss and requirements, and thus spec, comes from the boss. (Perhaps you need take an MBA to understand how business works - for starter "It's not democracy")
Yes, Developers are not bees, they are humans. Because of this, there is a correct division of labor. We are always doing the job that could be another. And, not always, there is affinity and / or tune between members of a team.
royal jelly Unit Test.
honey Instant Install Builder
I do deploy my software on communication systems. I do the testing, first without, later with the customers. I also train people on the apps. And I'm in charge when a customer calls and has problems with the system.
So yeah, I guess I am a "DevOp".