Skip to content

Instantly share code, notes, and snippets.

View GeeH's full-sized avatar

Gary Hockin GeeH

View GitHub Profile
@GeeH
GeeH / f.php
Created September 18, 2012 09:28
validator array zf2
public function create($data = null) {
$json = "{ \"artist\":\"ergsern\", \"title\":\"enruy7u\" }";
$array = \Zend\Json\Decoder::decode($json);
$artist = new Input('artist');
$artist->getValidatorChain()->addValidator(new Validator\StringLength(array('min' => '5', 'max' => '20')));
$title = new Input('title');
$title->getValidatorChain()->addValidator(new Validator\StringLength(array('min' => '5', 'max' => '20')));
$inputFilter = new InputFilter();
@GeeH
GeeH / RFC-DHZM.md
Created October 18, 2012 08:33 — forked from Hounddog/RFC-DHZM.md
RFC - Decision Helper for ZF2 Modules

RFC Status: Work-in-Progress

@GeeH
GeeH / query.sql
Created February 21, 2013 11:13 — forked from Ocramius/query.sql
DELETE FROM
blah
WHERE
id NOT IN (
SELECT
c.id
FROM
blah c
LEFT JOIN
blah d
<?php
/**
* Global Configuration Override
*
* You can use this file for overriding configuration values from modules, etc.
* You would place values in here that are agnostic to the environment and not
* sensitive to security.
*
* @NOTE: In practice, this file will typically be INCLUDED in your source
* control, so do not include passwords or other sensitive information in this
@GeeH
GeeH / SomeForm.php
Last active August 29, 2015 14:06 — forked from anonymous/SomeForm.php
/**
* @Annotation\Attributes({"enctype":"multipart/form-data})
*/
class SomeForm
{
.......
/**
* @Annotation\Type("file")
* @Annotation\Options({"label":"File"})
@GeeH
GeeH / README.md
Last active August 29, 2015 14:07 — forked from igorw/README.md

kayladnls/machine-forget

A simple machine forgetting library.

Example

Here is an example of how you can instruct the machine to forget the answer:

@GeeH
GeeH / user-story-mapping.md
Created January 11, 2016 19:27 — forked from elstamey/user-story-mapping.md
an abstract for a talk I'd like to present

Working in a cluttered work environment is really distracting. We have a lot of potential features to deliver, and we don't completely trust our users to prioritize them. Wanting to help these users we begin to override some decisions. At some point before the project ends, we realize that we implemented a feature based on bad information. As much as we want to blame this on the user, it is not their fault.

Changing the way we talk to our users about their needs, we can avoid some of these pitfalls. We will put more of these decisions and priorities in the hands of the users and set reasonable expectations with them. We will investigate how to drop the idea of minimum viable product and instead deliver the most valuable features first. We will prioritize user stories by the objectives they solve.

Possible titles:

  • Forget the MVP, Deliver the Most Valuable Features! (is MVP widely known enough as Minimum Valuable Product?)

  • Value-Driven Development