But there are much better options thannotepad.exe;one of our favoritesisNotepad++.

We caught up with Don to learn about what went on behind the app.

Where did the idea for the software come from?

Were you trying to solve a problem youd experienced, or did the inspiration come from somewhere else?

I foundScintillaand built a prototype using it.

However, this solution was not accepted by my company.

So I then removed that specific part and continued to develop it in my leisure time.

On the 25th November 2003 it was made available on SourceForge.

How did you choose which platforms to target and which to ignore or wait on?

Under the context mentioned above, Windows was the target platform.

That idea had to be given up due to heavy use of the Win32 API.

But that doesnt mean that Notepad++ will never be a cross-platform program.

We are considering a important refactoring in the medium term, to prepare the reporting in the long term.

How did you want it to be different from other editors?

Certainly performance is the primary concern for Notepad++, since thats the reason for its very existence.

But also, its small size and its rich generic features are very important.

What was launch like for you?

The launch of the Notepad++ project was really quite ordinary.

I had never thought that Notepad++ would become popular.

I put both the source code and binaries on SourceForge, then users downloaded it and used it.

Getting feedback from users was a good thing (and always is).

How do you handle user requests and criticisms effectively?

Handling crash bug reports is always top priority, which I think is clear for every project manager.

For the feature requests, however, I dont react to them immediately.

If the same feature requests keep coming, then I will consider implementing them.

Though I rarely reply to users criticisms, I do listen to them.

Now, how do you split time between developing new features and managing existing ones?

Adding new features doesnt generally impact old code.

On the other hand, I have to split time between coding and administration of project-related concerns.

One example is building an online document site which allows people to cooperate.

What advice would you give to others that want to take on a similar project?

Enjoy yourself is the first and principal goal.

There is no need to explain why doing so will bring to your project a lot of good elements.

Make it as open as possible is the main goal for me to reach on a popular project.

No one can build a cathedral alone.

Have someone youd like to see featured?