This is a list of books currently on my To Read shelf... literally. I do not suggest or anti-suggest any of them at this time as I haven't read them yet.
This is not the home of dotProject or web2project. It is the home of CaseySoftware, LLC. Any dotProject support questions should be referred to their support forums.
In the past couple months, I've chatted quite a bit with different startup founders. Most were non-technical people looking for a developer to expand what they have (rare) or build it from the ground up (the vast majority). In all but a few cases, something rubbed me wrong about the conversations...
In a few cases, they're using equity-only to recruit. That's a huge red flag, but not a deal breaker. In a few cases, the technical priorities are solid and clearly defined. That's a huge plus but doesn't guarantee anything. A couple have offices, most don't. The lead people vary by demographics, experience, industry, etc, etc. It wasn't until I read Ellen Beldner's post titled "Should you take a pay cut to work at a startup?" when it clicked:
As a sequel to last year's T'was the Night Before Christmas:
Cell phones ring
are you listening
on the web
No server in sight
no one's sleeping tonight
working in a startup wonderland.
As of 19 December 2010, web2project v2.2 is officially live! You can download it from SourceForge now.
While in many releases we might focus on cleanup or functionality or developer aspects or similar, this one is a mishmash of a bunch of useful updates on numerous fronts. This isn't all of the updates but a bunch of the important ones:
For the Project Managers:
This post was lifted wholesale from Cal Evans's post from DevZone. I think he summed it up well and I had nothing to add.
Today, the PHP community mourns the passing of a friend. Three weeks ago, Richard Thomas, community member and friend to all who knew him passed away. I had planned on writing this post today and am ashamed that I put it off so long. Thanks to Jeff Moore's post and Paul M. Jones's post I was reminded of my duty to my friend.
I didn't know Richard as well as some. I hung out with him on IRC and we swapped work horror stories and coding tips whenever we met at conferences. I was privileged to see him just days before he passed when we were both at CodeWorks Portland. I got to talk to him for a bit at lunch and between sessions. Sadly for me, that conversations centered around topics so trivial that I don't even recall the details, just that fact that it was with Richard.
From Jeff's blog:
Richard is survived by his wife Lisa and four year old daughter Nicollette. Donations are being accepted to assist them. Even if you haven’t had contact with Richard, consider making a donation if you’ve done freelance work, as Richard was doing at the time of his death. Donations can be sent to:
Niki Fund, 4818 Davis Place #G, Renton WA, 98055
While I never like to hijack a moment, Paul made an excellent point on his post that I'll repost here for all because it is sagely advice from a man I highly respect.
And now, a practical note: A lot of PHP folk out there are freelancers or independent consultants, or are in other kinds of unstable job situations. If you are one of these, and you have a family, *please* consider purchasing term life insurance to take care of your loved ones if you pass suddenly. Get it even if you are very young. It is not expensive. It’s not the only thing you should do to prepare, but it’s an important thing.
Richard died at his computer doing what he loved, programming. We will miss you Richard, the world is a little darker place without you.
Admittedly, I only knew Richard in passing. We'd met at a couple conferences and he was at CodeWorks last month. I wish I'd gotten to know him a little bit better.
Approximately 10 days ago, I finished the 2010 CodeWorks Tour. This time around with 4 speakers hitting 5 cities, it was smaller, more compact, and generally a litte more intimate of an experience. Due to the odd nature of this one, I'm going to skip my usual "Good, Bad, Ugly" conference review format and go straight to some highs & lows.
Since most of our attendees were local to each venue, we opted out of standard hotels. They're only cost-effective if you have 100+ people staying there. Instead, we looked at universities and theaters. In Seattle and Orlando, we were at the Northwest Film Forum and the Orlando Shakespeare Theatre respectively. Both we set up for a close, intimate setup where we could actually see everyone. It's fun to speak when most of the audience is within 50 feet and you don't need a microphone. In Austin and Baltimore, we were at St Edwards Ragsdale Center and Johns Hopkins' Charles Commons respectively. Both were standard university setups which meant they were great on tech but a little impersonal and seemed distant at times.
This was my sixth ZendCon and I've lost count of how many conferences overall. Regardless, this is one of the unique conferences in the PHP community as it's a blend of business and Open Source. Sometimes that works beautifully, sometimes not so much..
First, the content was excellent. In past years, I've always heard of a few oddbad "what was he thinking" sessions. This time, they either weren't there or didn't cause a ripple. Overall, the content was solid, interesting, and well-supported. A couple people - Stefan Priebsch and Elizabeth Naramore - stood out as also having an engaged audience that actively participated. If you're looking for slides or information, check out ZendCon 2010 on Joind.in for all the details.