JoshSweeney

Marketing An Inexpensive SugarCRM Module

SugarCRM is a great platform to extend with custom modules. You can extend it into various areas of work and add functionality that the creators never thought of when SugarCRM was coming into existence. These modules are great for personal and company use but things get a little more complex when you decide to sell one.

This week ALT-Invest completed and released it’s first purchasable module for SugarCRM called GetSocial Twitter Pro. The fact that we weren’t some large corporation trying to drive users to our service and simply offered an inexpensive SugarCRM interface to Twitter meant that we were embarking on a journey that not many have taken.

What do I mean by this? SugarCRM offers the SugarForge for developers that want to post their work for all to use at no cost. We have posted multiple modules here but decided that to provide a robust module that was feature rich, we would need a little bit of compensation. This drove us to look at SugarExchange.

Somewhere between mid development and completion we looked at adding the module to the SugarExchange and found that there is a $2000 annual listing fee. This was just not feasible for a module that cost $25 and connected a free service ( Twitter ) to a community that mostly utilizes the free version of SugarCRM. Later we were told that SugarExchange was for corporate modules which, again, means companies that want to drive users to their software or service by offering a module. This seems like an odd positioning given SugarCRM market but that is for another day.

Now that we knew that the two biggest channels for attracting SugarCRM users weren’t going to work for us we had to get more grass roots than originally planned.

Here is what we have done so far:

Seeing that this is a Twitter module and we are Twitter users we started to leverage….. you guessed it, Twitter. There are many helpful SugarCRM users on Twitter so we started by posting screenshots to the new module which thanks to a few got retweeted. We will continue the Twitter effort over a period of time while trying to keep it from getting to spammy. Since we already posted the screenshots we are likely to follow up with posting the docs and then some more info. I think that three Tweets is enough when it comes to marketing one product on Twitter.

Next we hit up the bloggers. We searched out bloggers that used Twitter and SugarCRM that would be willing to review the module. Our offer to them was a free copy with no stipulations. One thing that we also made sure NOT to do was ask for a good review or anything like that. We simply asked for a review of a 1.0 module. Hopefully they enjoy it enough to give us a fair review that is accurate and provides value to potential customers. If they dislike it then at least we still get honest feedback that we can feed off of for the next release.

The third thing that we have done is created a press release to email out to any CRM sites that we identify to be valuable. We just finished the writing the release and will keep you posted on this process.

Since ALT-Invest is one of the organizers of the Atlanta SugarCRM meetup we will be giving a presentation dubbed: Building SugarCRM Modules for Fun and Profit. This will revue everything that we learned in the process of building a module with the intent to sell. In the presentation we  will mention the GetSocial Twitter Pro module as the case in point but will not go more in depth. Doing this will let people know it exists while still staying true to the focus of the group.

Lastly, we have to count personal and company blog posts such as this.

So far, this is were we stand on marketing our inexpensive SugarCRM module. As we further our efforts and make progress we will let you know so that you can know what to do or what not to do with your next module. If you have any suggestions then please leave comments or catch me on Twitter @JoshSweeney.

_{»crosslinked«}

March Atlanta PHP Meetup Recap

Speaker of the Month

This months meeting centered around Jonathan Freeman’s Model Baker Product. Model Baker is a Mac OSX product that enables a user to rapidly build fields and relationships that will be used on a new web application. Once they build the fields and relationships they can deploy the application which will automatically create the MVC portions of the application. Here is a blurb from the Model Baker website which provides a little more information.

“ModelBaker – a remarkable application that delivers point and click development so you can do amazing things for your business, your customers, organization and school. Rapidly build a corporate intranet from scratch. Create custom client web applications based on templates you’ve created. Place your classroom online and offer your students mobile access from an iPhone, iPod touch or Google Android. “

As you can see it also has the ability to deploy views that work on the iPhone, iPod, or Android. These views are options that are set with the click of a checkbox.

The ModelBaker client is a Mac only client the is written in Objective C. The deployment and creation of the application is accomplished using the CakePHP and EXT JS frameworks. The current version does full server side validation but only stubs out code for client side validation. Jonathan mentioned that full client side validation is on the way.

Another upcoming feature that was discussed was the ability to take and existing database and create the MVC application around it. I have seen a few applications that do this but most were prototypes that were not ready for production use.

