Yep.  Those are the stats of a website now live  -- this website.

I've started notifying all those who provided awesome feedback during the initial research and development stages of this project.  To each of you, "Thank you."

And, yep, bugs do exist (especially with respect to IE goofiness and box model padding in Chrome) -- and are all being chased down and squashed.

To those I have directly emailed, as well as everyone else, ENJOY and keep the feedback and ideas flowing in.

For The Posters

• Come to a place where the most savvy of product people come to establish and build their careers.
• When everyone is a product person, reaching your ideal, qualified, target audience is as simple as posting.
• Get the right Product People to find you!

For The Seekers

• Quickly find the perfect product job for you without sifting through a lot of the noise.
• Make the process of growing your career easier and more fun. 
• Engage and learn from the best of the Product Community.

Many have been asking me lately what I am using to manage the workflow and prioritization.  For the features, bug fixing, etc., I have been using Pivotal Tracker -- a very nifty and free Agile tool.  It has taken my previous Excel + Wiki / OneNote approaches to the next level and is perfectly suited to The Product Jobs workflow.  And, for now, it also fits my team size very well.  ;-)

Initial sketch...

Implementation...

I recently met up with a bunch of potential users of The Product Jobs. This additional, "creaped" feature, I noodled over at length this past weekend before deciding to include it at this point in time.

 From the very beginning it has been my goal to make the entire product both enjoyable and simple.  Resulting from early feedback, I decided one more layer of simplicity was called for -- to make it optional for job seekers to create an account.  More power to you, the job seeker, if you do, but I'd rather it be easy for everyone to come by and benefit from the centralized source for all product jobs

I feel it is better to let people, the users of The Product Jobs, interact in whatever ways they are most comfortable, either quickly applying, with no lasting product person footprint, with no searchable presence, or creating an account, tracking progress, monitoring for new opportunities, having greater access to employers, etc. --- to each their own.

While this feature will slightly delay the product's release I am very comfortable doing so to set the right initial tone, and be of greatest benefit to as many Product People as possible, from the onset.

For someone who is a big fan of jQuery (and author of numerous popular opensource jQuery plugins) this decision may sound to many as strange and counterintuitive.  I've decided to not just keep the languages simple, but to also limit the use of any JavaScript to the barest of minimums, avoiding the use of any of the fancier flourishes (animations, jQuery, ...)  leading up to the initial product launch  --- in turn, keeping a firm eye on the minimum viable product.

At the onset, I had resolved to develop this product in Google App Engine.  It was very appealing in terms of scalability and reliability.  The implementation was begun in the App Engine (Java flavor); and made it to the point of having a good portion of the core functionality both working and completed. 

Furthermore, due to the inflexibility of the Datastore, I have opted for the quicker, less resource intensive route - PHP & MySQL.  I am traveling this route with the knowledge that, in the future I can always revisit the App Engine as The Product Jobs grows and the underlying data structures stabilize.

In working with Google App Engine, I have found it to be too clunky and cumbersome for the task at hand and the rapid and dynamic process of development being undertaken. For now, in these early stages, Bluehost will do the trick.