Kevin Chiu

Tagged: programming RSS

• Kevin Chiu 12:26 pm on November 19, 2008 Permalink | Reply
  Tags: git ( 3 ), programming   

  Git Rebase 

  I was having a discussion about git the other day and rebase came up.

  My normal workflow didn’t involve rebase; so, my natural curiosity sparked up and I dove into the documentation.

  It turns out git-rebase is quite controversial. (And, you should avoid it if you’re sharing your commits.)

  Linus Torvalds on rebasing:

  * [http://kerneltrap.org/Linux/Git_Management](http://kerneltrap.org/Linux/Git_Management)
  * [http://lwn.net/Articles/291302/](http://lwn.net/Articles/291302/)
  * [http://lwn.net/Articles/291303/](http://lwn.net/Articles/291303)
  * [http://lwn.net/Articles/291304/](http://lwn.net/Articles/291304/)

  Random Redditors:

  * [http://www.reddit.com/r/programming/comments/6ube0/synchronizing_development_rebase_vs_pullmerge_git/?sort=top](http://www.reddit.com/r/programming/comments/6ube0/synchronizing_development_rebase_vs_pullmerge_git/?sort=top)

   

  Reply Cancel reply

  Required fields are marked *

  Name *

  Email *

  Website

  

• Kevin Chiu 9:19 am on November 19, 2008 Permalink | Reply
  Tags: django ( 3 ), erlang ( 5 ), erlyweb, php, programming, python ( 4 ), ruby ( 9 ), ruby on rails ( 2 ), zend   

  Tipping Point? 

  

  Down: Rails

  Up: Django and Zend Framework(?!)

  Odd: Erlang (Erlang is hot… but I guess not that well known yet?)

  Reading: Erlang at Kevin’s Blog is discussing. Toggle Comments

   

• Kevin Chiu 8:36 am on November 19, 2008 Permalink | Reply
  Tags: git ( 3 ), programming   

  Git Blame is awesome 

  At work, I manage a software product with 19 contributors, most of whom are no longer active.

  For my situation, git blame is seriously awesome.

  When someone starts typing their personal email into the code base in some random area and accidentally checks it in, you can figure out exactly who is lazy with focusing their windows.

  (I wonder if there’s a way to automatically reject pushes that don’t pass spec tests…)

  Todo: check out git bisect

   

• Kevin Chiu 10:17 am on November 13, 2008 Permalink | Reply
  Tags: collaboration, programming, teamwork   

  Code Scent 

  UPDATE: git blame does this!

  One day, you find yourself happily hacking away at some code you checked out from one of your collaborative coding projects and BAM!, you hit a gnarly bit of one-line wizardry that completely blows your mind. While it may read like English and be as concise as an abridged Cliff Notes, the functionality you need to modify is crystallized somewhere between the continuations and inline DSL definitions.

  Who wrote this?

  The solution to this would be what I call Code Scent (as opposed to Code Smell). With Code Scent, you’d be able to see code history on a line-by-line or better granularity. Imagine, if you will, selecting a menu option and getting a highlighting scheme that told you who touched which piece of code most recently:

  

  Stolen from Moonedit. Not the most complex code, but you get the idea…

   

• Kevin Chiu 11:46 pm on October 27, 2008 Permalink | Reply
  Tags: Google ( 63 ), programming   

  An Idea for Chrome Extension Development 

  One problem people have with Firefox is that sometimes its extensions run amok and gobble up tons of memory or freeze the browser with resource hogging tasks.

  Well, ponder this: Currently, Chrome monitors its processes, including individual tabs and plugins.

  

  It doesn’t take a huge stretch of the imagination to project this kind of analysis into the world of extensions. Advanced extension users could spot sources of slowdown in the browser, and Google could provide supplemental tools to help extension developers drill down into nether regions of their extensions to enhance speed and memory usage. As an added bonus, extensions could be tracked individually, allowing the developers to receive live aggregated feedback on their extensions’ performance in the wild.

  Imagine — Google Analytics for your Chrome Extensions!

  

  Other hopeful features for Extensions:

  * Updates are installed without forcing a browser reboot.
  * If individual extensions malfunction, they don’t bring the browser down.
  * Extensions are as easy to write as web apps. (CSS/HTML/JS)