I know it’s easier said than done. There are at least as many articles on this as there are stars in our galaxy. Or may be more.

But the hard truth is that the world’s still full of people who find no time to code their pet project into a full-fledged app. And it’s more or less a self-discipline issue.

Finding time to code is one of the hardest things to do if you’re working full-time and doing the code in your ‘free’ time, which is typically the evenings/nights and the weekends. Quite a lot of hobbyists find it easy to code simple “hobby projects” that won’t see the light of day on the App Store (or even GitHub) but when it comes to serious coding, trouble starts at the time-management level.

There’s always a time to code. “I haven’t got the time to code/test/debug” isn’t a good excuse even when you’re in a full-time job and it all boils down to two things: sacrifice and self-discipline.

I’m sure most of what you are going to read is advice you’ve heard (possibly a million times before). For the benefit of those who’re starting the first lines of their app and for those who’re struggling to manage time to code, here are some things you should always, always remember:

1. There’s No Coding in Small Chunks

If there’s one lesson I’ll take to my grave after having spent a considerable chunk of my lifetime writing code, it’s this: there’s nothing called ‘code in small chunks’. This ‘do it in small measures’ thing might work elsewhere but no, sir, not when you’re coding.

A few lines of CSS and jQuery can take away more than an hour of your time even if you’re smart and can write semantic code on paper like Steve Wozniak.

If you think you’ll come back from office, do a little of this and that and then sit to code for about an hour, I suggest you forget that idea. Code is something that takes away a lot of your time and if you want to get it done, you’ll need to, more often than not, forget time. That means forget setting time limits to code.

2. There’s Something To Sacrifice

Evening visits to the gym can be shifted to the mornings if you code well in the night. A handful of weekend parties can be skipped. Webinars/Seminars on development can be missed. Or if things come to a head-on, a dine-out can be sacrificed for those few hundred lines of code that’ll fix the core part of your project.

There’s always something that you can sacrifice. For me, it has been – for sometime – reading books in the night. Club that with a couple of other things like an evening stroll (about an hour) and TV and you probably get more than enough time to code your way to heaven.

Figure out your routine. Then, cut out stuff that can be sacrificed for precious coding time.

3. Set Up A Distraction-free Environment

There’s this thing called Zero Clutter work zone. It’s basically about de-cluttering your work-zone so you can work distraction-free. And while Leo stops at the physical level of de-cluttering, you can (and should, definitely) take it to the next level: your screens.

When you are coding, have nothing more than one thing in focus: the IDE that you’re working on.

It takes a lot of self-discipline not to:

- check email every two/five/ten minutes
- constantly compile the code every time you make a minor change
- open and refresh Facebook/Twitter/App.net or HN every once in a while
- flip your phone to check messages
- munch on a bagel or fries (drink water; that’s a healthier practice)

Everything other than the IDE is a distraction. If you’re writing a caching program, do just that till you get to a point where you start debugging the code (once it’s totally complete). If you’re writing a regex, finish that totally (test, debug) before you even think of opening a new window in Chrome.

Use a blocking program to keep you off from Gmail, Facebook, HN etc. Keep the phone away – preferably in a different room so you get up only to pick a call.

Little but effective disciplinary changes can help you a lot in focused coding: which translates into less time, more code.

Like I said, it all boils down to self-discipline. And of course, a few hacks like a distraction-free environment (Sublime Text 2, may be?) and a lot of burning the midnight oil (or, if you’re a morning person, getting up a lot earlier than before).

Image by Flickr User Toni Verdú Carbó

These 7 tips will help you transform your most difficult clients into big marketing victories.

Watch out! Here comes Gladys. Or maybe it's Tim, Nelly, or Nigel. Whatever the name, this client is cranky and snappish, making even the most skilled professionals run for cover. Is it possible to convert this cantankerous customer into a fan?

Success coach and international speaker Marilyn Suttle offers a resounding yes.

In her best-selling book, Who's Your Gladys? How to Turn Even the Most Difficult Customer Into Your Biggest Fan, Suttle recognizes that most any business has their Gladys, and it can be a huge challenge, but there is hope. "When you practice emotion management and grow your creative problem-solving abilities, magic happens," says Suttle.

Here are Suttle's seven tips to turn tough customers into devoted fans who spread good news about your company. To learn more about creating world-class customer service, tune in to my interview with Suttle on Million Dollar Mindset radio.

1. Thank your customer for complaining, and mean it.

The most calming phrase you can say to a complaining client is, "Thank you for telling me." A genuine thank-you can be disarming. Be thankful that your customer is willing to tell you what most won't. It's a gift that may offer you insight into problems that other customers aren't willing to share. Eighty-nine percent of unhappy customers will simply take their business elsewhere without telling you why. Instead, they tell everyone else: their families, friends, and everyone in their social-media networks. When they do tell you, follow up your gratitude with, "I'm so sorry. Please tell me more."

