(git rebase -i HEAD~3). The number is the end number of commits you want to review and the -i means you want it to be an interactive session. :) Now let's get moving.

Now that we are in a "rebase session", we will be using "vim" commands, if you're not familiar with vim commands, you can check out a cheat sheet of them here. Your terminal screen should look something like this:

Once you're in the open session, we will want to hit i for insert with vim, then we will direct to the correct place with our arrow keys, change the first word in the line next to your commit. To rename commit, we will change it to reword, then after that hit esc then we will type :wq and hit enter since it's vim, this will

I don't know if this is a mistakes guide, or a confession post about things I wish I could do different. I guess a little of both, at the end, I hope it gives you a better understanding of my experience, and give you something to take way that you can apply to your own entrepreneur project.

Don't Rush it

Everything was right at launch, right audience, right team, right marketing, right design, but the product was ready.

Don't Overdue It

too many features, too many things to go wrong, went after perfection for the customer before I knew the customer, I had an edge being deep into that field before, but lost touch with what was common and what was my methodology.

Don't Lose Yourself

This one my be counter intuitive, as an entrepreneur, and someone with a passion

Git can be your best friend or your worst enemy at times. Navigating through the treacherous waters can be sometimes nerve racking for even long time users at times.

Not all git processes are the same. With using git more than 10 years now, I have seen several different processes within companies.  Our of these, main practices I have noted are these:

• Git Branch Methodology
• Git Commit Methodology

I will break down each of these with pros and cons and show you the series of git commands that works best for each. To make it easier to understand, I will use a book analogy, with chapters being the branches and commits being the pages.

Git Branch Methodology

Using branches I have found to be the most common practice. It usually conisists of these commands.

• To start: git clone {repo}
• You're

We will be going through how to setup Postgres locally on mac. We will cover the following:

• Starting Postgres
• Using psql to interact with database in command-line
• Creating your first database.
• Manage Data (Create Table, Inserting Data, Viewing Data)
• Stopping Postgres

Let's start off with making sure we have Postgres installed locally. Open up terminal on mac and run postgres --version. You should see the version information outputted.

If you don't see the postgres version or need to install it still. Check out the Install Postgres on Mac post. Now that we have that out of the way, let's continue.

Step 1

In terminal, run the following command. It will start Postgres locally.
brew services start postgresql

Step 2

Next, let's go into the Postgres server now that it's up and running. Run the following:

PostGres has grown a lot recently in popularity, as a free alternative to enterprise relational databases such as Oracle SQL, and also as a database to get a new application cranking very quickly that comes filled with features and easy to setup.

Now let's get one of the best databases ever up and running on your Mac. As a developer, I think you owe it to yourself to have Postgres installed :)

1. Open Terminal

2.   Now copy and paste brew install postgresql then hit enter.

3.    Last, in Terminal, copy and paste postgres --version and hit enter.

You should see the PostGres version output in your console. This is good news. You're ready to go. You can create your database and start storing data. Checkout PostGres Documentation to learn more about all you can do with the PostGres database.