To complete the meeting, Jonathan generously supplied all attendees with a free license to the ModelBaker package. If you would like to get a demo or read more about ModelBaker you can head over to WidgetPress.

More Meetup Information

At this months Meetup we did something a little different with part of the time. Even though we were near record attendance we went around the room and had everyone introduce themselves, tell us what they did, and what future topics they would like to have presented. Although it takes a while to get around the room it was enjoyable to find out what each persons job and interests were. This way if you needed some assistance or wanted to organize a group around a specific topic then you could quickly identify who to speak with.

With each Meetup we also go over local events, new, and upcoming conferences.

News:

Zend Server CE Released

The PHP consulting company launched – thephp.cc

PHP 5.2.9 Released

Zend Server Beta released

The PHP QA book is in the works – qualityassuranceinphpprojects.com

Ibuilding launched TechPortal – techportal.ibuildings.com

Conferences happening now that you can follow

PHP Quebec

Twitter Hash: #phpquebec

Web: http://cond.phpquebec.com

DrupalCon DC dc2009

Twitter Hash: #drupalcon

Web: http://drupalcon.org

Upcoming Conferences

PHPtek – tek.mtacon.com -Chicago

International php conferences – Berlin

DC PHP – dcphp.com – Washington DC

Dutch PHP – phpconference.nl

OSCON en.oreilly.com/oscon2009

EXT JS – Orlando

Upcoming PHP related events are also tracked on the PHP Community Calendar http://calendar.phpcommunity.org

Local Happenings

A new Atlanta Javascript Meetup has been organized.

Asterisk Install Day

Atlanta PHP Specific

Atlanta PHP recently became an LLC and as is looking to rebrand. The goal is to raise $300 and host a contest on 99designs to get a new logo.

The group is also looking to host a PHP Day which will be a day long seminar all about PHP. If you are interested then please let the organizers know so that there is a better change of making that happen.

Atlanta PHP is planning on putting together an event to support the PHP QA test fest. For more information on test fest visit TestFest 09

The new Atlanta PHP wiki is up and awaiting your entries.

You can follow Atlanta PHP happenings and updates on Twitter: @AtlantaPHP

SugarCRM: Project Management vs Advanced Project Management

If  you are interested in the project management functionality of SugarCRM, the first question that you may have when comparing versions is “what is the difference between project management and advanced project management?”

If you are not familiar with the comparison chart, SugarCRM Community Edition shows project management but Professional and Enterprise offers Advanced Project Management. The comparison chart is usually where the “whats the difference” question originates from.

The Community Edition offers the ability to create Projects, Project Tasks, and relate information to the project records as seen in the partial below.

Creating projects and the tasks assigned to them is a helpful feature but this could be easily built with Module Builder. It is only when modules go beyond the functionality of what could be done with Module Builder do they become the most useful. The same applies for the project management module hence advanced project management.

Advanced Project Management offers multiple pieces of additional functionality which includes resource management, project templates, Gantt charts, a project dashboard, project holidays, and the ability to export to MS Project.

Project Management Comparison Chart:

Resource management gives project owners the ability to assign users and contacts to projects. These users and contacts will then be used in the Gantt charts for the visualization of a project.

Resources Sub-Panel

Project Templates are most useful for companies that do similar projects on a reoccurring basis. With templates, a user can add all of the common tasks that are required for reoccurring project types in order to speed up the build out of the next project.

Of all of the extra features in Advanced Project Management, Gantt charts are considered one of the most useful to many users. Especially for those who are MS Project users.

As you may be able tell from the example chart above, the Gantt functionality closely follows that of the most common functions used in MS Project. Chart creators can assign resources ( users and contacts ), set predecessors, and analyze estimated duration vs actual duration which is very handy for analyzing estimation accuracy and progress. With the ability to create charts it is only natural that SugarCRM give you the ability to export to MS Project.

The last added feature in Advanced Project Management is Project Holidays. Project Holidays blocks out dates on a per user basis so that the project time lines are accurate and adjust for any possible deviations.

Holidays Subpanel

Holiday Scheduling Form

Learn More:

Project Management section of the documentation

Sugar best practices for Project Management recorded seminar

If you have more questions about Project Management then please feel free to contact me or post a comment.

SugarCRM: Import Wizard Tips

In this SugarCRM post I will discuss some tips on importing data into SugarCRM using the import wizard.