2. Soothe yourself when customers rant.

When you're on the receiving end of a Gladys attack and your customer is angry and venting, do you bristle inside? Feel annoyed and defensive? What can you do? Soothe yourself. Tell yourself, "Venting is good. I choose to be calm and capable of creating a safe space for my customer to feel heard." Jumping in with a solution before a customer has fully expressed herself only makes things worse. Not until the negative feelings come out can good feelings flow in. (Much like turning on the shower--the icy-cold water comes out first before that warm water flows.)

3. Take the high road.

The customer isn't always right--but their perception of that matters. Managing perceptions is a necessary part of long-term success. Resist the urge to point fingers, pass blame, or make excuses. Instead, take ownership of the situation and restore trust. Remind yourself that you don't have to prove someone wrong to set things right. Before saying anything, ask yourself, "Is what I'm about to say truthful, useful, kind, and unifying?" If not, don't say it.

4. Get comfortable with conflict.

No one wakes up in the morning thinking, "I'm so glad I get to have a tough conversation with my client today." Conflict is uncomfortable. Even so, disruption is sometimes necessary for better results, deeper understanding, and stronger relationships to emerge. Avoiding a conflict doesn't make problems go away. You may get a temporary retreat from a client's displeasure by avoiding an angry phone message or email, but the longer you put it off, the harder it is to recover. It's a proven fact that when conflict is resolved well, a customer can become an even more devoted fan than they would have if there was never a problem in the first place. Managing conflict well builds trust and loyalty.

5. Pivot toward thoughts that inspire excellence.

How you think about your customers influences how you respond to them. It's so easy to slip into unhelpful thinking like, "My customer makes me want to pull out my hair and run screaming from the room!" When you notice it, reach for a more resourceful thought like, "My customer's persnickety personality gives me an opportunity to use my skills to win them over." This belief activates all your inner resources and puts you in a calmer, more inspired state of mind. Put pressure on coal and you get diamonds. That's good pressure. When a customer puts pressure on you, see it as a good way for you to grow your abilities.

6. Look for the positive qualities in your client's negative behavior.

Depending on your view, you can describe a customer as being "loud and demanding" or "excited and tenacious." When you look for the positive qualities in your challenging customer, you increase your ability to connect. Begin noticing the positive qualities and your clients will start responding to you differently. Consider "rude" as "willing to say what's on her mind." View "wishy-washy" as "someone who likes to weigh options."

7. Be prepared for service recovery.

When it comes to doing business, it's not a matter of if something will go wrong, it's a matter of when. Don't be surprised when it happens; be prepared. Ask, "How can I set things right and make you happy?" Often customers ask for a lot less than you might think, because what they really want to know is that you care. Go above and beyond to take care of them when things go wrong and you'll gain their loyalty.

Building a minimum viable product — something that can show what you want to do to prospects and perhaps even start bringing in a little money to help you fund the development of a bigger product — makes a lot of sense. It’s especially useful when your product is solely the result of the hours you spend at the computer: minimizing those hours to test the basic concepts means that you can discover what does and doesn’t work a lot faster.

But deciding on just what you’ll offer as your MVP isn’t always easy. Some projects have a small core component that you’ll have to build anyway to get started, making for a quick decision. But many projects have a lot of moving parts and it’s not always simple to decide which parts need to be tested first. These tips can help you make a decision.

1. Make some lists. It may seem old-school to just sit down and think about your product, but write out a list of the reasons the full product will be attractive to your customers. Create a list of the smaller pieces of the project that you could complete without building the whole structure, and note the pros and cons of using each piece as your MVP. Don’t limit yourself to what you can build, by the way. If you can mimic the function of an app by hand for your users or rely on a couple of APIs to get started, include those options.
2. Schedule interviews with your ideal customers for the full project. Unless you are also a member of that audience, it’s hard to tell what you’re assuming to be true and what that audience actually believes. Take your list and start asking questions. You may find that one small piece of your project is exactly what gets that audience excited.
3. Put together a short plan for actually building each of your contenders for MVP. Some options will be more minimal than others, at least in terms of what you need to build to make it available. Consider details like whether you prefer test-driven development and how they might slow certain options down.
4. Plan how you can test and gather data about the finished product. If you can’t find out how audiences respond to your MVP and what you need to change, then you’re not looking at a practical MVP. This needs to an experience you can easily learn from.
5. Decide what part you’re excited about. The coding always goes faster when you’re working on something you actually want to finish. If a lot of your potential MVPs aren’t exciting you, skip over them to something that you’ll be happy to put extra hours in on.

Image by Flickr user Gangplank HQ