12 Code Commandment e-book Release!

Ebook Commadnment begining

What the book includes?

The 12 Code Commandments are the steps to follow when building a new software. Each commandment goes into detail of each fundamental aspect of the project and provides insight on what you should keep in mind such as:

  • Prioritizing tasks.
  • Effectively monitoring the progress of the project and your team.
  • Tips on getting the most out of your testing phases.
  • Launching successfully!
  • And much more!

Why are we releasing it as an e-book?

The 12 Code Commandments is compiled into one downloadable e-book so you can save the book in your pocket, share it with all your friends, and print it for safe-keeping. No matter what your experience level is, everyone will learn something from reading through this guide. 

Now available for Free Download:

If you have any suggestions on how to improve the e-book, please send them in as this is our first version.

Download Button

Code Commandment 12: Launch Software. It generally helps if you throw a party!


“Caannnoonn Baaaaallll!!!!” – It’s time to make a splash!

  • Product launches are an exciting time! If you plan correctly, you can create enough noise to make sales right away. The trick is choosing the correct way to launch, the budget to spend and deciding how to get the attention you want.

What’s your viral coefficient?

  • A Viral Coefficient is the measure of how viral your software is, which is measured by how many new customers or users your current ones are bringing in.
  • So, how do you increase your viral coefficient? It’s like word of mouth marketing. Build up your reputation for quality and service by responding to your customers’ feedback.

It’s time to party… and work.

  • Make sure you celebrate all the hard work you and your team has put in, you deserve it.
  • Remember, your launch will likely give you, even more, feedback about your product so ensure you are ready to do more work.

After launch, your baby is now alive. Remember you will need to continue to feed the newborn with new features or hardware to support the growth. 

Code Commandment 11: Incorporate Feedback: Make final adjustments to UX.


Which Beta feedback do you need to incorporate now?

  • It depends on which features are necessary for user adoption. If the features you want to add will increase virality, marketability, and revenue, and if they avoid over complicating your app, it’s probably a good idea to add these in.
  • It’s also a good idea to get a time estimate from a developer for the rest of the features so that you can prioritize the smaller ones that add the most value to your software.

Plan out multiple versions to keep users actively interested in new features.

  • Instead of adding everything before you launch, introducing new features through different versions of your software will keep the users excited and demonstrate you are listening to them.
  • This will also make it easy to prioritize your features as the number of requests for them comes in.

Ensure the UX issues are addressed. Keep your software simple to get it going.

  • At this point, be careful not to over-complicate your user experience. Some user features can sound super cool but take you away from the main vision. Launching something that is hard to explain will only make user adoption harder.

After the UX feedback is incorporated in your software, it’s now ready to launch! It might seem easy but making a splash is one of the greatest challenges for new softwares. Stay tuned for the last Code Commandment – #12 – Launch Software.

Code Commandment 10: Beta testing: Thorough testing from actual users not involved so far.

10 v1

What is Beta testing?

  • This is testing done by people external to the project to ensure it works in real use cases.
  • The purpose of this testing is to confirm your software performs as expected for users that were not involved in the design and development. Often this test will return some feedback about functional bugs but mostly it will return feedback about the User eXperience (UX) and if they were able to understand your vision.

Close or Open Beta? Which one should you perform?

  • Closed Beta means you control the users who are involved.
  • Open Beta means you let anyone sign up to be part of your beta testing.
  • This largely depends on your end goals and target market for the software. Most enterprises want to keep their ideas private until they are ready to market them.

Beta testing can engage your users and improve your software

  • Document the user feedback and use it to prioritize how you will refine your software and create the best experience for your users.
  • Giving users feedback will also build a good reputation and boost the success of your software.

After you’re done Beta testing, you’ll want to incorporate the feedback into the software before launching it. Multiple rounds of Beta testing are generally needed to confirm the features you are adjusting/adding are to the users expectations. You aren’t done Beta testing until the users are happy using your software.

Code Commandment 9: UX testing: Plan to optimize the UX and incorporate feedback.

9 (v1)

What is UX testing? 

  • UX is short for “User Experience“, and UX testing is when your team tests the experience of using your software.
  • Is it intuitive? Easy to use? Are there bugs? UX testing addresses these questions so that you and your team can identify inadequacies and start fixing them.

Will my software have bugs if we planned it all out?

  • Yes, there will be bugs and your software can always be improved upon. In this way, you can fix the problems in order to perfect your software. 

Is my software easy to understand? Can a 5-year-old use it? Or more like… can my grandma use it?

  • It is important to put yourself into the shoes of new users and make the UI.
  • You need the learning curve to be smooth so that even a technologically challenged person can just pick up the final product and use it right away.

Make sure you focus UX on your target market

  • Keep the target market in mind and tailor your software UX to the needs of your customers.

Finally, plan time for bug fixes… even just tweaking the UX to be exactly how you want it can take time.

On the next commandment, we will give some handy tips for Beta testing your new software.


Code Commandment 8: Alpha Testing: Involve yourself in weekly testing.

8 v1 (1)

What is alpha testing?

    • It is when developers test the project to find bugs and make sure the project works.
    • This process lets you and your team discover as many fundamental problems as possible and make sure the software functions before beta testing.

Why is it important for you to get involved?

    • Things don’t always go as planned and bugs will creep up during the testing. You need to identify and fix these problems with your team.
    • When patching up these problems, your inputs are important in order for your project to stay true to your vision by the end of the process.

What can happen if the tests go wrong?

    • In an alpha test, something will go wrong! It is your team’s responsibility to fix and adjust the product.
    • You can help further improve the final result by being involved and providing the team with directions to save them time.

Coming soon! Code Commandment #9 details UX testing and bug fixes.