Skip to content

Latest commit

 

History

History
78 lines (51 loc) · 4.68 KB

INTRODUCTION.md

File metadata and controls

78 lines (51 loc) · 4.68 KB
Raw

Programming Introduction

It important to have a good understanding and consistently apply the basic fundamentals of programming. We would like you to run through the following courses:

Afterward we can get you on to the backlog on Pivotal Tracker were you can be assigned to a weekly sprint, and work on a story. Once completed it will be pushed live!

Resources

Our current stack is as follows

• PHP 7.0.10
• AngularJS 1.4.7
• Symfony Framework 3.2
• Kendo UI 2017
• MySQL 5.6.28
• Elasticsearch 1.5.2
• Amazon Elastic Beanstalk, EC2 and RDS (Production instances)

We are currently using PHPStorm IDE (download the demo, and request a full license from our team) you can follow some of their getting started video tutorials showcasing all the amazing things it does. Most of the dev team use either docker, vagrant or MAMP PRO to easily manage Apache, MySQL and PHP on our development iMacs/macbooks

You can full reference to development enviroment in SETUP.md

Backend

• PHP Documentation (Language Reference)
• Symfony2 Documentation (Getting Started, Databases (Doctrine ORM), Services, Forms, Event Dispatcher)
• Doctrine2 ORM Getting Started
• RESTful API’s with Symfony2
• Symfony2 REST API (Best Practice) (We use FOSRestBundle, NelmioCorsBundle, Swagger to document the API)

Frontend

• AngularJS Documentation
• AngularJS Phonecat Tutorial
• Kendo UI AngularJS Integration
• Kendo UI Demos (Browse the demo code, with particular attention to the AngularJS examples
• AngularJS Style Guide Opinionated AngularJS style guide for teams, endorsed by Angular team.

Github

In addition we use github.com and git for source code versioning, create a free github.com account, try creating a repository, have a play committing file, creating branches or merging either on command line or through PHPStorm.

We follow the GitHub flow branching model, which discusses feature branching, and creating pull requests .

Agile Methodology

We have standups in the morning with all members of the IT department (development and support), it good to know what team is working on, and any blockers can be raised early.

For a typical development feature:

  • Pick a story from the sprint backlog on Pivotal Tracker
  • Create a new feature branch from develop branch, feature branch must include the story ID
  • Create pull request on github for code review, or assistance.
  • Once story has been accepted the feature branch can be merged into develop branch
  • Once develop is stable, we merge to master branch and CI (continous intergration) teamcity servers automatically deploy to production.

Training

Each employee has a training budget, which can be used to purchase books, courses or material which will assist in your developments.

Every year we attend the PHP Northwest Conference which has inspiring content from speakers from all around the globe, valuable opportunities to network with the PHP community.

We encourage developers to become certified, we will set aside time to revise and train for ZCE (Zend Certified Engineer) or Symfony Certification