If the org is structured to where the architect role isn't directly involved with the configuration you should still get read only access or have the ability to see how these systems are setup or functioning somehow. You should not have to bother dozens of people on and off over several months to get the details on how these systems are set up and you should be able to verify these things on your own as needed. If it were me, I would present a list to my supervisor of all the the things I'd like to check and the potential recommendations/improvements I'm going to make. That way he/she will see that I need a lot more information on these systems and that having to constantly go to the busy admins for all the information would be a very slow inefficient process. How can you make or verify documentation that is accurate without the details? I wouldn't push it too hard, but get all your data together to make your case then present it....but still be ready for an answer you may not like.
...is easy. Put a protected zip document on your desktop named "tehsecretz" and fill it with one thousand GOATSE images of all different sizes. That way
they're sure to have to look at each and every one of them. They won't want your passwords anymore. Atleast, one would hope....
How the heck do these foreigners know so much about us?! It all makes perfect sense. We only support
OSS because we save money. Then, we use that saved money to buy mountains of cheeseburgers. After we're done eating (which we never are, right?) we
lay around and avoid things like education and the cleaning up the environment. We only use our energy to do cruel things to animals and activities that only benefit ourselves. Plus what ever other stereotypes we have going against us...
Personally I don't think starting off with "easier" languages is the answer, and I'll explain
why. I started programming in VB3 and continued to do so awhile after the release of VB6.
When I attempted to learn C it was very difficult at first. It was tougher and more of a
bare bones and "do-it-all-yourself" language. It's when I really got heavy into C and assembly
that I really learned about computer programming. Now, I think that if I were to start all over
or teach someone to be a computer programmer, I'd have to say I would first teach them the basics
of true computer programming in assembly. I wouldn't expect them to be an expert, but I would want
that person to be able to atleast read and understand assembly and what a computer can do with
data at that level. If you have a decent understanding of that, you can pick up any language a lot
easier and quicker. Going from ASM to C would not be tough, hell, you'd welcome it and love it.
And as your mind develops the "how things came to be" and structured thought of programming,
learn something like C++ or anything with OOP. Once you have that knowledge you have a good sound
understanding of programming in general which will make life a lot easier as you learn different
languages, but having that sound foundation is the most important.
I stopped buying music CDs many many years ago. Every few years I will buy a
"Greatest Hits" CD and that is it for obvious reasons. I know this is broken
and I've done it several times but, get rid of that gay ass data partition on
those CD's. I'm tired of having to just rip the whole damn CD and toss the CD aside
so I can play my music in Winamp or XMMS where I have an EQ and a playlist.
Unless there is something useful on there, get rid of it or put that shit on a seperate
CD.
Metallica is somewhat heading in the right direction. When St. Anger was released and you
bought the CD, you got access to all their live stuff for free that they recorded as a
way of saying thanks. Granted the CD wasn't as good as their others, but I still bought it
because it came with a DVD and I get to listen to their live concerts that they record for
ever and ever through their website. Plus they are free to have and free to share and they
actually do kick serious ass. I have put more of things like that onto my own music CD than
anything else. So in short, start saying "Thanks for buying and being a fan" instead of "Thanks
for your $20," here's your CD with 3 good songs.
Slashdot Mirror
If the org is structured to where the architect role isn't directly involved with the configuration you should still get read only access or have the ability to see how these systems are setup or functioning somehow. You should not have to bother dozens of people on and off over several months to get the details on how these systems are set up and you should be able to verify these things on your own as needed. If it were me, I would present a list to my supervisor of all the the things I'd like to check and the potential recommendations/improvements I'm going to make. That way he/she will see that I need a lot more information on these systems and that having to constantly go to the busy admins for all the information would be a very slow inefficient process. How can you make or verify documentation that is accurate without the details? I wouldn't push it too hard, but get all your data together to make your case then present it....but still be ready for an answer you may not like.
...is easy. Put a protected zip document on your desktop named "tehsecretz" and fill it with one thousand GOATSE images of all different sizes. That way they're sure to have to look at each and every one of them. They won't want your passwords anymore. Atleast, one would hope....
How the heck do these foreigners know so much about us?! It all makes perfect sense. We only support OSS because we save money. Then, we use that saved money to buy mountains of cheeseburgers. After we're done eating (which we never are, right?) we lay around and avoid things like education and the cleaning up the environment. We only use our energy to do cruel things to animals and activities that only benefit ourselves. Plus what ever other stereotypes we have going against us...
that's all fine and dandy, but we may have to wait for these
Personally I don't think starting off with "easier" languages is the answer, and I'll explain why. I started programming in VB3 and continued to do so awhile after the release of VB6. When I attempted to learn C it was very difficult at first. It was tougher and more of a bare bones and "do-it-all-yourself" language. It's when I really got heavy into C and assembly that I really learned about computer programming. Now, I think that if I were to start all over or teach someone to be a computer programmer, I'd have to say I would first teach them the basics of true computer programming in assembly. I wouldn't expect them to be an expert, but I would want that person to be able to atleast read and understand assembly and what a computer can do with data at that level. If you have a decent understanding of that, you can pick up any language a lot easier and quicker. Going from ASM to C would not be tough, hell, you'd welcome it and love it. And as your mind develops the "how things came to be" and structured thought of programming, learn something like C++ or anything with OOP. Once you have that knowledge you have a good sound understanding of programming in general which will make life a lot easier as you learn different languages, but having that sound foundation is the most important.
I stopped buying music CDs many many years ago. Every few years I will buy a "Greatest Hits" CD and that is it for obvious reasons. I know this is broken and I've done it several times but, get rid of that gay ass data partition on those CD's. I'm tired of having to just rip the whole damn CD and toss the CD aside so I can play my music in Winamp or XMMS where I have an EQ and a playlist. Unless there is something useful on there, get rid of it or put that shit on a seperate CD. Metallica is somewhat heading in the right direction. When St. Anger was released and you bought the CD, you got access to all their live stuff for free that they recorded as a way of saying thanks. Granted the CD wasn't as good as their others, but I still bought it because it came with a DVD and I get to listen to their live concerts that they record for ever and ever through their website. Plus they are free to have and free to share and they actually do kick serious ass. I have put more of things like that onto my own music CD than anything else. So in short, start saying "Thanks for buying and being a fan" instead of "Thanks for your $20," here's your CD with 3 good songs.