Reply
SanDisk User
Posts: 91
Registered: ‎12-21-2010

Sansa Fuze+ Firmware Development Team

[ Edited ]

What is the size of the firmware development team working on firmware for the Fuze+?

 

Just wanted to get a bit of an idea of how many people are working on firmware, and how often they work/get together and discuss ideas. 


Are any of them on these forums and if so what are their names?

SanDisk Guru
Posts: 5,822
Registered: ‎12-26-2007

Re: Sansa Fuze+ Firmware Development Team

[ Edited ]

At great personal risk, I have unearthed a spy photo of the development team discussing wraparound scrolling and microSD card enumeration.  Sorry, the flash would have ruined the moment.

 

 

Starting from the left, Ned, Ted, Jed, Red, Ed, Stanley, and Leroy.  Brewing our evening lattes over the fire, we discussed the new lock function and video integration.

 

Bob  Smiley Tongue

 

Check out the Extreme Team here.

SanDisk Guru
Posts: 16,310
Registered: ‎04-17-2008

Re: Sansa Fuze+ Firmware Development Team


@neutron_bob wrote:

 

Starting from the left, Ned, Ted, Jed, Red, Ed, Stanley, and Leroy.  Brewing our evening lattes over the fire, we discussed the new lock function and video integration.

 


Where's Mongo?

"Candy-gram for Mr. Mongo!"

 

Smiley Very Happy

SanDisk Guru
Posts: 1,018
Registered: ‎02-05-2009

Re: Sansa Fuze+ Firmware Development Team

@ neutron_bob and Tapeworm

 

 

That's a          LOL

SanDisk User
Posts: 91
Registered: ‎12-21-2010

Re: Sansa Fuze+ Firmware Development Team

Can you please answer the question seriously? Or?

SanDisk Fanatic
Posts: 214
Registered: ‎06-20-2008

Re: Sansa Fuze+ Firmware Development Team

[ Edited ]

You can't expect to get that type of information for several reasons:

 

1.  Direct interaction between the customer and a developer is discouraged.  The decision on what to fix and the priority of fixes is usually a business decision.  Mitigating factors for deciding on what to fix might rely on how difficult the fix is, whether or not the hardware is capable of doing what is being requested and would the fix break some other basic functionality.   Giving direct access to a developer short circuits the process and as a result, the development team is distracted from the task at hand.

 

2.  Developers are typically not the most social of animals, and quite frankly I would be scared to death to let some of my development team talk to an end user.  Many developers I have met belong on the Sitcom "Big Bang Theory" and the last thing I would want as a corporation is to expose the end user to a Sheldon Cooper.

 

3.  The job of the moderator is to scan the forums and generate user cases for possible enhancements and fixes based on requests from all customers, not just the most vocal.  For instance.  Some users do not experience a slugish user interface because they don't have an SD card, but rather think that FLAC tagging needs addressing.  For me, that is not important, I do not use FLAC and since I have a HUGE database and a Micro SD card, I would rather have the UI issues addressed.  I have "solved" the UI problem temporarily by having all my content stored on the card and leaving the internal memory empty.  I know this is not a fix, but a work around.   The point is, we all have different ideas about what is the "most important" thing that needs fixing.  The moderator can look around and make a dispassionate choice and provide guidance on prioritizing issues.

 

The point is, asking how many developers and their names is typically proprietary information and would not be given out.  If a developer wants to come on this forum and identify himself as one, that is his perrogative.  Asking the moderators to "out" any lurking devs or give information regarding the size and makeup of the development team is basically asking for insider information about the company and can't be expected with any reasonability.

 

The mod's were just trying to be humorous without outright telling you that you're not getting that info.  Since I don't work for the company, I can tell you....You ain't getting that info. 

 

In my company I'd lose my job if I gave out that type of information.  I imagine the same is true at Sandisk.

SanDisk Fanatic
Posts: 398
Registered: ‎07-09-2009

Re: Sansa Fuze+ Firmware Development Team


@p_opus wrote:

 

The mod's were just trying to be humorous without outright telling you that you're not getting that info.  Since I don't work for the company, I can tell you....You ain't getting that info. 

 


Umm... I'm Pretty sure Tapeworm and Neutron Bob aren't moderators. There just people who spend a lot of time on these forums.

Tired of the Sansa Media Converter? Try Video4Fuze! It can create smaller videos than SMC, and is WAY more reliable!!!!

SanDisk Guru
Posts: 5,822
Registered: ‎12-26-2007

Re: Sansa Fuze+ Firmware Development Team

...and Stanley is a hothead too, a real curmudgeon.

 

A wise policy for the developer is to sit on the sidelines and observe how the feedback goes.  You can imagine, I am sure, how much headache putting yourself in the open could be.  Not only that, development is a team- and company- effort, and any statements made could need official blessing.

 

That's not even taking testing and quality assurance into the equation.

 

Bob  Smiley Very Happy

 

 

SanDisk User
Posts: 91
Registered: ‎12-21-2010

Re: Sansa Fuze+ Firmware Development Team

Hey, what I really wanted to know was just how many people are on the dev team, or where they work etc. are they just people sitting at home or do they go into an office. I was just interested. I didn't want to know their personal bank details, I was just interested about whether any of the usuals on this forum were part of the dev team.

 

I am not a spy. Chill Out.

SanDisk Guru
Posts: 5,822
Registered: ‎12-26-2007

Re: Sansa Fuze+ Firmware Development Team

 

We're just pulling your leg.  The forums are a great place for feedback.  

 

Bob  Smiley Very Happy