3 ms·

I've never understood GitHub...I just write code in notepad and then sftp it into my server to deploy...why go through github?

by RawData 14y ago

krapp 14y ago
I just started using Git and Github myself... and for me, github itself is useful as an online backup for a repository (git itself being incredibly useful in terms of organizing projects) and just having a github profile looks better on your resume, etc than not having one. At the very least, your code is right there to be looked at.
- RawData 14y ago
  I don't want my code to be looked at though...it's proprietary. It powers the software that I sell to make a living...why would I spread it around? Though I get your general gist...
  - dwb 14y ago
    A git repository doesn't have to be public, though you do have to pay for private repositories on GitHub. GitHub is great for the "network effects" of it having a lot of developers on there, maybe wanting to help out with your (public) software, but if you just want some free, private Git hosting, https://bitbucket.org https://bitbucket.org is fine.
  - krapp 14y ago
    You can always start a number of personal projects or dust off some old ones and put them up on github. That's basically what I did... take code I can't really sell and use it to sell myself. Such as it is.
  - propercoil 14y ago
    you pay 7 bucks or less and you can manage 5 private projects. best thing i did
- aioprisan 14y ago
  you don't have to make it public, it can be private. I use bitbucket, unlimited free hosting repos, and makes for much better code deployment to distributed servers etc.
fmoralesc 14y ago
[ ] You want to use git (which allows for pretty awesome workflows)[1] [ ] You want to keep some external backup you can rollback changes from. [ ] You want to allow other people to collaborate with you. [ ] You want your work to be more visible. Check as appropiate. [1] See http://sandofsky.com/blog/git-workflow.html http://sandofsky.com/blog/git-workflow.html, and http://nvie.com/posts/a-successful-git-branching-model/ http://nvie.com/posts/a-successful-git-branching-model/ for an example.
dwb 14y ago
The importance of source control (git, svn, mercurial etc etc) is not as keenly felt by a solo developer, but imagine doing what you do in a team of developers, all trying to SFTP their own copy of the code to a server. Unworkable. Once you start using git, even on your own, you begin to see how useful it is. You commit small, well-named units of work, and you can see the history of what you wrote. Maybe you don't like a commit and you revert it. You can go back in time to any point. If you want to work on one feature in isolation, while having a stable branch that you can make hotfixes on, you can create a branch. This is very easy to do in git. If you want to work in any sort of team, learning source control (especially git, as it is very commonplace these days) is vital – and it is extremely useful just on your own too.
- RawData 14y ago
  Very good points...yeah I'll start using it.
lnanek2 14y ago
Exactly as he said, think of it as your public portfolio. Honestly, though, if you want to modernize, you should set things up so you can just git push to your web site to deploy new code to it, not FTP. Many organizations require all code that hits production be committed to source control. If you think about things from a business perspective, it's insane not to have a source control logged revision of exactly what's running on the machine. When something goes wrong the machine may not be accessible. When something goes wrong, someone will have to lookup what the latest changes were. When something goes wrong any one particular programmer may not be available.
- RawData 14y ago
  Good points...yeah I should really start doing that.
ronyeh 14y ago
That's because you have never worked in a team. :-) Read up on version control systems. Also, learn to use text editors other than notepad (emacs, vim, sublime, whatever). You can quickly become hire-able if you learn all the things that will make you valuable when working as part of a larger team.
kaffeinecoma 14y ago
"Why should I use version control?" http://stackoverflow.com/a/1408464/93995 http://stackoverflow.com/a/1408464/93995

I've never understood GitHub...I just write code in notepad and then sftp it into my server to deploy...why go through github?

by RawData 14y ago

I've never understood GitHub...I just write code in notepad and then sftp it into my server to deploy...why go through github?

krapp 14y ago

I just started using Git and Github myself... and for me, github itself is useful as an online backup for a repository (git itself being incredibly useful in terms of organizing projects) and just having a github profile looks better on your resume, etc than not having one. At the very least, your code is right there to be looked at.

RawData 14y ago
I don't want my code to be looked at though...it's proprietary. It powers the software that I sell to make a living...why would I spread it around? Though I get your general gist...
- dwb 14y ago
  A git repository doesn't have to be public, though you do have to pay for private repositories on GitHub. GitHub is great for the "network effects" of it having a lot of developers on there, maybe wanting to help out with your (public) software, but if you just want some free, private Git hosting, https://bitbucket.org https://bitbucket.org is fine.
- krapp 14y ago
  You can always start a number of personal projects or dust off some old ones and put them up on github. That's basically what I did... take code I can't really sell and use it to sell myself. Such as it is.
- propercoil 14y ago
  you pay 7 bucks or less and you can manage 5 private projects. best thing i did
aioprisan 14y ago
you don't have to make it public, it can be private. I use bitbucket, unlimited free hosting repos, and makes for much better code deployment to distributed servers etc.

fmoralesc 14y ago

[ ] You want to use git (which allows for pretty awesome workflows)[1] [ ] You want to keep some external backup you can rollback changes from. [ ] You want to allow other people to collaborate with you. [ ] You want your work to be more visible. Check as appropiate. [1] See http://sandofsky.com/blog/git-workflow.html http://sandofsky.com/blog/git-workflow.html, and http://nvie.com/posts/a-successful-git-branching-model/ http://nvie.com/posts/a-successful-git-branching-model/ for an example.

dwb 14y ago

The importance of source control (git, svn, mercurial etc etc) is not as keenly felt by a solo developer, but imagine doing what you do in a team of developers, all trying to SFTP their own copy of the code to a server. Unworkable. Once you start using git, even on your own, you begin to see how useful it is. You commit small, well-named units of work, and you can see the history of what you wrote. Maybe you don't like a commit and you revert it. You can go back in time to any point. If you want to work on one feature in isolation, while having a stable branch that you can make hotfixes on, you can create a branch. This is very easy to do in git. If you want to work in any sort of team, learning source control (especially git, as it is very commonplace these days) is vital – and it is extremely useful just on your own too.

RawData 14y ago
Very good points...yeah I'll start using it.

lnanek2 14y ago

Exactly as he said, think of it as your public portfolio. Honestly, though, if you want to modernize, you should set things up so you can just git push to your web site to deploy new code to it, not FTP. Many organizations require all code that hits production be committed to source control. If you think about things from a business perspective, it's insane not to have a source control logged revision of exactly what's running on the machine. When something goes wrong the machine may not be accessible. When something goes wrong, someone will have to lookup what the latest changes were. When something goes wrong any one particular programmer may not be available.

RawData 14y ago
Good points...yeah I should really start doing that.

ronyeh 14y ago

That's because you have never worked in a team. :-) Read up on version control systems. Also, learn to use text editors other than notepad (emacs, vim, sublime, whatever). You can quickly become hire-able if you learn all the things that will make you valuable when working as part of a larger team.

kaffeinecoma 14y ago

"Why should I use version control?" http://stackoverflow.com/a/1408464/93995 http://stackoverflow.com/a/1408464/93995