"It is not enough to do your best; you must know what to do, and then do your best" —W. Edwards Deming
Read one developer’s story about navigating the stormy waters of developing websites for colleges and universities for more than a decade.
The web was born in the world of higher education and research institutions. Starting first as a tool for sharing information among researchers and educators, it has expanded in the three decades to connect to practically every portion of our lives.
Your CMS, digital asset management software, or DAM, and Pantheon’s website operations platform can be friends. That’s what I say to anyone who worries if their file and workflow management will integrate nicely into Pantheon. And yet, questions persist because DAMs are like mega-homes for media assets and we know real estate deals can be messy.
In this post, we break down how to set up and configure Autopilot. Dive in to learn more.
Joel Hughes is SVP of eMedia & Information Technology at Scranton Gillette Communications, a fourth-generation family-owned business-to-business communications company, named by Folio magazine as one of the 40 fastest-growing companies — and an “All Star” in the magazine industry.
Approximate Reading Time: 7 Minutes
At Pantheon, we do our best to make building, launching and maintaining a Drupal or WordPress site as easy as possible. All sites on our platform get the same PHP and MySQL configurations tuned for their applications. Every site has Varnish sitting out front to provide speed and protection against surging traffic. Our Dev/Test/Live workflow helps ensure only quality code makes it to production. Multidev allows teams to work on new features in isolation. And database backups are very easy to move around between environments.
As Spring rolls forward, it is that time of year again for DrupalCon, which is in Seattle, WA this year. I got the chance to sit down with the longtime Pantheon Hero, Duran Goodyear, founder of Alphex Information Solutions. He shared his thoughts about the event, the community, and Pantheon. Watch the full video and read highlights below.
The way people use the phrase “technical debt” implies that good, tested code is debt free. If you are building a software service this is wrong; every line of custom code you maintain is debt.
To be competitive, software products must continually improve. All of the custom code you’ve written yesterday, rewritten today, and what you’ll write tomorrow -- you will be burdened with maintaining, forever. To build competitive software you must balance this cost when you decide what code gets written, and what gets integrated from upstream.