Viewing 15 posts - 2,326 through 2,340 (of 3,047 total)
Shorten the time to get something done, increase the risk for error. This requires other things to change to keep the risk down, such as increased testing.
June 25, 2015 at 8:03 am
Thanks for the post.
June 25, 2015 at 7:57 am
Sounds good in theory. But management just hired someone. They want that person producing as quick as possible. They don't expect us to then have to train them. We should...
June 25, 2015 at 7:54 am
Thanks for the training.
June 25, 2015 at 7:50 am
I guarantee 100% uptime, with the exception of the 8 hours a day I reserve for maintenance.
June 25, 2015 at 7:49 am
It looks interesting, I'll have to give it a try. Thanks.
June 25, 2015 at 7:47 am
g.britton (6/22/2015)
June 25, 2015 at 7:38 am
Interesting but probably won't use it. Thanks for the education though.
June 25, 2015 at 7:34 am
I worked for one company 15 years. I've been with my current one for nearly 16. I get comfortable and it takes a lot for me to want to leave....
June 25, 2015 at 7:32 am
Our biggest hangup was normalization. There is a thing as too much normalization. A little less normalization (and sometimes duplication) can go a long ways to making operation more efficient.
June 25, 2015 at 7:28 am
I'll pass this one on to my sys admin. Thanks.
June 25, 2015 at 7:26 am
We had a new programmer talk us into using a complex tool set for a rewrite we were doing. After we got well into it, way to far to pull...
June 25, 2015 at 7:25 am
I'm still a little confused, but good start for me anyway.
June 25, 2015 at 7:21 am
Haven't seen a blue screen in a while, knock on wood.
June 25, 2015 at 7:20 am
Thanks for the script and the extra comments.
June 25, 2015 at 7:19 am
Viewing 15 posts - 2,326 through 2,340 (of 3,047 total)