To start off with I would like to review what the import wizard is intended for. Even though the import wizard can import mass amounts of data, it’s intended use is to allow users to easily import data from various outlets such as trade shows, event attendance lists, and other exports that get appended to the current record set.

Tip 1: Database Migrations

As of SugarCRM 5.1 the import wizard is robust enough to import tens of thousands and even hundreds of thousands of records from a database dump. For an accounts migration starting point the import wizard will do the job. The problem comes when you want to maintain relationships during the migration.

When you are migrating data, each system relates records using different keys or formats in the database. SugarCRM is Accounts driven and relates using unique ids. This means that Accounts will go in smoothly but to import a related record, like a related Contact, you will have to get the contacts related account name and the SugarCRM Account id, merge the id in to the contact information and then import. This process is best left to tools like Talend and not the import wizard.

Tip 2: CSV Files

Most people use the comma separated values ( CSV ) format to import data. CSV does the job well but there are things that you need to check for before you import. The first is commas. Since you are importing using CSV, any time that the import wizard ( or Excel ) sees a comma is will think that it is working with the next column of data. This will completely throw off your imports. To fix this you will need to cleanse the data of commas before you import. You can usually substitute with a space or a dash depending on the data. The other alternative is to use another format for importing such as tab delimited since most dumps don’t have tabs in the data, but it is still something to watch out for.

The same thing that goes for commas goes for the the field qualifier. If each entry is wrapped in single quotes and the data fields have single quotes ( Ex: Janes’s Store ) then your data could get imported incorrectly.

Tip 3: Field Qualification and Saving Templates

Fields in CSV files are usually wrapped in quotes, double quotes, or are not wrapped leaving just the comma separators. When you are building the import mapping you are asked to choose which field qualification to use. My tip is to add which type you use in the naming of the template. The reason is that in SugarCRM’s current implementation if you import data using a template with the quotes field qualification and the data actually uses double quotes then the mapping will be blank. This isn’t a problem with a one time import or when the same person does the import the same way each time, but this is not always the case. You may receive weekly exports of the same type of data but from different people with different version of MS Excel/Open Office Calc causing different field qualifiers.

Tip 4: Drop Downs

All drop down boxes added in  Studio need to have a NULL entry as the first option. This is where you click the add button in the drop down editor with no data in the fields. The reason is that when you import data you have to specify a default value for fields that are not filled in. If you don’t have a NULL entry as an option then the import wizard will automatically assign the first value in the list even though the data for that column may not exist.

Tip 5: Matching Data for fields

If you are importing data that requires custom fields or custom values, then each of the custom fields/values needs to exactly match the data being imported. Let look at an example:

DropDown Example

Your data has field/column called Manager Level and the fields are filled in with three options which are Manager, Middle Manager, and Senior Manager.

In SugarCRM you have drop down box that has Manager and Senior Manager.

When you import the data you will get an error for every record that has Middle Manager as a value since it is not in the SugarCRM drop down. For data accuracy reasons SugarCRM is not going to automatically add that as a drop down item.

Hopefully these tips will help you the next time you import data into SugarCRM. If you run into any others that need to be added to the list then feel free to comment or send me an email.

Tags: crm, import wizard, SugarCRM, sugarcrm import

BarCamp Atlanta 2 – Morning of Day Two

Day Two started off a little slow mainly because people that didn’t camp had to drive in to join the crowd. Those who did camp, including myself, stayed up until 4am discussing various topics of interests. Thankfully we have good sponsors in Atlanta who have provided food for the entire event. Breakfast from Flying Biscuit assisted in getting everyone moving and prepared for another day of talks and demonstrations.

The first presentation that I attended on day two was RSS tips, tricks and discussion with Will Powell. One trend that many people at the table were seeing was that they spent less time reading blog posts and more time watching Twitter since it is a real time update and less time consuming from a dedicated reading perspective. Some other take aways were that nobody in the room pays for a RSS readers and from a user level nobody really cares if you are using Atom or RSS for feeds.

After the RSS discussion I sat in on Rachel K’s presentation of Squidoo. From her presentation I would describe Squidoo as a web page building platform that has built in widgets for functionality and also provides monetization. Squidoo uses a shared revenue system and distributes the cash based on the popularity of your lens ( page ).

