|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (8) » Carbide.c++ 2.0.x (1) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (24) » General (46) » Off-topic (4) » On-device debugging (13) » Performance Investigator (2) » Product features (16) » Product releases (16) » Screencast (12) » Support (30) » Tool setup (5) » UI Designer (8) » Usability (15) » Work in Progress (13) » Write-build-debug (4) |
|
» Launching from the SPN View » Tips for using the CodeScanner tool! » Carbide in the summer » Austin Eclipse DemoCamp » Where's my console output? |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Quick tip: Getting TRK support issues solved faster | Main | Making the connection with TRK »
While I spent most of my time when I visited Symbian working with their engineers, I also worked with the team that is putting together their new internal Carbide support team. In my two years as Symbian's primary support contact at Nokia over 400 of their defects and feature requests have gone through my hands, so I was happy to give them what advice I could on ways to make the transition to their new team go smoothly.
One of the things that came out of my meetings with their support team manager was an agreement to share training materials. There is no reason why Symbian and Nokia should develop separate tracks of Carbide training material covering the same ground, so we're looking into ways to coordinate training topics between our two companies and will probably share all of the material we create via the Symbian Developer Network wiki. This means that new training content should appear much more quickly and in greater quantity.
Watch this space for further announcements!