I began plugin development at the hackathon at PHPTek, and I installed my phergie environment using a tarred up thing. But I'm not having some problems running phergie locally. I cannot seem to figure it out, so here is a foundational bit that I cannot get from the documentation.
Should I composer install from the composer.json file on the readme?
{
"require": {
"phergie/phergie-irc-bot-react": "^1.3"
}
}
| local: phergie-irc-plugin-react-cfp $ vendor/bin/phpunit tests | |
| PHPUnit 4.5.1 by Sebastian Bergmann and contributors. | |
| Configuration read from /var/www/html/phergie/phergie/scaffold/phergie-irc-plugin-react-cfp/phpunit.xml | |
| ..object(Phergie\Plugin\Http\Request)#121 (1) { | |
| ["config":protected]=> | |
| array(6) { | |
| ["url"]=> | |
| string(42) "http://api.joind.in/v2.1/events?filter=cfp" |
User Story Mapping is a strategy where you form a team of customers, developers, and users around your project to discover the full details of your project. Your team diagrams the story of the business process and all of the events happening around it. Once you have completed discovery of these stories, your team uses strategies to view features alongside the problems they solve. It is a powerful approach that allows your team to prioritize features, based on everyone's needs and motivations. Instead of planning our project as a building that we must build with a strong foundation, we learn to plan as if it were a vehicle. This focus delivers the Most Valuable Features to the customer by answering the question, “What’s Your Skateboard?”
In this talk, we will use some simple examples to diagram the process, discover the details of the project, and finally to identify the main objectives of the project. Through examples, we will discuss strategies for prioritizing features. Finally, we will talk about how to h
Pulling up Your Legacy App by its Bootstraps!
Your mission, should you choose to accept it, is to support an application built on an older framework. Refactoring isn't an easy option. The code is untested and nowhere near best practices or standards. In this session, we'll talk about strategies to incorporate modern PHP coding practices to add features and functionality and retiring the older code in pieces. We'll review specific examples and code from a real project where we bootstrapped a legacy application that needed a lot of help to become useful to its users and simpler for developers to maintain. We'll talk about strategies to leave the existing code in place until the new code is ready to replace it in whole or in pieces.
These are some ofthe most notable episodes I've listened to so far. I started with this one, and recommend it for an entry-point:
###women
I hereby claim:
To claim this, I am signing this object: