1. I love that now has shiny namespacing and a thriving code sharing community, but I think the heavily hierarchical namespacing practises used by some of the community (e.g. symfony components) are unhealthy.

    They are difficult to memorise, relying on (often slow) IDE autocomplete, and encourage a use statement for each class. That’s pretty much a scoped equivalent of from x import * in python — not a good practise! It’s still namespace pollution, it just takes longer to write.

    I am trying to use a more python–like, package-centred approach with much fewer subnamespaces. The outcome of this should be that you use the package name:

    use BarnabyWalters
osse;

    …and then using all the classes/subnamespaces from that root, e.g: $t = Posse\Helpers::convertHtmlToTwitterFormat($s);

  2. Question: What Status code should I use for “You haven’t provided enough/correct information to carry out that method”? Currently I’m thinking 422 Unprocessable Entity.

    Context: POST request to a list resource for the creation of a new sub-resource.

  3. URLs don't just give addressability, they give accountability. When there's a URL, someone is responsible for it. When a thing (concept, object, document, proposal, idea, etc.) has a URL, it can be discussed, supported, contested, referenced and documented.

    URLs are valuable things. We must treat them with respect.

  4. Rolled out usage of the menu element on . I’m looking forward to more browser support for HTML context menus, that will really open up the possibilities for cross-browser extensions

  5. Pushed some styling improvements to individual note pages as a result of some brainstorming earlier today. Splitting the content into Primary, Contextual, Metadata and Network will give me a solid foundation on which to add more information (e.g. mentions).

    One thing I haven’t added is an “actions” section, mainly because of double-click-to-edit. That only applies to the main content, though, and I have some other actions like syndicate to facebook, so I should make a section for those.