Sanjay Parekh gave the next presentation on How I built StartupGossip.com in a weekend ( using Yahoo Pipes ). For those of you that aren’t familiar with Sanjays site, it compiles startup blog posts, news, and tweets that are focused on the Atlanta startup scene. Unbeknown to me there is the capability to get Tweets that are geolocation based. Users of the Twitter API can also set a range and get tweets from people within the vicinity. This is what Sanjay used for the Twitter section of StartupGossip.com. The other sections use a compilation of data that is gathered and filtered using Yahoo Pipes. Then the new Pipes streams is fed into StartupGossip.

After Sanjays presentation I visited Greg Tuve which was presenting on memory fractals. Since I had never heard of memory fractals I thought that I should find out just what he was talking about. what the presentation ultimately boiled down to was a highly efficient study technique. By giving the brain three different words or images it would instantly trigger a forth word or piece of information. One example was as follows. Here are three words: lime, salt, Mexico. Now say the forth word that is linked to all three. For most the answer is tequila. Greg uses a program called Memory Weaver which allows people to quickly create study grids. During the presentation Greg also provided explainations down to the neuron level. To get more in depth information you can visit Gregs website: Memory Genesis.

For Lance Weatherby’s second act of the weekend he presented Everything Twitter. Below I have listed some information that Lance gathered and presented.

Reasons to use Twitter:

• Stay in the loop.
• Learning
• Connections
• You are bored in board meetings.

Top Twitter Tools:

• TweetDeck
• Thwirl
• Twitteriffic
• Twitterfom
• Twittercelerator

Useful Twitter Sites:

• Summize
• Favrd

What makes you unfollow people?

• Bad Signal to noise ratio

Tips for Newbs:

• Follow people in your industry
• Do not automatically reciprocate people who follow you
• Find a good client

Another interesting thought was to follow your competitor. I have seen people who follow the Twitter accounts of their competitors but the extra step which was mentioned here was to actually follow individual people in the competitors company. It would be interesting to do a study of this and determine what kind of insights that one could gain.

Next, Brad Gilbreath presented on Location Based Services. Being a Dash user Brad has created addons that allow a new level of interaction with your GPS. One of his examples was a site that integrated with your GPS to list all of the haunted houses in the area that was updated real time. So if you wanted to go out for Holloween and hit every haunted house you could quickly and easily pull this into your GPS. The discussion also went over some potential abuses for a GPS that gets real time data from web services. For example: if you wanted the closest gourmet coffee shop, a service could provide a coffee shop that they were being paid to direct people to.

The last speech of the morning was from our sponsor representative. Glen Gordon is a locally based Microsoft evangelist that always knows the latest happenings coming out of Redmond. He went over the various pieces of recent Microsoft news which is listed below.

• The release of ASP.NET MVC
• Silverlight 2
• Microsofts adoption of JQuery
• IE8
• XNA Framework for Zune and Xbox 360

After asking about the innovations in IE8 it quickly turned into an IE8 Q and A session. One of the cool new features in IE8 is web slicing. You can pick out a portion of a website, create a slice, and every time that particular portion of the website is updated you get an indicator in the browser. From the description it is almost and instant RSS feed for a specific section of a website. Glen also told us that IE8 is packaged in a VM for anyone that wants to try it out. To top of the final meeting of the morning Glen offered free one year subscriptions to anyone interested in joining the XNA Dev Network.

After Glens speech we went off to have pizza and drinks provided by the sponsors. This would be out last meal at BarCamp until next year.

Tags: atlanta, barcamp, ie8, microsoft

Bugs vs. Features, A Holy War

For anyone who has worked in a software company the bugs vs. features debate is one for the record books. There are always two sides, one that wants more bugs fixed than features added and one that wants the opposite. Both of which are compassionate about the reasons that their views are correct and the others are not. In the end, each side gets a little of what they want and each side feels like they are getting the short end of the stick.

To fully understand this argument lets take a look at both sides of the argument and the factors that come into play. Below I have listed a few arguments from each side. This is in no way a comprehensive list so if you have more suggestions then please comment.

The Bug Squashers:

1. Bugs are costing us deals.

2. The product is unstable which makes us look bad.

3. Bugs expose an underlying engineering issue.

4. More features means more bugs.

The Feature Zealots:

1. Features are costing us deals.

2. We have to weigh time to market.

3. Customer X wants it.

4. We promised it to get the deal.

As you can see, like any holy war each side has valid arguments as to why they are right or, in this case, why they should utilize more engineering time than the other. Fortunately with this war there are solutions to the problem.

