neloy-ahmed

Awesome Laravel

Dumping ground for Links

• https://gist.github.com/cjthomp/1455c39d4a14292676ea
• https://www.agvision.ro/building-api-starter-pack-laravel/
• https://deliciousbrains.com/react-laravel-lumen-company-status-board/
• http://mguimaraes.co/creating-a-fully-testable-books-review-app-from-the-ground-with-laravel-part-1/
• http://www.programmerfort.com/php-code-optimization-tips-and-tricks/
• http://blog.pisyek.com/create-room-booking-system-laravel-fullcalendar/

neloy-ahmed

There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

neloy-ahmed

Using Git

Global Settings

Related Setup: https://gist.github.com/hofmannsven/6814278

Related Pro Tips: https://ochronus.com/git-tips-from-the-trenches/

neloy-ahmed

Javascript Handbook

A hand crafted markdown document contains all major Javascript topics covered, taken from different sources. Brush Up your JS memory.

Comments

---

Single line comments start with //. For multi-line commands, you use /* ... */

// This is a single line comment