PSSICA = Placement, Shape, Size, Interaction, Color, Animation
The p is silent. Let's start there.  

Influencing your user to take a certain action, or influence their feeling, or emotion about an object portrayed to them can be very.. well deep. I have been a designer and developer for several projects through my years in the tech industry and I have come up with a common pattern I bring to every project when working with the project manager on the design.

Design can take on several styles to portray a brand as a whole, but this article is not about edges, angles, or font-type. It's about the basics of influence in the human mind, one layer deeper. The term PSICA is something I started to use, which refers to Placement, Shape, Interaction, Color, and Animation. Which reflect the 4 basic things that

Almost everyone does it wrong, they pass the value to a state, this is very similar to how Angular and $scope worked in two-way-binded. Every letter typed does an update. why not just get the values on submit?

With web, it's very common to do this, they pass the form submit and get the value based on the element's reference. for React Native however, we setup two-way binding with the component state. But WAIT, there is another way!

Using TextInput vs Input from React-native-elements, getting the value of inputs, I advise not updating state on every keypress, it feels way overkill, we should be able to just grab these values on the form submit using the _lastNativeText (https://github.com/facebook/react-native/issues/511)

Everyone uses the state for this, on Web, they use the DOM, simple

(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