Even though we see what the issue is I still don’t beleive that we have gotten to the core. The core reason that people arugue for one or the other because they don’t have the data. Each side sees things one way and thinks that the product manager just doesn’t understand.

If each side was given quantifiable data to backup the decisions made by product management then at least all parties would understand why the decision was made. Everyone who was feeling wronged would now know that the product manager analyzed quantifiable data and came up with a features to bugs ratio that determined the allotted hours spent for each in a span of time.

If you are a product manager you may be saying “why do I have to justify my decision to you.” The answer is that you don’t. However, for coworkers to really believe in your decisions they need to be able to see justification for the for the outline laid before them. The fact that there is quantifiable data backing up the decision makes it where coworkers no longer feel that bug to feature ratios are simply pulled out of the air or are related to to the most angry customer of the day.

Now that we have looked at one of if not the true cause of the issue we need to determine how to quantify the data. For every software company this approach will be different. I will give an outline on a possible solution using one of the common arguments above.

1. Bug or Feature costs us the deal – This is perhaps the most quantifiable argument. By having salespeople utilizing a CRM system or other tracking system, management can impose required fields. I dub these the “Why did we lose the deal fields.” Each of these will be mandatory if a deal is moved to a loss status. Some examples are as follows:

a. Lossed Because: Bug, Feature, Price, etc..

b. If a bug or feature is chosen then which bug or feature. This would need to be a drop down will all product sections or top X number of features requested.

With information about why each deal was lossed and what the sales person sees as the reason, we can now start to quantify the information. We can now run reports on losses and generate a bug to feature ratio. This is quite simplistic but gets us started. In addition to the hard numbers we can factor in the amount lossed on the opportunity/deal. This step will take a more effort mainly because if hinges on the fact that the opportunity numbers are not inflated.

This in no way is a comprehensive solution but gets us on the road to quantifying why we make the decisions that we make.

There is a good number of books that discuss the benefits of quantificaiton and give compelling reasons on why it makes people more satisfied with decisions and companies more profitable. I have personally read Competing on Analytics which also references Moneyball. Information form both of these books is highly recommended when adding in the trials of running or working in a company.

I will end this post with a quote from Lord Kelvin that I beleive should be on the office wall of all decision makers.

“If you can measure that of which you speak, and can express it by a number, you know something of your subject; but if you cannot measure it, your knowledge is meager and unsatisfactory.” Lord Kelvin (William Thomson, 1824-1907)

Tags: bugs, features, product management

The “What is code coverage” cop-out

At one point in time I was a quality assurance engineer and had the pleasure of attending many conferences about testing methodology and how to test throughout the SDLC. In having this education I have always attempted to pass testing information along that I felt would benefit another company or person.

After talking with many developers I have found one thing that is an absolute cop-out.

It starts like this:

Developer: They say we have to many bugs

Me: What is you code coverage?

Developer: Well that depends on what you consider code coverage.

This final statement generally translates to “We have nothing in place to measure code coverage.” In even worse conditions you can append “We write code not tests. Testing is for QA” on to the end.

I know that all of the developers out there now want to kill me. Some say that the “what is code coverage” argument is valid. To that I would say that you are 100% correct. It is a valid question if you have not decided to start testing on the developers side of the house. The fact that you are still avoiding answering the question with a percentage of code coverage instead of this counter question just backs up my point.

To other non-developers including QA and management the issue doesn’t come down to what code coverage is. What they want to see is that the people writing the code are taking every step necessary to test the code that they write and make sure it is the best quality possible before being pushed to QA and then to the world. No matter what you or the analysis tool considers code coverage the rest of the team wants to see metrics. They want coverage represented in a percentage that is moving in the correct direction with every cycle, closer to 100%.

Oddly enough I have found a direct relation to the answer to “what is your code coverage” and the quality of products. Not in every case, but in most cases if you ask the lead developer about their code coverage and they answer with a percentage or metric then you can at a minimum be assured that testing is on their radar. If the number or metric is high then it is likely that the level of quality is higher than to other competing software.

Code coverage is not an exact science and each tool calculates in a different fashion. As long as you or your developers are using the same tool and testing methods then the coverage report should look better with every development cycle. Remember, testing is a process and not a department.

Tags: code coverage

Crawling Your Way to QA

