Quote of the week
Posted Jul 12, 2012 22:05 UTC (Thu)
by daglwn (guest, #65432)
[Link] (4 responses)
How did this ever make the quotes list?
Posted Jul 12, 2012 22:56 UTC (Thu)
by Tobu (subscriber, #24111)
[Link] (3 responses)
Entertainingly wrong? And while it's completely wrong for someone who has embraced Git a bit, knows that branch names are nonpermanent, repo names unimportant, and maybe knows how to do squash merges, rewrite commit metadata, restore killed lines, and reorder commits, a noob used to centralised vcs or who only uses Git through a dumbed-down (but streamlined) gui would have some reason to feel the stifling caution keybuk describes.
Posted Jul 13, 2012 13:15 UTC (Fri)
by nix (subscriber, #2304)
[Link] (2 responses)
Posted Jul 15, 2012 12:52 UTC (Sun)
by man_ls (guest, #15091)
[Link] (1 responses)
If you do not have APIs then you are not writing client-side code which calls server-side code, or not writing components or classes, or scripts called by other scripts. In any of these cases I hope you are just writing toy code, where git and unit tests are not going to make much of a difference. In any other case you have APIs even if you do not call them so, and you should test them.
The original post makes lots of silly assumptions: you do not need to create a git repo right from the start, you can wait for a while before the first
However, the most glaring error of the whole post is right at the start:
Posted Jul 15, 2012 13:16 UTC (Sun)
by nix (subscriber, #2304)
[Link]
Posted Jul 14, 2012 9:31 UTC (Sat)
by Rudd-O (guest, #61155)
[Link]
Quote of the week
Quote of the week
Quote of the week
Personally I like to be the first one to exercise my own APIs; unit tests allow me to iterate much faster than waiting for external input.
Quote of the week
git init and before you start committing. Anyway nobody is going to look at your whole history to discover your mistakes anyway, unless you are Linus Torvalds and your first commit reads "starting toy project, having some fun" -- and in that case you will probably not care much.
It was pretty easy, you opened your favorite text editor with a clean, inviting blank page and a flashing cursor and started typing with no real thought about where was best to start.
What? Flashing cursor? Immediate fail!
Quote of the week
Personally I like to be the first one to exercise my own APIs; unit tests allow me to iterate much faster than waiting for external input.
Quite. If you claim you got a nontrivial API right without implementing at least one and probably two or more users, you are either a highly-experienced genius or you are a liar. Probably the latter. API design is hard (and no, that doesn't mean the things should be patented, it means they should be shared more aggressively so that everyone can benefit).
Quote of the week