NYCPHP Meetup

[Gary Mort]

Hi David, thanks for the excellent suggestions!

In all honesty, I think some people are viewing my goals as loftier than 
they are.  I don't plan on writing a book or designing a curriculum.

Instead, I want to go through one of my old "Learn to program Object 
Oriented PHP" and rejuggle the lessons so that as much as possible, good 
practices are used throughout the chapters.

My plan would be to publish it on my website, maybe setup an email list 
to send out notifications when each new lesson is available - and 
definitely to have a forum for people to discuss with each other as well 
as provide me with feedback.

Also, just to clarify, I am shamefully at the middle of the process to 
unit test, comment, and use version control.  As such, one of my goals 
with this process is to actually learn - as I find trying to write 
instructions for others helps me develop it in my own head.  So I expect 
the initial "lessons" to be rough and need fine tuning - but one of the 
things I've really learned is that even bad version control is better 
than no version control.  Many people get so hung up on which system to 
use - wheras it doesn't matter nearly as much as using SOMETHING.

If at the end of the whole process I have something solid, then I can 
consider the daunting task of "writing a book".. :-)

On 1/24/2012 1:42 PM, David Krings wrote:
> <major snippage>
> - algorithms / objects / classes
> <snip>
> - documentation
<snip>
> - scope doc of project: what is it supposed to be (address label 
> creator or a bird bath?)
> - functional requirements: detailed list of individual features and 
> functions explaining the expectations of the stakeholders (users, QA, 
> devs, etc.)
> - technical spec I: flow charts, description of approach
> => now write code, unit tests, and so on
> - technical spec II: amend the first version and add a description of 
> what was done, no code is to be found in here
> <snippage>
> - error handling
> - adherence to UX guidelines