{"id":149411,"date":"2015-12-21T11:00:41","date_gmt":"2015-12-21T11:00:41","guid":{"rendered":"http:\/\/premium.wpmudev.org\/blog\/?p=149411"},"modified":"2016-04-29T06:47:55","modified_gmt":"2016-04-29T06:47:55","slug":"wordpress-dev-fears","status":"publish","type":"post","link":"https:\/\/wpmudev.com\/blog\/wordpress-dev-fears\/","title":{"rendered":"WordPress Fears: The Little Things That Scare Developers"},"content":{"rendered":"<h2>Developing websites comes with its own unique brand of challenges. Even if you&#8217;re very good at what you do, you&#8217;re still going to face issues now and then, especially since it&#8217;s a client-driven industry.<\/h2>\n<p>And when those issues arise, it&#8217;s likely to send a mini-wave of panic through your body. Though it&#8217;s likely you take a deep breath and approach the problem as calmly as you can, that doesn&#8217;t mean you&#8217;re not internally screaming the whole time. Until you hand over the keys, so to speak, your site projects are likely filled with biggest development fears come true. That&#8217;s okay, though. Especially since we&#8217;re all in this together and we&#8217;ve all been there before.<\/p>\n<p>But what about specifics? What things trigger that undeniable sense of dread?That&#8217;s what we&#8217;re exploring here today in tongue-firmly-planted-in-cheek fashion.<\/p>\n<p>That&#8217;s what we&#8217;re exploring here today in tongue-firmly-planted-in-cheek fashion.\u00a0<!--more--><\/p>\n<h3>1. &#8220;So, I Have This Idea for a Website&#8230;&#8221;<\/h3>\n<p>Ideas are a dime a dozen. Truly. So unless a potential client comes to you with a well-considered budget, that &#8220;idea for a website&#8221; is unlikely to see development. Too often, this phrase is uttered when someone&#8217;s looking to have a site built for free. Which is, just, no.<\/p>\n<h3>2. &#8220;It&#8217;s Really Easy!&#8221;<\/h3>\n<p>Uh-huh. Sure it is. And I bet it could be completed in ten minutes, too. If it&#8217;s really all that easy, the client would&#8217;ve done it himself. When someone says this, they&#8217;re hoping to get something for nothing, which makes developers want to run and hide.<\/p>\n<h3>3. &#8220;I&#8217;ll Google the Problem and Fix it Myself&#8221;<\/h3>\n<p>While taking initiative is something that should be praised, it&#8217;s often a source of dread for developers. When a client refuses a developer&#8217;s offer to fix something and insists on doing it himself, he&#8217;s more often than not trying to go cheap and avoid having to pay for site maintenance. Unfortunately, a site in untrained hands can be dangerous. This leaves many developers shaking in their boots at the thought of all their hard work getting destroyed.<\/p>\n<div  class=\"wpdui-pic-right  \">\n\n\n\n<figure><img loading=\"lazy\" decoding=\"async\" class=\"attachment-490x490\" src=\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2015\/12\/perfection.png\" alt=\"perfection\" width=\"490\" height=\"312\" \/><\/figure>\n\n<h3>4. When the Client Insists on Perfection<\/h3>\n<p>I mean, really? Why on earth do you need that PSD to line up 100% with the live site? Unless you literally overlay that file onto the live site, no one&#8217;s going to notice anyway. Not to mention the slight changes that appear in cross-browser tests.<\/p>\n\n\n\n\n<\/div>\n<h3>5. Local Server or Software Crashes<\/h3>\n<p>Nothing like a server crash to liven up your day! And it always seems to happen right when you&#8217;re in the middle of something super important. A crash requires relaunching the server, reloading the site, and getting everything open again, which breaks workflow and can result in a need to redo work, too.<\/p>\n<h3>6. When a Plugin Update Breaks Your Site<\/h3>\n<p>Ugh. This happens way too often. You&#8217;re like, &#8220;hey I&#8217;m going to update all my plugins right now&#8221; and you click the button and then your site goes all whitescreen. It&#8217;s the worst and enough to make you stop everything and panic, hoping against hope you&#8217;re backed up your site recently.<\/p>\n<h3>7. When You install a Plugin and It Causes Conflict<\/h3>\n<p>This is sort of like when you update a plugin and it breaks stuff, only it refers to those times you think, &#8220;Hey, this feature would be great to add to my site,&#8221; and you install the plugin on a whim and your site goes all whitescreen again. No fun. And emphasizes the importance of developing on a local server. That way you can be sure there are no plugin conflicts before your site is visible to the world.<\/p>\n<div  class=\"wpdui-pic-left  \">\n\n\n\n<figure><img loading=\"lazy\" decoding=\"async\" class=\"attachment-490x490\" src=\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2015\/12\/checklist.png\" alt=\"Checklist\" width=\"490\" height=\"312\" \/><\/figure>\n\n\n<h3>8. &#8220;This Looks Good But I Need Changes&#8221;<\/h3>\n<p>The words that strike fear into the hearts of many a developer. While the client will more than likely just need a few tweaks here and there, there&#8217;s always that risk of a total design change that in the client&#8217;s mind should, &#8220;only take five minutes.&#8221; Gah!<\/p>\n\n\n\n<\/div>\n<h3>9. Sudden Changes in Project Scope<\/h3>\n<p>Scope creep is real and it&#8217;s hazardous to your productivity and bottom line. Revisions are expected but when a client keeps adding new features to the project and doesn&#8217;t want to pay more for them, you&#8217;re truly in scary territory.<\/p>\n<h3>10. Terrible, No Good, Very Bad Content<\/h3>\n<p>The best site design and layout in the world isn&#8217;t going to fix awful copy. It&#8217;s truly terrifying when a client has invested in a nice-looking site but couldn&#8217;t care less about how the content reads. Then you have to walk that line between mentioning it or just taking the payment and high-tailing it out of there.<\/p>\n<h3>11. &#8220;We Don&#8217;t Have a Big Budget&#8221;<\/h3>\n<p>Some clients truly mean these words and have full plans to increase their development budget later. But more often than not, clients mean &#8220;we&#8217;re just starting out and don&#8217;t have money for a site but want one anyway\u2014want to make one on the cheap for me?&#8221;<\/p>\n<h3>12. &#8220;It Can Be a Portfolio Piece&#8221;<\/h3>\n<p>This one makes devs want to run away fast. See also &#8220;free gig&#8221; and &#8220;for exposure.&#8221; Makes me shudder in fear just thinking of it.<\/p>\n<h3>13. The Text Editor Crashes and You Haven&#8217;t Saved<\/h3>\n<p>Oh, the horror! You&#8217;ve poured blood, sweat, and tears into those lines of code, only to see them vanish in a moment of poor computer function. I compulsively Command + S every ten seconds it seems for this very reason.<\/p>\n<h3>14. The Site Gets Hacked<\/h3>\n<p>Is there anything worse that finding out a site you built has been taken down by hackers or infected with malware? And you certainly don&#8217;t want to have to spend your time cleaning up the mess. If you have a good backup system in place, at least the cleanup effort shouldn&#8217;t be <i>too <\/i>bad.<\/p>\n<h3>15. &#8220;I Know You&#8217;ve Been Working on This Design But I Just Found This Theme\u2026&#8221;<\/h3>\n<div  class=\"wpdui-pic-right  \">\n\n\n\n<figure><img loading=\"lazy\" decoding=\"async\" class=\"attachment-490x490\" src=\"https:\/\/wpmudev.com\/blog\/wp-content\/uploads\/2015\/12\/scared.png\" alt=\"Scared\" width=\"490\" height=\"312\" \/><\/figure>\n\n<p>While there&#8217;s no law that says once someone hires a developer they have to stop looking at other designs and themes, it&#8217;s frustrating when the continued research slows down project progress. Devs fear getting stuck in the feedback loop with clients who want revision after revision based on &#8220;this cool thing&#8221; they just found.<\/p>\n\n\n\n\n<\/div>\n<h3>16. Learning a New Trick Right Before a Site is Done<\/h3>\n<p>And said trick could&#8217;ve saved you a ton of time on the development process. The fear of time wasted is real.<\/p>\n<h3>17. &#8220;Needing&#8221; Too Many Plugins<\/h3>\n<p>When a client wants every feature under the sun on their site, it&#8217;s easy to go the plugin route. But too many can slow down the site you&#8217;re working hard to build. And manually adding in functions is time-consuming. It&#8217;s the ultimate catch-22.<\/p>\n<h3>18. Slow Load Times<\/h3>\n<p>You&#8217;ve optimized your images, reduced the number of plugins you&#8217;re running to the bare minimum, and minified your code, and pages are still loading much too slowly. Terrifying, to be sure.<\/p>\n<h3>19. Improperly Sized Images<\/h3>\n<p>Speaking of slow load times, it can be downright frightening when your client begins to create content and uploads images that haven&#8217;t been resized or compressed. Holy slowdown, Batman!<\/p>\n<h3>20. When the Client Becomes Non-Responsive<\/h3>\n<p>You&#8217;ve submitted the final site and your inbox is quiet. You stalk the client&#8217;s social media and they&#8217;re even being silent there. Did they take an unexpected online break? Or are they dodging you to avoid final payment? It&#8217;s enough to make an overworked developer hyperventilate.<\/p>\n<h3>What Are You Afraid Of?<\/h3>\n<p>WordPress developers and implementers, alike all have at least one thing that leaves them shaking in their boots. So now I want to hear from you. What&#8217;s something during the development process that scares the daylights out of you or makes you panic? Share or confess below because I&#8217;m sure you&#8217;re not alone in how you feel!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We&#8217;ve yet to meet a WordPress developer who didn&#8217;t panic about some aspect of the development process. Here, we outline some common fears and why they&#8217;re just so scary.<\/p>\n","protected":false},"author":344989,"featured_media":150312,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"blog_reading_time":"","wds_primary_category":0,"wds_primary_tutorials_categories":0,"footnotes":""},"categories":[10468],"tags":[],"tutorials_categories":[],"class_list":["post-149411","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-reviews-opinion"],"_links":{"self":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/149411","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/users\/344989"}],"replies":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/comments?post=149411"}],"version-history":[{"count":6,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/149411\/revisions"}],"predecessor-version":[{"id":215815,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/posts\/149411\/revisions\/215815"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media\/150312"}],"wp:attachment":[{"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/media?parent=149411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/categories?post=149411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tags?post=149411"},{"taxonomy":"tutorials_categories","embeddable":true,"href":"https:\/\/wpmudev.com\/blog\/wp-json\/wp\/v2\/tutorials_categories?post=149411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}