The multi project manager
>> Outlook and Excel always compile
>> Endure the client’s anger
>> PM duty times 5
>> Your mail inbox is always overflowed
>> All the mails that you receive are important
>> Interesting job
>> Doesn’t have assigned team or project, works like a mercenary
>> If there’s something strange in your neighborhood, who you gonna call? Yep, the Architect.
>> Results at the end of the year, I guess
The full stack developer
>> Layers, layers and more layers: you know each and every bit including hardware, front end, back end, servers, databases, project management and client coordination
>> You don’t have to argue with anyone in your team. You know, you are alone
>> You don’t exist.
>> Every PM loves you and wants you in their projects
>> You can estimate issues and assign them to other people that won’t resolve them in that time. It’s their fault. Obviously
>> You can avoid other developers questions by making them feel bad about their lack of knowledge
>> You don’t have to deploy software in production
>> If you maintain your position, chances are that you will be promoted to Architect
>> You better not to fail. Ever
>> For the previous reason, sometimes you have to work at home, resolving your errors or working ahead. Because you fail, like everyone else
>> You have to work in two projects of the Multi Project Manager, assigned to each of them at 100%
>> You have to make changes directed by the Architect, despite they are not easy because you work in a legacy project. The Multi Project Manager is not aware of that because they couldn’t read the Architect’s email
>> You have to resolve issues estimated by the Rockstar Developer. And fail
>> You have to write test cases for the Testing Team
>> You have to answer the questions about how to execute them for the Testing Team
>> You have to retrieve testing data for the Testing Team
>> You have to deploy the software in production.
>> The receptionist knows your name (because they have to remember you everyday that you have to go home).