Ignorance
I once was in a programming class where the task was "build a calculator". A student did one with buttons 1, 2, 3 all the way up to about 25 and then ran out of space on the screen. We've asked this before but liked it so much we're asking again: What's the best example of ignorance you've encountered?
( , Thu 30 Aug 2012, 12:30)
I once was in a programming class where the task was "build a calculator". A student did one with buttons 1, 2, 3 all the way up to about 25 and then ran out of space on the screen. We've asked this before but liked it so much we're asking again: What's the best example of ignorance you've encountered?
( , Thu 30 Aug 2012, 12:30)
« Go Back | See The Full Thread
'people-pulled-off-the-street-and-poured-into-suits' sounds like exactly the type we get 'off-shoring' on projects sometimes
Personally I don't mind working with 'off-shore resources' over in India - most of the time they work their nuts off and are very friendly. However, trying to get them to properly test anything, or admit they don't understand something or got something wrong, is like getting blood from a sodding stone.
Relating to your comment as well, if a big project comes in, you know their sudden 'abundant resources' are probably people they just grabbed off the street.
Case in point, got some code back just this year, confirmed to be 'fully tested and ready for live'. Past experience forced us to double-check - the Developer had hard-coded his name into the software. In other words, you had to log in as him in order to use the system now. Scary.
( , Fri 31 Aug 2012, 11:53, 1 reply)
Personally I don't mind working with 'off-shore resources' over in India - most of the time they work their nuts off and are very friendly. However, trying to get them to properly test anything, or admit they don't understand something or got something wrong, is like getting blood from a sodding stone.
Relating to your comment as well, if a big project comes in, you know their sudden 'abundant resources' are probably people they just grabbed off the street.
Case in point, got some code back just this year, confirmed to be 'fully tested and ready for live'. Past experience forced us to double-check - the Developer had hard-coded his name into the software. In other words, you had to log in as him in order to use the system now. Scary.
( , Fri 31 Aug 2012, 11:53, 1 reply)
Oh God
I used to get that a lot in a company I used to work for. As part of our security policies, an enforced password change was put in every month. However, one of the devs in the company had hardcoded his username and password into a piece of software he was working on, and promptly forgot about. And then wondered why his account seemed to be locking out all the sodding time.
Idiot.
( , Fri 31 Aug 2012, 13:34, closed)
I used to get that a lot in a company I used to work for. As part of our security policies, an enforced password change was put in every month. However, one of the devs in the company had hardcoded his username and password into a piece of software he was working on, and promptly forgot about. And then wondered why his account seemed to be locking out all the sodding time.
Idiot.
( , Fri 31 Aug 2012, 13:34, closed)
« Go Back | See The Full Thread