39 karma · joined October 19, 2010
No update means:
- ZERO GPS functionality (Verizon reps acknowledge this) - crippled performance on what's supposed to be top-of-the-line hardware (because the Samsung version of Android 2.1 uses a badly written swap filesystem)
My iPhone 3G has a better UI, multitouch, and even now feels like a more solidly built device. On the other hand, I've never had a dropped call on Verizon in San Francisco. I'd rather have a mostly-functioning, always-connected device than a beautiful idiot that connects to a network incapable of delivering even SMS.
It's easy for Oracle to stand up, roll out the long list of their patents, call "They're infringing!", and then the burden is on SAP to show they were not.
I'm sure that some of SAP's products have similar (or near identical) UIs and APIs to Oracle's copyrighted works. Whether the similarity is intended, who knows...
Then again, the timing along with the iPhone screen lock bug could have been better...
Or, use a platform that handles dynamic allocation for you, or that lets you perform "object" based memory management instead of size-based memory management.
A similar principle applies to locking: do as little as possible. If you can use a development platform that lets you solve your parallel/concurrent problem naturally without locking (like folks have applied functional programming to do so successfully), do it!
- no Friday deployments - deployments run primarily by a single person should be done early in their work day - avoid Monday deployments ... people are usually fuzzier on Monday than they are on Tuesday, after having had a day to go through the weekend's email and get their heads back into work.