Testing the quality of a Web application, like any application, can be a cumbersome process. Companies and testers alike are always looking for new ways to test more efficiently and obtain broader coverage with every development cycle. With the introduction of new features and ever-expanding site trees it is tough to keep up with changes in web applications using traditional testing techniques such as manual input validation.

In this article we will take a look at how one crawler could test major portions of a web application with little effort or time from the user. By utilizing crawl-based testing tools we can test the security, verify proper search engine optimization ( SEO ) techniques, and test performance of most web applications without having to write as many complex scripts or test cases. Using crawlers for QA doesn’t replace the need for traditional tools. It accompanies tools and human logic to provide more information in an automated fashion. The biggest benefits in using a crawl-based tool for web applications are its speed and ease of use. You can enter a URL and in only a few hours you will be presented with enough information to keep developers busy for hours, days or even weeks. While not the only tool you should use, crawl-based tools are likely among the most dynamic and should be the first tool that gets executed. Once a new feature or content section is placed in the testing environment the crawl-based tool can be launched against the site or the new section. While the testers are executing test plans the crawl-based tool will be running in the background to identify places where changes may need to be made. After the initial assessment a qualified tester can take an in-depth look at the results and decide what needs to be done with them. Now that you understand why a crawl-based tool can be helpful and how it could fit into and assist in your testing environment we will take a deeper look into how it works.

Using crawl-based programs for security testing is a common practice in the Web application security industry. In relation to SEO tools and performance testing tools, crawlers appear to be most prevalent in the security arena. Most enterprise web application security testing packages are based on a crawler that uses various types of logic or checks to test for vulnerabilities and best practices. Current black-box testing systems can detect cross-site scripting ( XSS ), SQL Injection ( SQLi ) and various other security issues. Utilizing a Web application security scanner is a proven technology that will immediately assist the quality assurance effort.

Just as there are techniques to make a Web Application more secure there are also techniques to assist in improving your ranks in search engines, this commonly referred to as SEO. Search Engine Optimization ( SEO ) is the process of improving the volume and quality of traffic to a web site from search engines via “natural” (“organic” or “algorithmic”) search results. –Wikipedia. This process has two parts. The first part is the optimization of the Web application. Second are external promotions which involve link submissions and social based web promotion to name a few. There are applications which do automated link submissions but they are not crawl-based and therefore outside our focus. Currently the most widely used functions of a crawler in SEO programs is to check for broken links and check web site structure against web standards. Most other tools that check for code-to-text ratios, meta-data, and keyword density are stand alone but can be rolled into a crawler. Since SEO is somewhat subjective, a crawler would have to test for best practices. It would also have to have knowledge of “black hat” SEO techniques so that it could alert you to a page that could get your site removed from top ranking search engines. As you can see, a crawler itself cannot complete all tasks related to SEO but can easily test many aspects of a Web application to make sure it is configured in an optimal manner for search engines and users.

Performance testing tools use predefined scripts to put a load on a Web server and calculate how it is affected. This process can also be done to some extent with a crawl-based testing program. As part of the performance testing section of the crawl the test application can execute load testing followed by stress testing all in one scan. This can all be accomplished by iterating the number of crawl threads and increasing other variables while providing input to fields that are available in the Web application. Then, by analyzing the response times and load times of each page, it can determine how multiple users could affect the Web server. To go one step further, the integration of pre-recorded scripts could introduce more “human like” load on the server.

Testing the various aspects of a Web application can take many tools and is a continuous process. As you have seen, crawlers can accomplish much larger tasks than they are currently used for as well as enhance the coverage of a Web application. By understanding the ROI that a crawl based tool can have you can better understand how it could assist your company, application, and testers. As long as we are using crawlers, we should take advantage of their full spectrum of effectiveness in security, search engine optimization, and performance testing.

Tags: crawlers, QA, quality assurance, testing

I broke down and created a blog

For roughly the past three years I have attempted to be heavily involved in community. The communities of entrepreneurs, security, CRM, business, networking, and anything else that interests me. While being part of these communities I have ideas and thoughts but only a few outlets for them. My main outlet was to take what I learned or thought and use it in another business if it was applicable. The problem with this is there is no single place to house all of this information. Sure, I could write a private journal, and I have, but where is the community in that. How does that help others think differently about problems or overcome issues that I have seen. It doesn’t! So I have broken down and decided to create a blog years behind the curve. By creating this blog I am pledging to myself to keep it up to date and to become a more compelling writer.