Quote:
Originally Posted by CRussel
Yeah, I know. Just needed to vent a bit. Office full of developers, who all think they know IT.
|
A friend is dealing with that currently. He's essentially in a DevOps role, but is primarily responsible for the architecture his employer builds out for their clients. He's getting increasingly picky about things like holding architecture meetings so the developers understand the underlying issues. Current languages and development environments tend to abstract away the places where problems can occur, and the devs won't be aware of them till something blows up.
I happened to be around when he got a call from the office about holding an online demo. The problem was, the stuff to be demoed was on a server not public facing and accessible from outside. It would be moved to a public-facing server once fully developed. His response was "If you really want to bend over and moon the Internet, "svcadm start apache" will start an Apache instance on the box and let you get to it. But we really need to plan these things and I need to know rather
before you want to do a demo for a client..."
He said "The developer who created what was to be demoed is a front-end developer. He works in HTML, CSS, JavaScript and Php. You tell him what kind of website is needed and how it should look and behave, and he'll build one to spec. The security of the system his site will be hosted on is not his problem, and shouldn't be. It's my problem, and people need to learn to talk to me."
______
Dennis