After coding the first implementation you will always realize things that you didn't anticipate that could improve the design. It's easier to get it working quickly, find the holes in the algorithm/design, then refactor it to be pretty and maintainable.
Pipe hidden behind the wall still has to be beautiful in relative to how the plumber have to work with it. If some plumber hide pipe behind the wall in a way that makes any maintenance impossible, then it's probably "ugly" for plumber standard.
Even if he is, to continue the analogy, people will care how well arranged and maintained those pipes are as soon as they have a problem with the plumbing and have to call a plumber.
A messy unfathomable array of pipes will cause the plumber to spend more time fixing the problem and will cost the customer more.
A well arranged, "documented" set of plumbing will help a good plumber spend less time performing the maintenance lowering the long-term cost of ownership of the plumbing. Not only that, it's more likely to work correctly the first time. Instead of spending weeks calling out plumbers to figure out why no hot water is coming from the bathroom taps, etc.
I'm also curious about this. I had the same idea and spent probably 20 minutes going through a proxy of mine clicking the PROCEED button every few seconds, but eventually gave up.
Confirmed working on Rogers in Canada. :D
http://imgur.com/bkyWL
It's not only faster than the HSPA speeds I was getting, but it's faster than my home internet connection from Telus. This is awesome.
I had to add an apn with these settings:
Name - Rogers LTE
APN- ltemobile.apn
Port- 80
MMSC- http://mms.gprs.rogers.com
MMS Proxy- 10.128.1.69
MCC- 302
MNC- 720
Apn type 1- (default,supl,mms)
2- (*)
After coding the first implementation you will always realize things that you didn't anticipate that could improve the design. It's easier to get it working quickly, find the holes in the algorithm/design, then refactor it to be pretty and maintainable.