git-svn 搭配 remote git repo. 的注意事項
This all hinges on the fact thatgit svn dcommitchanges the SHA1's associated with the original git commits. With that point firmly in mind, after making a commit locally, I [optionallygit svn rebasethen]git svn dcommit, producing the final SHA1. At that point, I push to my remote git repo.
svn dcommit 跟 rebase 一樣會產生新的 commit object；所以要先作完 svn dcommit 再 push 才不會有問題。
讓 msysGit 正確處理中文
via Git 系列之二：Windows 下 Git 客户端的选择，及 msysGit 各种中文问题的解决 - 风中之哨
~/.profile
alias ls='ls --show-control-chars --color=auto'
export LESSCHARSET=utf-8
~/.inputrc
set output-meta on
set convert-meta off
git config
git config --global gui.encoding utf-8
git config --global i18n.commitEncoding Big5
git config --global i18n.logOutputEncoding Big5
--
Update 2011-04-07: 不要用 commitEncoding，而改用 logOutputEncoding，確保在不同機器上可以產生出相同的 commit object。（主要是為了 git-svn，因為 git-svn fetch 總是會產生新的 commit object。）
Using Git to manage a web site
Using Git to manage a web site
The one-line summary: push into a remote repository that has a detached work tree, and a
post-receivehook that runs "git checkout -f".
via toroid.org
- bare repository + core.worktree = detached work tree
post-receive= auto update
Solution for "rails: undefined method camelize" (FreeBSD)
Don’t panic. Everyting ok and solution is pretty simple. In fact its not a trouble with rails, but there is a missed unmentioned dependency
all you need to do:
> cd /usr/ports/converters/ruby-iconv
> make install clean
via john.vipvip.com
Java Logging Standards and Guidelines
- Use TRACE only for tracing execution flow
- Prefix all logging statements with a method name
- Use DEBUG to report results to yourself and other developers
- Use INFO to report results to Administrators and Users
- Use Guarded Logging Use StringBuffers and toString() or toPrint() to ease and improve logging
- Use Delegates, Managers, or Service classes as a logging juncture
via burlesontech.com
Wise programming techniques for writing quality code
- Think before coding
- Fix bugs immediately
- Test individual functional elements
- Test complete puzzle
- Write robust code components
- Fail as early as possible
- Avoid quick hacks
- Use defensive programming
- Prefer strong typing over dynamic binding
- Write self-explanatory code
- Avoid sophisticated code
- Avoid dense code blocks
- Avoid code duplication
- Avoid magic constants
- Strive for loose coupling
- Avoid hidden dependencies
- Strive for flat responsibility distribution
- Keep related code close together
- Build a house, not an empire
- Redesign when needed
- Do not sacrifice quality
via Developer Art
IE conditional comment gotcha
<!-- [if IE]> (bad)
<!--[if IE]> (good)
10件敏捷專案時間管理原則
- 利用DoD (Defintion of Done)
- 使用時間框(timeboxes)去管理工作
- 不要在自己的工作評估時保留buffer
- 延遲再決定
- 縮短生產週期
- 保持pipeline短而細
- 維持紀律
- 限制工作互換
- 預防持續的加班
- 分離急迫性和重要性
節錄自 David Ko的學習之旅
Original post: 10 Principles of Agile Project Time Management
