-
It's time for the silent majority to speak up! warning: nothing but positivity here!
We're on a forum discussing PlayBooks so let's discuss them! I've had mine for a week now and it's been nothing short of a blast!
The number one top feature for me is the WOW-factor of it. Everyone who's seen it is impressed by the screen, the UI&OS and the simple fact that it's portable! (which means I get to show it off to more people
)
Remember the pre April 19th time on this forum?? We were all excited about finding out all the future options and functions, discussing every small rumour in the greatest detail. Well, we can still do this, and the best part is: We're doing it from our PlayBooks
So let's count our blessings and enjoy our PlayBooks! And ignore the trolls06-12-11 04:33 PM - I work in IT And I wholeheartedly agree with RIMs development approach.
First the architecture is set up and the own bb customers are served (bridge) Now that the roots are in place its easy as pie to deliver updates and improvements to the software. They probably use agile task&test driven iterations of up to 2 weeks frequency, where 2 weeks is the potential, not the promise!
Really the bb/pb user wins three times: free 3G, free updates, and no need to buy a new device after 10 months bc the hardware is outdated!06-12-11 05:16 PM - i use to work in IT as well. we made software that tested other software....imagine that
......this extended from java to C/++, to AJAX. long story short, even we couldn't release a fix without it messed up something else, somethings something so unrelated to the fix that we'd all be scratching our heads. we had a policy that every piece of code had to be accompanied with a test suite testing its functionality. nightly tests would run all the test cases, and we'd come back in the morning and fix the problems. sometimes the error ranged in the hundreds. even then....people make mistakes, and made test cases that would always pass, or didnt consider making an important test case, worse yet, an automated test case was not feasible. so newly introduced bugs were a hard to find even with strict coding and testing standards. it alway took a while before we could get our software to fully accept a fix/new feature.
i feel for rim and every other development company in these aspects of the game.06-12-11 05:50 PM - Wow 20 times thanked! Looks like there still is a lot of positivity and spirit here!
Its freakin awesome to type this reply halfway, swipe from the right bezel, check facebook, swipe back and continue typing!
Now I'm downloading Beats Brainwave Entrainment, did anyone try this out yet?
Multitasking... gotta love it!
06-13-11 05:26 AM - I made a comment that never before has 100s of 1000s brand new QNX OS iterations been in the hands of 100s of 1000s monkeys trying to do 1000s of things to it ("monkeying around with it" is how I put it). Someone took offence to being called a "monkey".I work in IT And I wholeheartedly agree with RIMs development approach.
First the architecture is set up and the own bb customers are served (bridge) Now that the roots are in place its easy as pie to deliver updates and improvements to the software. They probably use agile task&test driven iterations of up to 2 weeks frequency, where 2 weeks is the potential, not the promise!
Really the bb/pb user wins three times: free 3G, free updates, and no need to buy a new device after 10 months bc the hardware is outdated!
I am very impressed at how well the OS has performed under such an onslaught.06-13-11 10:43 AM
Would love to know if this works for you?
