Christoph Rumpel demos PhpStorm code snippets a.k.a. live templates.

Marmoset is a Chrome App which lets you create gorgeous code snapshots within seconds.

The issue is that doctrine is keeping the objects in local memory because the daemon is basically a php long-running process. In order to allow the objects used by the job to get updated, you need to $em->detach() the objects. But you'd also have to have cacade={"detach"} on all relationships that object has as well. So the best thing is to just call $em->clear() at the end of your job. This will detach all objects from doctrine and it will get a fresh copy of all the objects from the database for the next job run.

This new NodeJS framework was inspired by Laravel, with similar folder structure and includes IOC container, very similar router, service providers, middlewares, even Views similar to blade. Utilizes ES6 classes for controllers. Even has an ORM called Lucid.

Interesting presentation from one of the Doctrine core team members.

In this Talk, we are going to dive into Doctrine 2 ORM’s feature set. We’re going to see the advantages and disadvantages of each functionality, with a particular focus on use-cases that each functionality attempts to solve, which features should be used with care (or avoided completely) and which ones should be used even more.

Building a JSON API, you should be trying to follow the JSON API spec. Save your team the effort of arguing the best response format. It reached version 1.0 earlier this year, so it's safe to say there won't be too many big changes now.

It defines a standard for what the offsets in the json response should include: a resource is returned in "data", pagination in "links", errors in "errors", additional data in "meta", and a standard for including other objects aka "compound documents" in "relationships"/"included", so that instead of embedding other resource objects inside the main resource it flattens the graph of objects to eliminate duplicate data in the response (eg. the same user can be both the post author and a comment author).

If you're curious about some of the design decisions or how it compares to HAL, check out the FAQ.

If you've played with vagrant it can be difficult to know which vagrant might be taking up a port right now, or where all your memory went (various vagrants still running). This lets you boot up and shutdown vagrants from the Mac Menu Bar, see the status on all your vagrants, etc.

Great website by Github to help developers understand the differences between the open source licenses and which one might be best for their project.

A little-known-feature of the GitHub API is the ability to attach changes to an issue, converting it into a pull request. The hub command, a wrapper around git that makes it more GitHub aware, allows you to easily do this.

Neat site that shows side by side how to do something in jquery and how to do it in native javascript. It's not saying don't use jquery, but your just doing something simple, in modern browsers, maybe you don't need the whole jquery library.

The Sequelize library provides easy access to MySQL, MariaDB, SQLite or PostgreSQL databases by mapping database entries to objects and vice versa. To put it in a nutshell, it's an ORM (Object-Relational-Mapper). The library is written entirely in JavaScript and can be used in the Node.JS environment.

Plates is a minimal PHP template system that’s fast, easy to use and easy to extend. Inspired by the Twig template engine. Made for developers who prefer to use PHP templates over more compiled templates such as Twig or Smarty.

PHP-CS-Fixer will analyzes some PHP files and try to automatically convert the code to meet PSR coding standards. There is even plugins for VIM and Sublime Text.

NPM Link

It can be handy to use npm link to make npm use a local copy of a node repo if you're working on that other repo at the same time (eg. I'm working on a repo that relies on a npm module I also contribute to). npm link creates a symlink in your npm global modules folder to your local repo, so that npm install/update uses your local copy and doesn't overwrite it.

Vagrant

You used to have to add settings to your config to get symlinks to work in Vagrant (see this issue) but since Vagrant 1.1, Vagrant supports symlinks by default (yay!) (see the commit).

NPM Link Not Working With Vagrant?

If the symlink points to somewhere outside your shared_folder, the symlink won't work though. You have to shared_folder where the symlink points to as well. So just like in the example:

cd ~/projects/node-redis    # go into the package directory
npm link                    # creates global link
cd ~/projects/your-project-repo   # go into some other package directory.
npm link redis              # link-install the package

You have to add to your Vagrant config:

config.vm.synced_folder "/usr/local/lib/node_modules/node-redis", "/usr/local/lib/node_modules/node-redis", :owner => "www-data", :group => "www-data"

Jeffery Way, editor at Nettuts, is somewhat of a Laravel evangelist. In his talk at Laravel Conference 2013 he goes over how you can write more testable code, and how you can improve your unit tests.

• 5:40 - Intro to Laravel's handy generator Artisan to generate files, and a package he put together of even more handy generators, you can get it on github: Laravel-4-Generators.
• 10:55 - Using Dependency Injection to write more testable code.
• 13:30 - Smart type hinting with Laravel's IOC Containers.
• 18:45 - Intro to Interfaces using an example of injecting your database layer via an Interface implementation so your controller isn't bound to an ORM.
• 24:05 - Creating php unit tests.
• 28:40 - Using mock objects and the Mockery framework.
• 33:50 - Making tests more readable. I found this interesting; creating common assertions to simplify writing tests, so your more likely to write them in the future.

"whoops is an error handler base/framework for PHP. Out-of-the-box, it provides a pretty error interface that helps you debug your web projects, but at heart it's a simple yet powerful stacked error handling system." Another popular one is PHP-Error: https://github.com/JosephLenton/PHP-Error .

PHP 5.5 replaces APC with Zend Optimizer+, now called Opcache http://t.co/kM9EtMw8aO #php #programming

I learned a lot about the history of Laravel from this introductory talk by the founder Taylor Otwell at the first Laravel Conference (2013).

• 2:48 - The Vision: aka Otwell's inspiration. I didn't realize that Otwell used to be a big CodeIgniter fan. This is probably why I was naturally attracted to Laravel when I first discovered it. It fills a lot of the gaps the CI community wanted filled.
• 4:12 - Why create a new framework? Why not fork?
• 8:05 - Documentation is king. Since CI was known for its' simple/clear docs, Otwell realizes how important good docs are to attracting new developers.
• 9:15 - Important features of Laravel: Routing, Eliquent, Blade templating, and Auth.
• 11:35 - How Laravel is leveraging the Symfony community.
• 13:05 - Embracing Composer for dependencies.
• 14:25 - New features in Laravel 4: Mail, password reminders, job queue.
• 17:26 - Did he consider Zend? Not really, he mentions he was fairly new to the PHP landscape at the time and hadn't really tried it.
• 19:30 - Building a community.
• 33:50 - The name Laravel comes from rhyming with castle Cair Paravel in Narnia.

Want to learn more about Laravel? Check out the Laravel 4 Video Tutorials.

submitted by mitchmckenna to programming [link] [22 comments]