That will be a truly great conversation starter in prison.
Seriously. What Jeremiah Cornelius said. Your job is officially on an escalator to Hell and the steps have just flattened out.
They're doomed. Don't take it personally, just go.
Marketing is driving the software?
They don't care about security?
System administration is outsourced?
Quit. Leave now. Take only your jacket. Your adrenals will thank you later.
On the other hand, a truly good HR manager can be the making of a company. I've never known a successful CEO *anywhere* who didn't see absolutely top-notch people in the right places as a critical KPI of their company's long-term success. Either the CEO has those people recognition skills or they have a top-notch HR person at their beck and call.
Mind, for some firms (such as company harvesters like Bain Capital) this may mean the ability to carry out an order such as "find me a sociopath who can fire people in bulk and make it look like it's a mercy killing from a friend".
Sort of like Royal Archery. Your minions wait for the King's arrow to land, then paint the target around it. Bullseye.
You can always tell a pioneer by the arrows in his back.
Generally I just post a search for the item name and the string "problem with" and scan the list for clangers. Not so much a way to find, but a way to avoid.
I just had a look at healthcare.gov. Not a lot to show in the page source, but doesn't that page trailer look a lot like one of the open-source content management systems? Very Joomla! or Drupalish. If the content is in MySQL (/huge assumption) I do not wish to be insulting, but I can see how Oracle would very likely be an improvement...
It was about the transposition of The Man Who Sold The Moon to the development of a text editor, wasn't it? 'Been so long, think I'd better dust it off again...
If there were any professionally-architected deliverables from the site, they would at least have provided a page architecture, business rules, and use cases. Those things take a lot of time to put together, and they're usually transportable to a new infrastructure.
The Big Three involved in this will be able to pull together an underlying structure to support that front end, and it will be solid. A good, senior architect would be able to look at what they've got for about 5 minutes, know the solution, and spend the rest of their time pulling people together and explaining what they're doing. Engineers from companies that big will know what boxes to move around, and all will be well in a crashing great hurry.
The big difference of this sort of approach? The players have already made all their mistakes on other companies, and will freaking well know what they're about.
Just sayin. Couple of decades of that sort of stuff under my belt. It's why customers don't mind throwing money in certain directions.
(And no, I am *not* volunteering. Unless you want us to build it in Australia
Re: your sig: "Is buying a Harley Davidson as your first motorcycle since you were 16 at age 49 a midlife crisis issue?"
Answer, no. You need a CBR, Hayabusa or equivalent until 64. Then you may have a mid-life crisis and buy a Harley. If you wish.
Strong and versatile data typing and range checking is valuable, but it doesn't make code damnfoolproof.
I still shudder when I remember the Pascal programmer in a hydrology department who put his whole database in as an enumerated data type.
Only called us when he ran out of term slots...
The crash recorder says the driver pushed the accelerator and was not pushing the brakes, and then the car was hit....
From what source did the crash recorder get its inputs? Perhaps the failed ECU that was registering the accelerator was pushed when it actually wasn't, thus inappropriately opening the throttles?
And he never made that mistake again.
With rare exception, I have found WD-40 to be ineffective as a treatment for software coding errors..