BBEdit Zend Framework Clippings Updated

I’ve just uploaded the latest version of the Zend Framwork Clipping set for BBEdit. As usual you can grab this from the downloads page.

Changes in this release

1. Added the class to the clipping name to disambiguate duplicate method names. (Picture __construct 1000 times.)

   Since BBEdit doesn’t allow whitespace in autocomplete suggestions, I’ve used a double-star ** as the divider between method and class name. This I hope is clear enough visually, but please let me know what you think.

2. Added parameter and return type hints to the clippings in line with the conventions of Ted’s original PHP clippings. (The return value is selected upon clipping insertion so a quick delete will get rid of it; its purpose is currently just as an aide memoir but I hope to leverage it further later.)

Barring any major issues, this will be the final Beta of the BBEdit Zend Framework Clippings. They are just missing clippings for the Zend_Search_Lucene and Zend_Soap namespaces, which require ad hoc work-arounds. After that they will follow the Zend Framework release schedule.

Beta 1 of Zend Framework Clippings for BBEdit Released

Update: the BBEdit Zend Framework Clippings have been updated.

We've just uploaded the first beta of our new Zend Framework Clipping set for BBEdit.

You can grab it from the downloads page.

The set currently covers 99%+ of the Zend Framework's methods, but we're aiming for 100%. After that we'll be following Zend Framework releases. (Updates via the newsletter.)

As per usual, bugs via the contact page, questions/suggestions welcome on the discussion board.

Introducing the Noumenal PHP Library

We just added the first version of the Noumenal PHP Library to the downloads page.

This is a collection of PHP classes built on top of Zend Framework. The Zend Framework team aim for an 80% solution. The Noumenal PHP Library is the next 10%.

It's released under a new BSD licence.

At the moment there's not much in the Noumenal PHP Library, just a FlashMessenger View Helper to begin with. We've got a big backlog of code to include but it takes time to get our private code massaged for an open-source release.

Download a copy, try it out and keep up to date via the newsletter.

Bugs via the contact page, questions welcome on the discussion board.

12 on The Joel Test

I started Noumenal 3 and a half years ago now. In that time I've learnt to program and written some software, some of which has actually been good. My greatest achievement by far is that, one year after the birth of my first child, I'm still business. (Just before his birth, I'd guess, not many thought that likely.)

Starting out, just surviving was always going to be a lot harder than my natural arrogance would allow: I was a philosophy PhD and despite my focus on the more technical areas, philosophy is the archetypal liberal art and liberal arts majors don't know anything about developing software. Thankfully for me I knew nothing of this.

More thankfully though, I'm stubborn, as much as that may not be good for my mental health. I have learnt the hard way about the need for specifications and testing and iterative development, and all the rest of it.

As much of an achievement as still being in business is, it is but a platform for success rather than success itself. (My long term goals were slightly more ambitious than merely not going bankrupt.) As such I've decide to apply the famous Joel Test, 12 yes or no questions to help you determine how good your software development process is.

For those of you who may not be familiar, the 12 points of The Joel Test are:

1. Do you use source control?
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?

(I'll be discussing these in reference to their application at Noumenal in future posts but you can read Joel's original discussion for more details now.)

A quick count says I'm currently running at 4 (which could pretty easily be bumped to 6) but 4 (or even 6) isn't good enough. As Joel says, companies like Microsoft run at 12 full-time.

Goals should be SMART: specific, measurable, achievable, realistic and time-boxed. Here's my goal: I will be at 12 on The Joel Test by 6th July 2010, the day my boy is two.

Noumenal Web Site (Re)development

After much time, and many delays, the Noumenal web site is finally beginning the process of taking shape. We at least now have a sitemap for the forthcoming v1.0: (Generated using http://writemaps.com/.)