Originally posted by NickFitz
View Post
Another day that's just a long planning meeting tomorrow 
These things really bring it home to me how out of place I am in this scene. I'm a web developer: front end, back end, databases, web servers, all of them, some of them, whatever. But this is an IT infrastructure gig: it's all about systems configuration and stuff, which I'm not really interested in as a field. And as so much of it is to do with ClientCorp's specific IT infrastructure, I'm not even that interested in learning about most of it, because it's just third-party solutions like Infoblox (DNS), Tufin (no idea), SolarWinds (no idea), and such.
I just get by with the attitude that input comes in, output goes out, and I write the bit in the middle that transforms the former into the latter. If that process of transformation has side effects like causing servers to be configured or DNS records to be created, great; but, as Sam Ruby has it in the strap line to intertwingly.net: "It's just data".
And on that note, goodnight
These things really bring it home to me how out of place I am in this scene. I'm a web developer: front end, back end, databases, web servers, all of them, some of them, whatever. But this is an IT infrastructure gig: it's all about systems configuration and stuff, which I'm not really interested in as a field. And as so much of it is to do with ClientCorp's specific IT infrastructure, I'm not even that interested in learning about most of it, because it's just third-party solutions like Infoblox (DNS), Tufin (no idea), SolarWinds (no idea), and such.
I just get by with the attitude that input comes in, output goes out, and I write the bit in the middle that transforms the former into the latter. If that process of transformation has side effects like causing servers to be configured or DNS records to be created, great; but, as Sam Ruby has it in the strap line to intertwingly.net: "It's just data".
And on that note, goodnight
The problem was that the data in the legacy systems was garbage. I kept on telling him it needed a cleanup, and that they had the benefit of time and foresight on their side. Of course I was ignored, and in his mid atlantic accent (previously worked in New York I think for 6 months - so hence the accent shift) would say "It's just dayda".
Never endless stream of cretins on every gig that think like this. If you lost your systems, but not your data your business could still function. If it was the other way around it's game over. Data is the lifeblood of your business, and some competitor is out there with better data than you exploiting that to it's full advantage.
In spite of the fact that we live in an age with the most sophisticated processors and programming languages available we still pay very little attention to data quality.
Comment