IT界討論區:刷排名(18)

入咗間中小企做，啲嘢冇Resources好難跟，但專業Programming冇我想像中咁難。

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

入咗間中小企做，啲嘢冇Resources好難跟，但專業Programming冇我想像中咁難。

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

入咗間中小企做，啲嘢冇Resources好難跟，但專業Programming冇我想像中咁難。

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

入咗間中小企做，啲嘢冇Resources好難跟，但專業Programming冇我想像中咁難。

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

有冇人後悔做it9
日日對著mon真係悶撚死
除左人工高d 真係無其他好處

呢個年代, 有咩OFFICE工唔使對MON. 對人你死得仲快.

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

直接搵另外一份，拎到Offer後同HR講你有心轉工。

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

我覺得係：
1 一行打一句COMMENT
2 例如明知有SQL INJECTION 仲用STRING 砌
3 METHOD 名 1 2 3 4

小心寫壞手勢

只要唔係下下都用Third party多啲自己Build嘢，反而咁先學到最多嘢練到最勁。

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

其實你可以當係幫自己整理返自己做過乜嘢，整咗咩FEATURE
他日要同人解釋都多D 內容9UP
COMMENT 真係好重要。
到你D 嘢多到唔記得，自己跟返都易好多

寫壞手勢一：亂咁COMMENT
寫壞手勢二：用埋啲一早有問題既寫法
寫壞手勢三：啲名亂咁嚟

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

我覺得係：
1 一行打一句COMMENT
2 例如明知有SQL INJECTION 仲用STRING 砌
3 METHOD 名 1 2 3 4

1行1句comment

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

我覺得係：
1 一行打一句COMMENT
2 例如明知有SQL INJECTION 仲用STRING 砌
3 METHOD 名 1 2 3 4

1行1句comment

1行1句comment,個program比街外人睇？

我覺得呢三樣唔係寫壞手勢，係概念唔好。

1. Comment is very important as long as the code is going to be viewed by anyone other than yourself.

2. I think he means spaghetti code, jumping from a to b but don’t show logic.

3. Names like: boolean: IsAlive(), String: getCustAC(), is good practice I think, but one is not very black and white

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

我覺得係：
1 一行打一句COMMENT
2 例如明知有SQL INJECTION 仲用STRING 砌
3 METHOD 名 1 2 3 4

1行1句comment

1行1句comment,個program比街外人睇？

1行1句comment正
即使opensource都冇咁多comment

諗吓後人啦 要接手都惡頂架，當練吓英文，向人解釋嘢就最好練習。

另外啲嘢加返@author做功德收集器

我覺得係：
1 一行打一句COMMENT
2 例如明知有SQL INJECTION 仲用STRING 砌
3 METHOD 名 1 2 3 4

1行1句comment

1行1句comment,個program比街外人睇？

1行1句comment正
即使opensource都冇咁多comment

一行一句command你打code定打文

知唔知實* 位*堂 。IT 好唔好做 見佢請人

知唔知實* 位*堂 。IT 好唔好做 見佢請人

知唔知實* 位*堂 。IT 好唔好做 見佢請人

知唔知實* 位*堂 。IT 好唔好做 見佢請人

我而家 都係 公司做 賭船

請唔到system administration就叫 it associate 搞server

知唔知實* 位*堂 。IT 好唔好做 見佢請人

我而家 都係 公司做 賭船

請唔到system administration就叫 it associate 搞server

無錢先請唔到姐

好婆媽點下

好婆媽點下