Skip to Content


Drupal @ Penn State: Drupal speed tuning: analyzing and further optimizing Pressflow

Planet Drupal - 8 April 2015 - 6:06am
If you've read my past posts on here, you'll probably find a trend: I'm obsessed with performance tuning. Any time you can get more responsiveness without more hardware, I'm very, very happy. I've been running a modified drupal core for ELMSLN for some time now and decided instead of keeping these changes / tuning to myself, I'd try and document them / test them and see if any changes make sense for pressflow. In you can see 3 folders: _PATCHES - all the patches (from utilized in the metrics _RECIPES - a drush recipe that auto optimizes to the level used in testing, there are also recipes for each of the sites in the test so you can see exactly what was used for testing. _METRICS - XLS file with detailed metrics of how testing was performed, where, and what combinations
Categories: Drupal

Drupal @ Penn State: Drush recipes cookin' up sweet beta eats!

Planet Drupal - 8 April 2015 - 6:06am
Drush Recipes has come a long way since the project was first announced on planet a month ago.
Categories: Drupal

Drupal @ Penn State: ELMSLN optimization: Cost and Scale

Planet Drupal - 8 April 2015 - 6:06am
I did a post the other day about ELMSLN Performance Optimization all about lessons learned and looking at some popular techniques and applying them. These are techniques that can be applied to ANY Drupal (and in many cases non Drupal) application to increase performance. This article looks at the real world price of performance tuning.
Categories: Drupal

Drupal @ Penn State: ELMSLN performance tuning

Planet Drupal - 8 April 2015 - 6:06am
Update 2: Apache tuning / Costs There’s another posting thats dedicated to the cost and scale metrics of ELMSLN vs D6 legacy systems we were using. This is an example performance pack of conf settings that should work to do sane tuning on ANY apache system let alone drupal.
Categories: Drupal

Drupal @ Penn State: Drupal, Singularity, Digital Activism, and saving our institutions

Planet Drupal - 8 April 2015 - 6:06am
It is as important to tell a great story using technology as it is to author technology that allows more stories to be told.
Categories: Drupal

Make Some Noise! Getting a Job Creating Sound and Music for Videogames. - by Will Morton Blogs - 7 April 2015 - 11:15pm
In this long and detailed post I will lift the curtain on what employers look for in video game audio staff, distilling 15 years of experience on both sides of the employment fence to give aspiring video game sound designers and composers a head start.
Categories: Game Theory & Design

Color-Coded Pink and Blue - by Sande Chen Blogs - 7 April 2015 - 11:15pm
In this article, game designer Sande Chen explores the notion of girl and boy games and wonders if it's time to cease such labeling.
Categories: Game Theory & Design

A living guide to the GDC Vault - by Francisco Souki Blogs - 7 April 2015 - 11:15pm
Here's a log of the ~100 GDC talks I've watched with fellow game developers, with ratings and tags so you can find the best ones and the free ones.
Categories: Game Theory & Design

You’re solving the wrong problem - by Samuel Rantaeskola Blogs - 7 April 2015 - 11:15pm
When once again faced with the problem of the team being overloaded. Are you solving the right problem?
Categories: Game Theory & Design

Motivational Concepts in Video Games - by Tim Eckert Blogs - 7 April 2015 - 11:15pm
What are the different kinds of motivational concepts that some games utilize, which resulted in a younger me playing these games all the time and missing important lessons in school in the process?
Categories: Game Theory & Design

Longitudinal relation between videogames use and sexist attitudes among German video game players - by Wai Yen Tang Blogs - 7 April 2015 - 11:15pm
The study assessed the relationship between video game use and sexist attitudes, using data from a representative sample of German players aged 14 and older.
Categories: Game Theory & Design

16 Reasons Why Players Are Leaving Your Game - by Nathan Lovato Blogs - 7 April 2015 - 11:15pm
Players leave games. According to Marc Robinson’s 2013 GDC talk, “On average, less than 40% of players return to a free-to-play game after just one session.” The best way for us to retain player is to know what scares them away. Here are 16 reasons.
Categories: Game Theory & Design

Gamification, Rewards & Learning - by Richard Atlas Blogs - 7 April 2015 - 11:15pm
In this article, I'll talk about gamification and its application in learning, and why we have to be careful about using it badly.
Categories: Game Theory & Design

What was that great idea again? - Why you should document your ideas early - by Justin French Blogs - 7 April 2015 - 10:58pm
The following blog post is taken from our weekly blog post over at - This week we wanted to discuss the issues we've had with documenting our project using the traditional GDD.
Categories: Game Theory & Design

Patent Blaster: A Retrospective - by David Stark Blogs - 7 April 2015 - 10:58pm
...a giant orange hovering duck shouting "Yes! Yes! Yes!" while occasionally emitting smaller ducks that turn into acid-spitting zombies upon death. My first foray into self-publishing a game.
Categories: Game Theory & Design

Modules Unraveled: 132 How and Why Acquia is Training Drupal Talent Before They Hire Them with Amy Parker - Modules Unraveled Podcast

Planet Drupal - 7 April 2015 - 10:00pm
Published: Wed, 04/08/15Download this episodeAcquiaU

While this episode might end up sounding like a giant advertisement for AcquiaU, it’s really not intended to be. I wanted to have you on to talk about the concept of, how a company that hires Drupal developers, can and should go about training them before they are hired.

In order to set the backdrop for the rest of our conversation, I’d like to quote a bit from the AcquiaU website:

The challenge the community is facing is one of supply and demand. Simply put, there just aren’t enough people to fill the needs. At any given time in the past 6 months, job aggregator has over 2,500 open position across the US for Drupal talent.

How do we close the gap? Find the people with the right passion and grow their talent from the inside-out. We're not looking for people with years and years of Drupal experience. We're looking for people who are curious, motivated, determined, and who can inspire a little crazy in us all. At Acquia, culture and a person's POTENTIAL to contribute and grow with us matters. A lot. These are the underpinnings of a successful candidate.

What I love about that is that you’re not looking for senior level developers with 5+ years experience. Because you’re not going to find them. They all already have jobs.

Mike and I ranted about that in the last podcast, so I won’t rehash it here, but what we boiled it down to is that Drupal shops need to create a talent pipeline for recruitment, which, as I understand it, is essentially what AcquiaU is for Acquia.

Ok, with all that said, I’ll shut up now, and let you do the talking.

  • Can you give us your description of what AcquiaU is?
  • The program is 14-weeks of hands-on training in Drupal, Acquia Products, related web technologies, and professional development skills like team building, leadership, and communication skills. We spend the first 6 weeks in a classroom environment, which is a combination of lecture, group projects, individual assignments, and self-paced learning. The most recent graduates’ project was to redesign the program’s website, Each participant is assigned an Acquia Mentor who is there to not just be a buddy, but to help from a technical perspective. The next 8 weeks are spent with job rotations where they work with our customer facing Professional Services developers and customer support. Each person is assigned a client team and works side-by-side on real projects. You might think it is like any other tech bootcamp out there but we differentiate ourselves in a couple of key areas. First, we make sure we have an open job opportunity for each person who joins the program and second, we pay people to learn. Many other bootcamps have a high cost- on average up to $10,000 and while they help with job placement, I can’t say how many have jobs lined up for graduates BEFORE they join the program.

  • How do you select your candidates? Or can anyone join the class?

  • We have a rigorous screening process and look for people with 2-3 years of technology experience, but who might not be able to get a job with a development shop. A lot of times, this level of talent is overlooked because companies don’t have the internal mechanisms to train, mentor, and coach junior level talent. They are already stretched thin and want new hires to hit the ground running at a fairly high level of proficiency.

  • What types of skills do you teach?

  • We dive deep into Drupal and other web tech skills like Drush, GitHub, and Agile and a dive into our own products and services. Helping people become well rounded also means that we do workshops in team building, communication skills, and presentation skills. The next session will have an engineering focus so we will be digging into LAMP stack and web architecture.

  • Do the students have any obligation to Acquia at the end of the program? (Like they have to work for you for a given time period after the program?)

  • People are hired on as temp employees and we really hope they have had a great experience and want to stay on. The program’s goal is to hire them at Acquia or with one of our partners.

  • What percentage of students would you say you hire on average?

  • So far we have a 90% hire rate. The goal for 2016 is to expand the program and hire more people into other Drupal shops

  • Do you have information about those that you don’t hire? Do you know if they’re employed somewhere else? Or did they decide Drupal wasn’t for them?

Expanding the Concept
  • Now that you have a few classes under your belt, is this something you think other shops should look into doing?

    • People have asked me this and I think they should think about what the end goal is. Our program is not to just train more people for Acquia, but to give back to the Drupal community by creating a long-form drupal training program with learning paths and a structured hands-on curriculum.
  • We were talking before we started recording about this idea. Mike had mentioned that shops should create a talent pipeline. And while I agree with that in theory, what that means is that the shops first have to develop a training program, and one or more people who are skilled at both Drupal and teaching in a way that doesn’t alienate the trainee. From your perspective, how would you respond to that?

    • Having a talent pipleline means that you have a people development strategy that aligns to your business strategy, and that you have launched that people plan long before you launch the business strategy. Most companies play catch-up and are more reactive than proactive. Being proactive means you’re looking ahead 2-4 years out and making plans for your people.
  • If there is a shop owner out there listening right now, what would your advice be on how to go about creating a program like this?

    • I think you really have to be prepared to commit. Budgets need to allow for hiring junior talent, the business needs to be ready to bring in this level of need. It takes a lot of planning to launch a program like this. For companies that can’t support hiring 5-10 junior level talent, they should start out with a smaller number. A really strong learning program doesn’t just focus on the skills, but on different ways that people will need to learn and being able to translate really complex ideas into ways that different people will relate to. If you’ve ever heard about the adult learning cycle and experiential learning, we know that people tend to be most successful learning new skills when they can reach back into their own experience and apply them to the new content. Being a really strong developer doesn’t always mean that you can tap into other peoples’ experiences and make it relevant to them now. So when you look at creating that pipeline and having junior level talent come on board, you also have to figure out the most effective way to do it.
Episode Links: Amy on TwitterAcquia on TwitterAcquiaU on TwitterAcquiaU WebsiteTags: JobsCareersHiringplanet-drupal
Categories: Drupal

Promet Source: My Experience with Acquia Certification

Planet Drupal - 7 April 2015 - 2:03pm
My Advice


Preparing for the exam:

- Review this great guide: Five Steps to Get Ready for the Acquia Certified Developer Exam (pdf)

- As the guide says, review topics (in the pdf appendix) and identify your weaknesses, read up on your weaknesses.

Categories: Drupal

Drupal Easy: Drupal Goes to College

Planet Drupal - 7 April 2015 - 1:04pm

DrupalEasy is so excited to announce that we are teaming up with Stetson University to present the first comprehensive, university-based Drupal career professional development program in Florida! The Drupal Career Certificate Program (DCCP), which is built on DrupalEasy’s Drupal Career Starter Program curriculum, marks an official entrance to the Drupal talent pipeline through the US higher education system. The DCCP, now part of the university’s Boundless Learning programs, will be officially announced at Florida DrupalCamp 2015!  The first course will kick off this Fall at the Stetson Celebration Center located right in the middle of Florida's High Tech corridor on the outskirts of Orlando.


read more

Categories: Drupal

Potx exportables

New Drupal Modules - 7 April 2015 - 12:54pm

This module aims to ease the deployment of translation .PO files that the great Potx module generates. No longer will you have to manually upload these files to keep your site translations up to date. You can manually batch import all PO files defined in custom modules or alternatively, you can use the always useful Drush command to make things easier for you.

Categories: Drupal

Drupalpress, Drupal in the Health Sciences Library at UVA: equipment booking system — simplify(ing) comments

Planet Drupal - 7 April 2015 - 11:52am

We don’t have a lot of feedback about how our patrons are using the current equipment booking system. There may be information that users could share with one another (and the library) if given a mechanism to do so. So as part of the new booking system implementation in Drupal, we set a task of including a commenting feature. Each reservable piece of equipment stands alone as a node so all we have to do is turn on commenting, right?


But there are a couple of things that are worth noting about that.

If you’re enabling comments on a content type, it’s probably a good idea to consider who can view (and post comments to) that content. That’s all in the permissions table.

In our scenario, we didn’t want unauthenticated comments and we didn’t want to restrict the individual equipment pages (e.g. the page for iPad copy 2) to any kind of login. The request to reserve equipment from that page would trigger the login.

The snippet from the permissions table below shows how we adjusted the comment access. Note that these will be permissions that will apply anywhere else on we’re using comments on our site … we’re not currently, but if we do in the future we’re fine with this access level.

Once authenticated, the comment form defaults to give users a text format selection option. There are advantages to users selecting a WYSIWYG format This too can be handled in the text format configurations or even the permissions table. An easier way is with the Simplify module.

Simplify gives you an interface to hide a bunch of stuff that may be noisy to users adding content — publishing options, path settings, etc.

And for comments it lets you hide text formats.

The finished product:

Categories: Drupal
Syndicate content

about seo