Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://medium.com/@alnutile/we-code-in-the-context-of-our-quoting-dab391fe0881#.6a1k99bu1 Whether you are working Waterfall, or Agile we still need to quote out the time it will take for new features . We still need to give the product owners, or the people with the money, a sense of timing. And it is this skill or lack thereof that drives the experience we are going to have when we code.

ReadOrListen

We Code in the Context of our Quoting

Author: John Ferguson Smart Author: Jan Molak Read By: Alfred Nutile Original Source: http://johnfergusonsmart.com/five-stages-bdd-agile-adoption/

The five stages of BDD (and Agile) Adoption

Author: Jesse Schutt Read By: Jack Fruh Original Source: http://zaengle.com/blog/diving-in-to-a-laravel-audit Recently the Zaengle team was asked to look over an existing Laravel application and give a review of the overall state of the code. We were to act as an independent third party, between a new studio who had inherited the codebase, and the client, who was anticipating launching the product.

Diving Into a Laravel Audit

Author: David Heinemeier Hansson Read By: Ryan MacAllan Original Source: https://signalvnoise.com/posts/2188-theres-no-room-for-the-idea-guy Startups need people able and willing of doing the actual work. They need programmers, designers, and eventually folks to do marketing, support, and more. What they don’t need, though, is someone who’s just going to be The Idea Guy.

There's no room for The Idea Guy

Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://alfrednutile.info/posts/177 This document will cover how to use a Behat specific API to setup a site for testing. What this includes is setting up a Scenario so that it has the data you need to run a test. This makes it possible not to rely on Seed data for this. This will allow us to run behat tests from remote machines as well as run tests in parallel.

Remote Behat Testing with Laravel

Author: Matthew Machuga Read By: Alfred Nutile Original Source: http://matthewmachuga.com/blog/2015/activerecord-and-the-beauty-lost-in-translation.html

ActiveRecord and the Beauty Lost in Translation

Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://alfrednutile.info/posts/175 We are working on using FeatureFlags or Toggles in our applications. For one we are aiming to do all our work on mainline branch at all times so this would be a key coding discipline to use FeatureFlags so we can hide a feature in progress knowing it will not interfere with the application. For example if a hotfix or another feature is ready to go to production we can push that with no worries of the in progress feature.

Feature Flags In Laravel

Author: Lorna Jane Mitchell Read By: Lorna Jane Mitchell Original Source: http://www.lornajane.net/posts/2015/git-pull-causes-a-merge If you type git pull and expect a fast-forward update, but get a merge instead, don't panic! This usually happens when we're collaborating on a branch with other people, and we've made changes on our local version of a branch, and someone else (or the other you, if you use git to sync between multiple dev platforms) has made changes to the remote version of a branch in the meantime. It also happens really frequently in teams where all commits are to the master branch ... yet another reason to have a decent branching strategy.

Git Pull Causes a Merge

Author: Lorna Jane Mitchell Read By: Lorna Jane Mitchell Original Source: http://www.lornajane.net/posts/2014/using-composer-without-gitignoring Recent additions to the joind.in API have introduced some new dependencies so we decided we'd start using Composer to manage these - but we don't want to run composer unsupervised. I'm sure this will bring the rain of "just run composer install, it's probably mostly almost safe" criticism, but actually it's quite tricky to run Composer without excluding vendor/ from source control so I thought I'd share how we did it so that anyone who wants to do so can learn from my experience!

Using Composer Without GitIgnoring Vendor/

Author: David Heinemeier Hansson Read By: Alfred Nutile Original Source: http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html It didn't start out like that. When I first discovered TDD, it was like a courteous invitation to a better world of writing software. A mind hack to get you going with the practice of testing where no testing had happened before. It opened my eyes to the tranquility of a well-tested code base, and the bliss of confidence it grants those making changes to software.

TDD is dead. Long live testing by David Heinemeier Hansson

Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://alfrednutile.info/posts/160 BETA: This is a Code Heavy Read :) Not all apps need to be an SPA (Single Page Application). Sure they have their place but in most cases the task might benefit from just a Blade template and Angular widget. This saves you from having to write an angular route which can be a tedious duplication of work. Also Blade is fast and fun to work with.

Laravel and Angular Widgets e.g. Non SPA (Single Page Application) Pattern

Author: Grant Ammons Read By: Alfred Nutile Original Source: https://medium.com/cto-school/ditching-scrum-for-kanban-the-best-decision-we-ve-made-as-a-team-cd1167014a6f#.8hh5rddu0 The following is a story about how we matured as an engineering team. We went from an ad-hoc process to Scrum, and used Scrum for a whole year. Scrum leveled us up as a team in terms of structure and process. But it caused major morale issues. Then we found Kanban. We implemented it and have never looked back.

Ditching Scrum for Kanban — The best decision we’ve made as a team

Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://alfrednutile.info/posts/172 This will cover two things. One, how helpful it can be to make a clickable Proof of Concepts (POC), not just with images, or tools the spit out html but instead just enough javascript and base theme to help "sell" the idea, or more importantly to help Product Owners see the possibilities that are not too far out of reach. And the second, and maybe more important thing I will cover is that the developer has a lot to gain in taking on this seemingly non-coding path.

Then Benefits of Building a Clickable POC as a Developer

Author: Konstantin Kudryashov Read By: Alfred Nutile Original Source: http://stakeholderwhisperer.com/posts/2014/10/introducing-modelling-by-example "For the last year I have been experimenting with the new approach to a Behaviour-Driven Development, which could be summarised as "Ubiquitous Language is a thing again". The core premise of this approach is that if you take Ubiquitous Language seriously and push for it in your scenarios, you open the door to doing a Domain-Driven Design while you're doing Behaviour-Driven Development's red-green-refactor cycle. By embedding Ubiquitous Language in your scenarios, your scenarios naturally become your domain model, which you can use to develop the most important part of your application - a core domain."

Introducing Modelling by Example by Konstantin Kudryashov read by Alfred Nutile

Author: Alfred Nutile Read By: Alfred Nutile Original Source: https://alfrednutile.info/posts/171 Some reasons why putting all library files into version control might be a good idea. You can read about it here as well https://alfrednutile.info/posts/171

Put It All Into Version Control Even Composer!

Coding and day to day developer related articles read by people passionate about learning and sharing.

hubhopper

ReadOrListen

hubhopper