Pay was good, resourcing was terrible, but the problem sets were really interesting and overcoming the technical challenges to get work done kept it interesting.
each team is essentially autonomous, and they pick the tools they wish to use.
yes, there is lots of paperwork, e.g. getting anything deployed requires multiple people from across the firm to agree, but it's mostly automated and doesn't take more a few hours of background time, and it's understandable: the amount of money the firm would lose if something went drastically wrong is eye boggling.
the problems are challenging and interesting, I get to experiment with extremely high end equipment that isn't available for general purchase, and the hours are good (as is the pay).
(though I admit there are parts of the organisation that don't have this freedom: you have to be careful when interviewing)
This will lead to a maintenance problem shortly. I worked in similar environments. Technically clueless managers think that they only have to throw requirements over the wall and let the developers figure out how to implement them. When someone leaves the team the replacement needs to become acquainted with totally unfamiliar code, libraries and tools.
I do not get any benefit such as daily perks which make me not to leave my job...
Recently, I applied for Google Designer Job and when I get a job there, I swear that I will write a blog post for Hacker News about the working environment of Accenture...
I can't just ditch them. I love the team and I will see this product through until production, then I'm asking for 40k/year on top of my current pay or I'm leaving.
Once the project's out, then he will have leverage in the form of a track record. Now his managers can say "look at what this guy's done for us, do you honestly want to let him go?"
Our mobile development environment is a locked down internal Windows XP laptop that doesn't let anything in or out, so we had to write our own tools to package code to leave the laptop.
We wrote a simple little "chat" client in Node, but before sending the code off, it was packaged into a .jpg, and unpacked on the other side (my development macbook). This is how we've been dealing with code for over a year now.
Shit pay, 0 resources basically. Can't wait to leave.