There will be an official announcement regarding the future of FaultTrack sometime between 4-7PM GMT.
Please share the following link: http://kck.st/MT1LWT on Facebook and Twitter, even if you cannot back the project or choose not to.
We have less than 70 hours left - let's not let your pledges be in vain. Spread the word like an infinite while loop and let's make this worth everyone's while by succeeding.
Major shifts are happening in software. Windows 8, "Metro" design principles, and more and more is expected from a piece of software. Developers especially demand that their tools be of the highest quality, and actually work for them. With FaultTrack, I am to not just innovate, but set the bar for future bug tracking systems. Why can't a bug tracker have a kick-butt interface design? Why can't it have a productive experience for the developer? Why haven't bug trackers actually helped during the debugging process?
I honestly believe that I can do better, and FaultTrack is going to re-define how bug tracking integrates into your debugging experience.
I've taken extremes to ensure that not just most, but all user interfaces in FaultTrack are well designed. I've used a mix of Metro inspired design principles and proven practices in UI design to deliver outstanding designs. And yes, I've themed FaultTrack to look much like Visual Studio 2010, because let's face it, it looks great.
FaultTrack is based around some very simple ideas.
- Bug tracking is intrinsically part of the debugging process, whether a developer acknowledges it directly or not.
- Automate things that make a developer slow, like copying exception data from the Visual Studio Exception Assistant into a bug tracker.
- Keep the tool out of the way of the developer, but have it ready when the developer needs it.
- Bug tracking should not be confined to the web. Let it live on the desktop, and work for all developers - those who have internet connectivity, and including those who do not. (eg. traveling, developing on a non-connected secure network).
- If you write in C#, Visual Basic, C++/CLI, F# or any other CLR compliant language, let's give you a tool that actually caters to that. The CLR and .NET platform have a user base of its own, its time that user base had a better tool for their specific needs.
- And while FaultTrack will be catered to CLR languages, there is nothing stopping you from using it for other languages.
Let's be organized. I can't stand to look at most bug trackers. They look like that average "company app" that have literally hundreds of unorganized fields. Yeah, you know which bug trackers I'm talking about.
I've designed the data entry parts of FaultTrack so you can show what you need when you need it, and hide what you don't need when you don't use it. Keeps the interface clean, and easily accessible.
See anything familar? Play, Pause, Stop, Restart? We have full access to the Visual Studio Debugger Services for Automation, and are fully interested in taking advantage of them in FaultTrack. This is the core of how I am doing real-time bug tracking for you, and will open up an entire box of goodies for the future. Right now I am focusing only on real-time bug tracking, but trust me, I have a ton of things planned.
So you're probably wondering right? Who the heck is this random guy? Hello, it's nice to meet you, my name is David Anderson. I linked to my blog where I talk about C# and .NET (I want to become a C# MVP) and I also want to create a software company and create jobs while writing kick-ass software. And, with a twist, I seriously want to prove to the world that anyone can do it without a college degree. People are smart, you just need to get them passionate about something, and generally the rest falls into place. It's alot of hard work, no doubt, but I'm ready for it. I've been doing it for two years already, and I'm still as motivated if not more than when I started.