Research contributions when problems are already solved

Posted on Tue, 10/08/2013 - 10:41

What happens when there are a lack of open problems? On the surface, it seems to make it more difficult to have impactful contributions. I just think it requires you to think outside of the box. Drupal is a great platform to look at this issue. A few nights ago, I was using my online banking system which required me to answer security questions as a form of two-factor authentication. I thought this would be a great problem to solve in Drupal. However, this is a solved problem: https://drupal.org/project/security_questions How does one contribute when problems are already solved? Let's consider

development drupal people

Design issues of a distributed Drupal system

Posted on Thu, 10/03/2013 - 13:22

Scale and performance are major issues for high traffic websites. The design of the Drupal system poses many challenges to building a distributed system that can support load balancing. In Drupal, the design of the system has three principle components: code, database, and files. I will be sharing potential solutions in later blog posts. Code: This includes Drupal core and the modules that run on the web server. By running multiple web servers, you need to ensure the code is consistently maintained during deployments across all of the servers (see: continuous integration). The issue of timing

development drupal

Learning is giving, not just receiving

Posted on Thu, 09/26/2013 - 21:13

I recently read this article: http://bryanbraun.com/2013/09/21/please-stop-stewing-and-start-blogging… You can't ask for a better justification to throw up a blog and share some information. It made me realize a few things. First: You have an opportunity to help others out because you most likely learned something someone could benefit from. Second: Don't be shy. If anything, someone may post a comment and share information with you again. Third: Tools like Drupal were built by people who were not afraid to give back. Step up and take your turn.

drupal people

Don't solve the same problem twice

Posted on Wed, 09/18/2013 - 23:04

If you spent hours solving a problem, what is the likelihood you will remember exactly what you did the next time it comes around? Don't solve the same problem twice. Find a way to automate routine tasks so you can focus on other challenges. What are some strategies used? Let's start by proposing a frame of reference: We have features, representing software requirements or components We have tools, which create or support features We have configuration, which sets options or behaviors of tools for use in features Let's consider the following example. A restaurant has content management needs

development drupal