A system (Imperial) that requires a tiny bit of thought isn't automatically bad, it may actually be good. Besides, as you may have noticed, we all seem to be able to deal with 60 seconds in a minutes, 24 hours in a day, 7 days in a week and ~365 days in a year. If you can do time, you can to Imperial units!
During the extensive hurricane seasons of 04/05 my POTS and DSL and Cable all went dead after 3 days. The only thing that worked was my cell phone.
I think that the transition to pure wireless will be ugly no matter what. The tipping point will probably occur when the majority feel that they don't need wired lines and that they are unfairly subsidizing those that do want/need wired lines.
As you say, they have no value in your environment. OK, maybe your team can't do reviews, maybe there is no point as the code is just a bunch of UI junk that changes constantly. It's no big deal. Not every team uses every software development technique, nor should they. I happen to write lots of code as a team of one. I'd like to get others to look at the code but that isn't going to happen, so no code reviews. I still get paid, applications work, customers are happy...it can be done.
Slashdot Mirror
A system (Imperial) that requires a tiny bit of thought isn't automatically bad, it may actually be good. Besides, as you may have noticed, we all seem to be able to deal with 60 seconds in a minutes, 24 hours in a day, 7 days in a week and ~365 days in a year. If you can do time, you can to Imperial units!
When they, the SI crowd, start using metric time I say it's "time" the USA switches to SI/metric for everything also.
Not to worry, the reset of the world can still do embryonic research.
During the extensive hurricane seasons of 04/05 my POTS and DSL and Cable all went dead after 3 days. The only thing that worked was my cell phone. I think that the transition to pure wireless will be ugly no matter what. The tipping point will probably occur when the majority feel that they don't need wired lines and that they are unfairly subsidizing those that do want/need wired lines.
As you say, they have no value in your environment. OK, maybe your team can't do reviews, maybe there is no point as the code is just a bunch of UI junk that changes constantly. It's no big deal. Not every team uses every software development technique, nor should they. I happen to write lots of code as a team of one. I'd like to get others to look at the code but that isn't going to happen, so no code reviews. I still get paid, applications work, customers are happy...it can be done.