Thanks for FF3.5

[Douglas McDonald]

Just want to say thank you. I can't wait to try it out.

Doug

[Jim Dunn]

Same here, much thx!  : )

[David Warner]

Ditto, thanks Paul you're a star!

[Paul Squires]

Thanks guys, I appreciate it.  :-)

As you can tell, I haven't been much of a programming machine these last few (well, 10 months). This has been a hard year for me and programming has really taken a back seat for me. It has hard to become excited about programming. Hopefully as the Fall/Winter sets in then I will have more time and motivation for FireFly and other products.

I have the best customers on the planet. You guys have always supported me and I am a better person for having made all you my friends.

[Haakon Birkeland]

We'll help motivate you â€" by nagging for those little gems that makes FF more and more precious. 8o)
And we'll / I'll help you forget that bad â€" you know ...

[Ronald Maxwell]

Just wanted to add my voice of thanx as well!  Your hard work is appreciated.

Greetings, Ron

[Haakon Birkeland]

Paul â€" did you ever consider having the FF version number in the caption of the main form?
Now that multiple installations are implied, I assume that would be useful to some users.

[Richard Kelly]

Another giant leap for mankind! If, when 4.0 comes out, will 3.5 projects convert over?

Rick Kely

[David Maruca]

It has hard to become excited about programming.

I was having the same problem here at work and talked to my boss about it. He's not a coder, but heads a bunch of project managers who are used to motivating people to finish projects which they usually aren't motivated to finish. The 2 things he said to focus on are setting milestones and giving those milestones dates.

So what I did was start to break my projects up into pieces or phases and estimate the time it should take to finish. You can't just stop there, though. Share those dates with others. Then the motivation really starts to kick in. The persons can be a team member or set of close customers. Someone who can appreciate and be supportive of you meeting those dates or exceeding them, and not be too critical if you miss a few of them. You would be surprised but it really kicks you into gear.

It can be real daunting when you have a bunch of people wondering when the final product is going to be finished. That's all they want. You start thinking of everything that needs to get done and it's easy to lose focus of what you want to or should work on first. However, if you do it this way then it feels like other people are actually involved in your project even if you are the only one coding it, and if keeps you focused.

Another thing that can really help is to get even just one person to help organize. They don't even have to know how to code, but just be someone smart. They could handle the bug tracker and help set priorities. Anything to just not feel like you're alone.

We're competitive by nature and do our best work when we're working with others. Coding a large project by yourself is like playing a sandbox game like Minecraft on singleplayer. That's just how I look at it.

I hope my words are encouraging to you. I'm a one-man shop where I work at, too. It's easy for me to lose focus without help.