That wasn't his password, it was the network password. He doesn't own the network. The city does. His supervisors are agents of the city, acting on the cities behalf. They requested the password to the *cities* systems, on behalf of the city. He refused said password. It was never his to refuse. He was compelled by law to give that password up. He broke the law. Now he's sorry. At least he has his principles right?
Wow, this sounds suspiciously like a pyramid scheme. You oversell at the top so the ones at the bottom receive devalued returns. When did Amway take over the financial market?
It's been this way for awhile now. I can't remember what the cut off is, but it's something like anything over $30 an hour is considered exempt. You get straight time no matter what. I've been in the IT industry since the early 90s and it's been that way for as long as I remember, except for a brief stint in the late 90s when we all made a killing writing "y2k compliant" software.
Low level code can also be efficient and "pretty". The language used does not necessarily indicate how clean the code is. I've seen assembler code that made me want to cry it was so well organized. That code was also very easy to maintain.
For any organization that plans on sticking around for awhile it's important that their code is as maintainable as possible. We all know that turn over rate for engineers is fairly high and it's not unheard of for programmers to have had 10 or more jobs throughout their careers (even more if they are a consultant). That being said, in order for an organization to protect it's IP, crown jewels, or what have you, it's imperative that the code can be picked up easily by fresh, new talent, otherwise the organization may end up hostage to the developers.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." (Knuth, Donald. Structured Programming with go to Statements, ACM Journal Computing Surveys, Vol 6, No. 4, Dec. 1974. p.268.)
Slashdot Mirror
That wasn't his password, it was the network password. He doesn't own the network. The city does. His supervisors are agents of the city, acting on the cities behalf. They requested the password to the *cities* systems, on behalf of the city. He refused said password. It was never his to refuse. He was compelled by law to give that password up. He broke the law. Now he's sorry. At least he has his principles right?
Wow, this sounds suspiciously like a pyramid scheme. You oversell at the top so the ones at the bottom receive devalued returns. When did Amway take over the financial market?
It's been this way for awhile now. I can't remember what the cut off is, but it's something like anything over $30 an hour is considered exempt. You get straight time no matter what. I've been in the IT industry since the early 90s and it's been that way for as long as I remember, except for a brief stint in the late 90s when we all made a killing writing "y2k compliant" software.
Low level code can also be efficient and "pretty". The language used does not necessarily indicate how clean the code is. I've seen assembler code that made me want to cry it was so well organized. That code was also very easy to maintain. For any organization that plans on sticking around for awhile it's important that their code is as maintainable as possible. We all know that turn over rate for engineers is fairly high and it's not unheard of for programmers to have had 10 or more jobs throughout their careers (even more if they are a consultant). That being said, in order for an organization to protect it's IP, crown jewels, or what have you, it's imperative that the code can be picked up easily by fresh, new talent, otherwise the organization may end up hostage to the developers.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." (Knuth, Donald. Structured Programming with go to Statements, ACM Journal Computing Surveys, Vol 6, No. 4, Dec. 1974. p.268.)