IT:BD:Infrastructure/Hardware

(UP)

Summary

Infrastructure costs. I'm not talking about the actual servers and computers – I'm talking about the rent, the cooling, the dust-free environments, the monitors, the tables ,the chairs, the movers, the security personnel, the support team, etc.

In other words, any infrastructure plan that revolves around acquiring and maintaining hardware in-house is to be considered …suspect.

Process

Improve the corporate understanding of safe practices
- teach developers to harden the data, not the infrastructure,
- enforce ssl for all communication, even among cloud elements.
- teach management to use truecrypt or others vaults to secure data on laptops, etc.
* Cloud the infrastructure as much as possible.
Purchase employees their own laptop. Let them code anywhere (saves rent).
- Consider Dual Booting, where one environment is AD controlled, for work-hour accountability, Outlook, and better hardware (antivirus & updates) management.
- Improve communication and progress reporting in other ways than at the cost of the renting of the space for a physical desk.
- Split the cost of repairs & replacement with them (leaving them a little incentive to not be careless).
Purchase everyone – not just devs – tonnes of screen real-estate.
Hardware names:
- Naming servers is hard. Consider looking at this first:
  - http://mnx.io/blog/a-proper-server-naming-scheme/