(public).sospep.subjects ~ view article ~ about-this-book

<h1 style="text-align: center;">about this book</h1>
<h2>[WHAT]</h2>
<ol>
<li><span>] learning git - for noobs, by a&nbsp;eh noobie/newbie - a {23} step/page guide for newbies to creating, publishing and managing your first open source project using git SCM software , </span></li>
<li><span>] guide </span><span>to managing your first open source project using git, for newbies </span></li>
<li><span>] </span><span>by E.H Noob </span></li>
</ol>
<h2>[WHY aka MY GOALS]</h2>
<ol>
<li><span>] &gt; to create, publish, update and manage <span style="text-decoration: underline;">my first open source project</span> using git </span></li>
<li><span>] BONUS 1&nbsp;- Would be to do this in a reasonable amount of time </span></li>
<li><span>] BONUS 2 - With as little pain and suffering as possible.&nbsp;</span>&nbsp;</li>
</ol>
<h2><strong>Some BACKGROUND </strong></h2>
<p><span>&gt; i am an independant software/web/mobile developer (for hire) and&nbsp;founder of sospep.com (this site), so <span style="text-decoration: underline;">i've built some stuff</span> along the way but when it comes to using the&nbsp;git scm sw i am pretty much a noob feeling my way in the dark </span></p>
<p><span>&gt; of course, speaking as someone who has developed software, you "have to/should/will" benefit from using some kind of source code management(SCM) system.&nbsp;I have typically used my&nbsp;own,&nbsp;very&nbsp;simple, scm system, it is not fancy, it's not sophisticated, but it works for the size and breadth of the projects that I have taken on to date. </span></p>
<h2><strong>&gt; so why git, why now?</strong></h2>
<p><span>- as much as i would like the world to adopt my simple SCM system, so that i wouldn't have to learn anything new.&nbsp;I've come to the conclusion thats not a realistic expectation.&nbsp;All&nbsp;kidding aside,&nbsp;if i want to use an SCM system that is widely adopted and in use by many developers, git is great choice, I would suggest that it has become a "de facto standard" in the world of open source software(OSS) development.</span></p>
<p>- and as I stated in&nbsp;my goal, i have an open source project that I am itching to git out there, so git it is !!</p>
<h2><strong>The PROBLEM</strong></h2>
<p><span>- i came across this&nbsp;comment - &nbsp;which more or less summed up my feelings about git - at that point and time </span></p>
<p><strong>[on git] by&nbsp;Joel Beazelman on hanselman.com/article{id}/comment{id}</strong></p>
<p>Git is like using a chainsaw with thousands of switches and buttons and all of them labeled in Greek. In the hands of someone who spent months learning it, it can be efficient productive and fast, but to the rest of us mortals, learning to use it can take off a few fingers and possibly your HEAD. Yes, you can always get your fingers and head back, but figuring out how is so difficult, you might as well opt for a transplant (which is also supported by git).</p>
<p>At its core, Git is a big leaky abstraction. It's like driving a model T, where the developer needs to know how it works in order to drive it. I'm tired of all the developers who claim using Git is easy. If it was so easy, why are there so many clueless developers asking questions on Stackoverflow on how to use it. Every GUI for git fails spectacularly because the buttons and switches bubble up to the surface like methane seeping from sludge at the bottom of the lake. You can't get around the Git stench--it sucks!</p>
<p>- video - If you look at the picture at the left, it also sums up my feelings ...</p>
<p>lots and lots of buttons, BUT where do i start?</p>
<p>The goal of this guide - is to be the start button<span><br /></span></p>
<h2>[WHERE aka THE PLAN aka THE SOLUTION]</h2>
<ol>
<li>&gt; these are essentially "my notes" as i travelled up the path/road&nbsp;FROM: <strong>git kilometer# 0</strong>&nbsp;TO: <strong>git kilometer# {23}</strong></li>
<li>] the notes&nbsp;are&nbsp;NOT intended to be an end to end comprehensive toom(?...) on everything git&nbsp;that&nbsp;delves into the inner workings of the git sw and&nbsp;leads to you&nbsp;becoming a SME on git/scm and ultimately world domination</li>
<li>] they ARE&nbsp;intended to git me (and maybe you) from Point A to Point B,&nbsp;with simple, clear step by step instructions that (hopefully, almost) anyone can understand and (also hopefully) as few of them as possible&nbsp;</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2014-mm-dd</li>
<li>] 2015-06-dd</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>]</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>] <strong>before we "git Started", some IMPORTANT DISCLAIMERS</strong></li>
<ol>
<li>&gt; IANAE - I Am NOT An Expert -</li>
<li>&gt; TANGIL - There Are No Guarantees In Life&nbsp; -</li>
<li>&gt; YMMV - Your Mileage May Vary -</li>
</ol>
<li><strong>OK, your still here, let git started !!!</strong></li>
<ol>
<li>&gt;&nbsp;<a href="/view/task?id=3663" target="_blank">kilometer 0</a> - download, install and configure git</li>
</ol></ol>
<h2>[REFERENCE]</h2>
<ol>
<li><strong>] BOOK - <a href="/view/chapters?id=263" target="_blank">git started</a></strong></li>
<ol>
<li>] #&nbsp;2459 - <a href="/view/article?id=2459" target="_blank">table of contents</a> - a guide to learning git for noobs</li>
</ol>
<li>&gt; there are at least 1.6 million other Guides/refs/how-to/abouts/books/videos to git, probably even more, with more coming online every day.</li>
<li>- I have found a few of the simplest, best by looking through &lt;many of them&gt; <span>and have included links to them.</span></li>
<li><span>- this <em>saves you</em> from&nbsp;spending&nbsp;your time to do that </span></li>
<li><span>- Of course, if you have the&nbsp;time to spend, and you want to learn more about git, IMO these are some of the best places to git started</span></li>
</ol>
<p><span><br /></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] ch-001-introduction FROM [ Book] book-git IN [ libraries] prj-035-git-started