749 reputation
413
bio website fergus-morrow.com
location London, United Kingdom
age
visits member for 2 years, 5 months
seen Dec 22 at 2:53

I'm a Mobile & Web Application Software Engineer, currently plying my trade at a healthcare software company in London, UK.

My pet hates include:

  • Using mysql_* methods in PHP; they're deprecated for a reason, dude.
  • Using jQuery and then doing absurd things with the DOM, or worse, using jQuery and doing next to nothing with it; it's added bloat, man.
  • Rolling your own security/authentication frameworks.

Stuff I know

Wordpress // Yii (PHP) // Laravel (PHP) // Plain ol' MySQL // PHP5 // Javascript // Node.js // jQuery // Underscore.js // Android SDK // Java // PhoneGap

Stuff I've used, but I'm actually pretty clueless about

Ruby On Rails // Spree // Objective-C // iOS SDK (The iPhone SDK back then?!)


Sep
24
awarded  Autobiographer
Sep
8
comment Git collaboration with pull request in a company
Git doesn't do Branch permissions out of the box as far as I know, unless you're running your own server and you use something like Gitolite. If you use "Git-flow" you can help minimise the risk of this happening accidentally somewhat, however there's no way to stop it happening purposefully as far as I know. (I'm going to post an answer with a potential solution)
Sep
8
comment Git collaboration with pull request in a company
There's no reason to have different repositories for production and master. It may be worth looking at Git Flow; if only to take away the ideas about having a 'develop' branch for testing, a 'master' branch and 'release-' branches for releases. Combined with tagging properly, this can enable you to keep track of releases, use one single repository and constantly have access to all releases - legacy or not.
Jul
16
awarded  Yearling
May
9
comment How to insert/update a large amount of data into mysql using php
You can change the settings regarding PHP execution time limits, which would solve the time out issues. This question may be more suited to StackOverflow though as it's bordering on specific implementation details.
May
6
answered Develop a website using mustache.js and PHP
Apr
26
revised Combining two MVC frameworks in a project
added 449 characters in body
Apr
26
answered Combining two MVC frameworks in a project
Mar
27
comment Tight Coupling Between Javascript, HTML, and CSS: A More Modern Approach?
Brilliant answer, +1. If only for mentioning data attributes as a mechanism for avoiding tight coupling
Mar
27
comment Tight Coupling Between Javascript, HTML, and CSS: A More Modern Approach?
Poor advice in my mind, especially when it comes to writing modular/reusable JS that should make no assumption on selectors. Data attributes are a better idea for these scenarios.
Mar
27
comment I'm looking for recommendations or advice on how to improve our workflow?
Swap 3 and 4. Get development in immediately, there's no point development reviews starting after client feedback. Feasibility assessments should be iterative throughout the design process in my mind, it's something that I'm trying to push for where I am at the moment. Unfortunately I think this is an issue that permeated throughout many digital agencies, where design is placed above every other discipline - leading to misunderstandings, confusion and general issues that are actually avoidable.
Mar
5
awarded  Enlightened
Mar
3
awarded  Good Answer
Mar
3
comment How does working in a team (in an OO project) work?
@yannbane Oops, I did indeed!
Mar
3
revised How does working in a team (in an OO project) work?
deleted 2 characters in body
Mar
2
awarded  Mortarboard
Mar
2
awarded  Custodian
Mar
2
reviewed Approve How does working in a team (in an OO project) work?
Mar
2
awarded  Nice Answer
Mar
2
comment How does working in a team (in an OO project) work?
Thanks @DocBrown! @Prog - That's a very interesting question, and not one I'm entirely sure I can answer! Speaking from experience though, it seems entirely common for that kind of situation to exist at the beginning - or when a feature is being implemented. A developer may take ownership of their new feature (and thus, any new objects implemented) - however, when it gets merged back in to the codebase and maintenance commences it's very much whoever gets assigned a specific bug, hunting down that bug to wherever it actually lives!