I was just wondering what kind of mix of professions people had here? Maybe list your 'official' job title and what you actually do. (ie. food technician = flipping burgers
) And if no one understands wtf you do or your embarressed, what's your usual line in reply?
I guess I can go first (and maybe the only one
):
Official Job Title: Build and Deployment Engineer
More Accurate Title: The guy who compiles and tells developers how to compile big pieces of software, makes sure everything works in every environment, bugfixes coding issues, diagnoses buildtime and deployment errors and writes scripts so the build is more simple and repeatable without spending hours friggin around with things.
WTF?: Essentially there's several bits to this 'role'; the main gist is you liase with the developers and make sure their builds work and there software deploys; your in charge of making any build that will go to either to a live, benchmarking or test area environment. You diagnose problems with the code and/or build, your incharge of building domains (software) that you have to put software into (usually following an extremely poorly written requirements specification) although not the maintainance of the domains once the works been completed. Essentially you write a lot of ant and shell scripts to make sure the code can go into a specific area, and that this task is easily repeatable based upon the scripts you've written. You also have to QA code at a basic level to make sure its buildable and its going to work in a test area. A new area that I'm in putting into place is the continous integration of software builds, which is essentially just delivering QA on a more regular basis.
So you tell people you do when they ask:
- "Its complicated"
- "I make the impossible, possible"
- "Too much"
- "By day or by night?"
| Code: |
[b]Official Job Title:[/b] [b]More Accurate Title:[/b] [b]WTF?:[/b] [b]So you tell people you do when they ask:[/b] |
