Recently I cloned a large remote git repository into my localhost, but failed and I got the error:
Cloning into 'D:\xampp\path\to\my\folder'...
POST git-upload-pack (350 bytes)
remote: Counting objects: 7544, done.
remote: Compressing objects: 100% (3985/3985), done.
fatal: early EOF
fatal: The remote end hung up unexpectedly
fatal: index-pack failed
In the last few days, I was looking for how to format a code block in my Google doc. After a few minutes I googled, I found a very useful Google Docs add-on Code Pretty. Just needs to select the code text you want to format and its “Format Selection” is pretty nice. The only con is that you cannot choose the programming language you want to format.
I started this blog when I’ve read one of the write-ups by Scott Hanselman, a program manager at Microsoft, author and avid blogger and speaker. Visit his blog, hanselman.com, for more productivity tips.
Pulling a page from author and software developer Jon Udell, Hanselman encourages you to “conserve your keystrokes.” What does this mean? He explains by example:
If Brian emails me a really interesting question about ASP.net … and I send him back an exciting and long, five-paragraph with a code sample email that solves his problem, I just gave him the gift of 10,000 of my keystrokes. But there is a finite number of keystrokes left in my hands before I die, and I am never going to get those keystrokes back and I’ve just gifted them to Brian. And I don’t even know if he reads that email. So what should I do to multiply these keystrokes given that there is a finite number of those keystrokes left in my hands? I write a blog post and I mail him the link. Then after I’m dead, my keystrokes multiple—every time I get a page view that’s 5,000 keystrokes that I did not have to type.