One of the major parts of any software development cycle is testing. Whether that testing is performed on just one feature or an entire product I think that any developer can agree that code and product functionality needs to be tested before it is deployed. As a developer, one thing that I continuously find myself wondering is when is it an appropriate time to test my code? I wonder if it cost effective and productive to perform testing on a feature by feature basis? I wonder if I should wait until an entire section of features is completed to test functionality?
I am proud to announce that the latest version of Agnostic Dev has been redeveloped and is now up and running on top of Drupal 8. I am very happy that the entire development process went very smoothly and from start to finish only took me about two weeks. This is a significant improvement over what it took to develop the Drupal 7 version of Agnostic Dev as it took me close to a month and I did not have any content to port. Along with the smooth development process there were also many valuable lessons that I picked up about Drupal 8 along the way.
Lately I have been working with Drupal 8 trying to get my head around what it takes to create a production application in the latest version of Drupal. One of the very first snags I hit was theming. Working with the theme system in Drupal 8 is quite a bit different from Drupal 7 beings how Drupal 8 utilizes Twig as the theme engine instead of PHPTemplate. Drupal 8 was my first exposure to Twig so diving right into development came with a bit of a learning curve to get started.
Recently Trekk was gracious enough to let me switch my workstation from Windows 7 to Ubuntu 15.04. This decision to actually evaluate making the switch stemmed from a number of different reasons. First and foremost I had been holding on to an outdated version on Windows for far too long and it really was time for me to either update to Windows 10 or start to evaluate different options.