jbWebWare.com

I've been a bit quiet around here, and development on jbClan v3.03_beta has slowed down, so I thought that I'd give everyone an update on the goings on around jbLand.

I've had two major life changes these past 2.5 months which I can attribute to a slowdown in development:

1: The birth of my beautiful little girl, Kayla Burns

2: New employment

I also have a top secret. non-e107 project that I've been working on. I'm very excited about it and want to stand on the mountain tops and scream about it, but I want to wait till everyone has something to play with before I spill the beans

Both of my daughter have been a bit of a handful (Kayla is 2.5 months old, and Brianna is 2 years old). I've really wanted to spend a lot of quality time with them lately, and give my wife a break when I'm not at work, so I've been doing my share after work and on the weekends.

And the new job is going great. I was hired on ultimately as a PHP developer to help port their inhouse applications from ASP classic to PHP. We've had a few discussions about the new PHP backend, but right now I'm mainly getting my hands dirty learning how the current system works by working on existing customer's sites. I'm not going to get into their software that much here, but it's along the lines of an AJAX/ASP classic CMS.

The only thing is I've never even looked at a line of vbscript before starting here, so I'm learning a bit about how the windows world works at the same time.

The thing I'm really excited about is that eventually I'm going to be able to help design and work on a brand new system/backend, rather than just coming in and fixing bugs and adding/tweaking new features. It's a very small dev team, so I'm not just a number, which means that my feedback and suggestions will at least be heard. if not always implemented.

We're going to keep the workflow close to what it is now, while addressing many issues that wouldn't be addressed without a new backend. They figured that they'd rather do a complete revamp, rather than refactoring the system using an outdated language/platform. And if we're going to create a new backend, then let's use a language/platform that has as much of a future, feature set and staying power as PHP. Let's face it, PHP isn't going anywhere any time soon.

ok, that's enough for now. Keep an eye out for more info about this little project I've got in the works.

Till then, gg's folks!