Michaels reviews

• The CIO and CEO are here to cash out. This could be a good thing since they will both be gone soon! • CIO has no understanding of how to create software. His total lack of knowledge of SDLC and the fact that he does not know the meaning of production level software is crippling the company. • There is no process, no testing, no documentation, The CIO hired a bunch of devs fresh out of school, no dev managers, no product managers, He hired scrums and UX but will not let them do their jobs. • The CIO spends most of every meeting talking about himself and how he could do everyone's job on the call. The fact that a CIO is on such low level calls everyday shows his lack of vision and strategy. • The CIO only surrounds himself with "Yes" people, if someone stands up to him or challenges him, that person is pushed out. • The CIO thought it was a good idea to not talk to the rest of the organization even though the projects being created where for them! Again showing a lack of vision, strategy, and balls. • The CIO does not have a plan, or a roadmap. Everyday, he and his lacky's just throw a bunch of requirements out and expect them to be done in a day! Never looking at the actual requirements, the big saying is Copy Amazon and make it 5% better! • The CIO built a team in China, and the code they are creating is Crap! It is hacky and they are just copying from competitors. • CIO uses bullying to hide his lack of knowledge and will blame everyone else. • The technology managers spend their days, kissing up, rather than standing up for their teams. Both the CEO and CIO must go and it will take Michaels 1-2 years to fix the mess.

Oh gosh. So much is terrible. Everyone's leaving, unless leadership is able to burn them out to prevent them from interviewing. Let's encapsulate everything in one anecdote. The CIO got his old CEO friend to hire him, started butting in to every decision just to leave his mark, then promised to rewrite the website all by himself in one month. After one month, he gave up and instead got permission to hire 200 people. He gave them what he'd "worked on": an Excel file of some database tables for a Point of Sale system that he blatantly plagiarized from the public API Javadoc of another POS software product. The tables had 2 columns: name and description. But description was a copy of the name, without the underscores. When asked what some fields were for, he said he didn't know and also mentioned that he wrote most of it while drinking whiskey. His original ridiculous deadline remained unchanged, the devs had to start before the UI designs were done, he brought in a shadow UI team to polish and rewrite the UI, demanded a UI rewrite anyway 2 weeks before it was due, all just to have something to show his CEO friend over lunch. Then they threw it out and started over 2 weeks after the deadline. It didn't get any better to work there, afterwards.