Sticky Post

Eyes

I realized that I have been delaying many things in life and have shorted many people I care about. This changes today!

Day One

I am sick and tired of being sick and tired. I do not want to be fat and uneducated any more. No more excuses and delays. For the next one hundred days I will exercise, keep my diet, and get a certification every three weeks.

I will log my accomplishments and failures.

Time to start… TODAY!

Git

Just used four hours today in learning Git. Amazing stuff! I made a spelling error in one of my commits and looked up how to correct the spelling error:

Source

If the problem commit is more than one commit ago, you have to fall back to interactive rebase. For example, if you notice a misspelling three commits ago, you would type something like this:

git rebase -i HEAD~4

Then rebase would open up your default editor with a view that looked something like this:

pick c5052cb Updated the workshop instructions
pick 6d6cd60 Upgraded to the plugin 0.6.1
pick c6d0921 Upgraded wrapper to Gradle 1.2
pick 7a111da Upgraded to 0.7 of the Liquibase Gradle Plugin.

# Rebase 097e6b2..7a111da onto 097e6b2
#
# Commands:
# p, pick = use commit
# r, reword = use commit, but edit the commit message
# e, edit = use commit, but stop for amending
# s, squash = use commit, but meld into previous commit
# f, fixup = like "squash", but discard this commit's log message
# x, exec = run command (the rest of the line) using shell
#

You'd want to edit the third line (the one referring to commit c6d0921) to start with the word "reword" instead of "pick." Once you save and exit from the editor, you'll find yourself right back in the editor with that commit's message in front of you. Correct your misspelling, save and exit, and all is well.

Note that doing this or doing a commit --ammend is dangerous business if you've already pushed these commits to an upstream repo. This is why there's no way to do this on GitHub.com directly. If you want to change commits you've already pushed, that's a separate matter entirely. :)

Also to see what changes have been made before doing a commit:

Source

git diff --staged
Depending on your exact situation, there are three useful ways to use git diff:
Show differences between index and working tree; that is, changes you haven't staged to commit:
git diff [filename]
Show differences between current commit and index; that is, what you're about to commit (--staged does exactly the same thing, use what you like):
git diff --cached [filename]
Show differences between current commit and working tree:
git diff HEAD [filename]
git diff works recursively on directories, and if no paths are given, it shows all changes.

Cannot wait to know how to use this tool much better, where I know how to do what I need to do. 😉

Learn

The only way I can leave where I do not want to be is to get better. As I stated before, I am learning Security+, HTML/CSS/JavaScript, Python and Git. But I need to put what I am learning into practice to solidify what I have learned. Else garbage in, garbage out. I will just forget.

In learning Git, I tried one of the commands the instructor provided, tree. Did not seem to work on my version of Git. I Google’d and seems that I have to create an alias for the “tree” command to work: Source git config –global alias.tree “log –oneline –decorate –all –graph”

Seems to work! But I do not have enough changes to actually show a real Git tree. For right now, I just see the Git adds that I have committed.

I am enjoying this! Nothing like learning. 📚📖🚀

I can see my tiny progress 😁. I am doing things so small, that failure is not possible. As much as I want to leap, I know I have limitations. When pushing to hard, there is possibility of failure. Just as someone building their muscles and going to the “gym”, just takes time. The important pieces, focus, discipline and consistency.

I have already used what I have learned in creating this page! 👏🎉🥳