Ex-Accenture here. Software devs (at the grunt level at least) would almost never work for another client at the same time as your main client. I only ever met one person who worked for two clients simultaneously, and IIRC they were management/admin level. As far as I know, they didn't file double-time as described in your comment.
Internally, the hour billing tracker (disgusting old thing) would limit you to 8h per day total anyway, so you couldn't just bill 8h to Project 1 and another 8h to Project 2, because it would scream at you that you're trying to file for unapproved overtime (which would cost ACN money). It's anyone's guess how this data would be presented externally to the client, but I like to think that they wouldn't bill for 8 hours externally when the internal record shows only 4 hours was worked.
As ex-Accenture, I can totally believe you. I was once on a project where a guy took more than a month to deliver a codebase that was negative in value - we spent more dev time untangling and cleaning up the utter cr*p that he produced than it would have taken to scrap the whole thing and rewrite it from scratch.
> Its best to make sure every damn communication is documented with them in the mix. It surely wasn't everyone, but enough of their onsite people pulled stunts that I am very wary of them.
I agree. Keeping a meticulous paper trail is the only defense against getting an incompetent team installed on your project.
Lots of mobile "games" are basically a casino, but the currency is time and you don't ever win anything. This is to the point that when I open older (pre-microtransaction) games on my PC, I'm momentarily disoriented because those mechanics are missing and I've gotten so used to them because they are so ubiquitous.
> It was seen as a resume starter before going back to MBA or other graduate programs.
This was exactly my experience as an undergrad, and later graduate software dev.
I'd venture that my skills were completely unsuited for the first couple of projects that I was placed on. I was utterly underqualified and not guided properly at all, though it remains to be seen how much this was Accenture's fault and how much it was the client's. I was definitely not worth the (rumoured) exorbitant hourly rates that our clients were charged for our expertise and work.
Ex-Accenture dev here. The problem with Accenture teams back when I still worked there was that they had no middle ground with regards to team quality - you either got a team 50% made up of people that could (metaphorically) kill a dragon bare-handed, or you got a team that couldn't code their way out of a wet paper bag. They will either be a help, or a hindrance.
Ex-Accenture software dev here. I'll be honest, your experience as a dev is basically subject to an RNG. You could luck out and land on an amazing project, with an amazing client, and an amazing team. Sometimes the clients, or the team, or the work itself, will sap your will to live. For a starter job, it's fine. It's a job and they aren't discriminating when it comes to graduates/undergrads (or maybe that's impostor syndrome speaking), so it's a great way to get some experience on your CV to move on to better and greater things after the 24 months is up.
Career progression for the technically-focused is non-existent. I legitimately felt like all technical functions were some sort of a vestigial growth that they haven't gotten around to removing. There are 13 levels of pay (I started at the second-lowest), and the top 8 I believe were reserved for the management track. Not a good sign if you don't like playing human politics.
After seeing how the metaphorical sausage is made within the company, I'd definitely not hire them for any technical work. You might get an amazing team, or you might get an outsourced money sink that messes up so badly that it's just cheaper to build your own in the first place. The AI and blockchain hype that you see in this comment section is (or was, in my time) an actual thing. Of course it's ill-advised to rock the boat about this on the record, so I chose not to do so.
LinkedIn is basically Stepford Smiler Central. There is no good argument to link back to a LinkedIn profile for dating purposes vs just saying the other person has a profile as an FYI.
The advantage is that the app is designed to work with specific obsolete devices that needed a now long-in-tooth software package to transfer files to them. It's very hard to get this package working on modern machines, so having this functionality available via a web app is a quantum leap.
* better battery life (supposedly up to 40 hours on a single AA, but I haven't benchmarked this independently)
* consequentially from the above, your phone's battery is saved for when it _really_ matters, like when you are in the middle of nowhere and need a map to navigate the environment
* a more tactile experience compared to a touchscreen
* works offline, and even without mobile signal coverage
* no adverts
* no interruptions, constant bings and bops and notifications from other apps
* no need for updates - it's already a "dead" platform and was never updatable in the first place
* can still download music from a PC, albeit it takes longer and is slightly harder than loading something onto a micro SD card
* no need to fight stubborn mobile UIs, just the buttons to play, stop and control playback
* some players come with a dedicated remote controller, which is also much more convenient than unlocking your screen to change tracks
* you can focus on just the music or audiobook that you took with you, no temptation to shop for new listens while out and about and no temptation to doomscroll your multimedia feed of choice (Instagram, YouTube, Spotify)
* content never "disappears" from your streaming service until you erase it on purpose
* as long as the laser module works, this device will be usable into ~eternity if your model runs on AA batteries. Your battery life never degrades, and your device will never be artificially obsolesced by its own battery disintegrating.
* the discs are very light and quite small, so it's still possible to get a couple of albums or several hours of speech-quality audio to choose from on the go.
* and of course retro coolness
That said, there are downsides:
* you could mostly get all of these advantages with a single mid-end MP3 player
* cables are a pain once one experiences the wireless life
* download from a PC is a thing, but it's undeniably burdensome because of how long it takes, and until Web MiniDisc, because of the antiquated formats and runtime environments supported by the official software.
* shock-proof, not so much. I don't recommend this for heavy workout in a gym
* the proprietary nature of everything chafes. Downloading music back from the player is impossible, remotes are proprietary, DRM is still a problem when the rest of the world moved on.
All in all, it's an aesthetic choice. An art project, if you will. It's not for everything, but in some ways, on certain days, the coolness makes up for it.
Internally, the hour billing tracker (disgusting old thing) would limit you to 8h per day total anyway, so you couldn't just bill 8h to Project 1 and another 8h to Project 2, because it would scream at you that you're trying to file for unapproved overtime (which would cost ACN money). It's anyone's guess how this data would be presented externally to the client, but I like to think that they wouldn't bill for 8 hours externally when the internal record shows only 4 hours was worked.