3 ms·

I had a boss once who conjectured that when you point a finger, there are three pointed back at yourself. I often come in to "rescue" projects after an initial

I had a boss once who conjectured that when you point a finger, there are three pointed back at yourself. I often come in to "rescue" projects after an initial developer or team, and more often than not I find just as many mistakes on the management side. For example - if the developer(s) have set up the production environment using their own personal AWS account, or set up DNS in their own name, yes, they screwed up, but that's the company's IP that management has failed to secure. Problems go both ways.

mgkimsal 8y ago
If developers did that against original requests, that's a huge problem and the dev is at fault. If, as I've sometimes seen, the dev asks for credentials, and a founder doesn't do it, or continually ignores the requests, but pushes for 'get it live', falling back to personal credentials (with reimbursement or using a company card) is a not-unusual fallback. If, after it's done, requests for transfer to a 'company account' are not made, again, dev at fault. If requests are made, but not granted, owner's fault. I've seen multiple scenarios happen, and they've gone in all directions.
- poulsbohemian 8y ago
  We operate in a completely unregulated environment, where anyone can hang out their shingle, calling themselves a software developer. For that matter, even our CS programs are not really training people for careers as software developers. Thus, there is a huge spectrum of training, experience, and talent in what constitutes software development. But, what I've witnessed is that as the "software is eating the world" mentality has taken off, in many companies responsibility for everything about the software has been delegated downward (shit rolls downhill) to developers who are not product managers, not security experts, not database experts, not really anything except <$lang> developers and then the company is surprised when in the absence of support and resources, they resort to just get it done techniques.

mgkimsal 8y ago

If developers did that against original requests, that's a huge problem and the dev is at fault. If, as I've sometimes seen, the dev asks for credentials, and a founder doesn't do it, or continually ignores the requests, but pushes for 'get it live', falling back to personal credentials (with reimbursement or using a company card) is a not-unusual fallback. If, after it's done, requests for transfer to a 'company account' are not made, again, dev at fault. If requests are made, but not granted, owner's fault. I've seen multiple scenarios happen, and they've gone in all directions.

poulsbohemian 8y ago
We operate in a completely unregulated environment, where anyone can hang out their shingle, calling themselves a software developer. For that matter, even our CS programs are not really training people for careers as software developers. Thus, there is a huge spectrum of training, experience, and talent in what constitutes software development. But, what I've witnessed is that as the "software is eating the world" mentality has taken off, in many companies responsibility for everything about the software has been delegated downward (shit rolls downhill) to developers who are not product managers, not security experts, not database experts, not really anything except <$lang> developers and then the company is surprised when in the absence of support and resources, they resort to just get it done techniques.