Skip to content

Home

偽Scrum - 瀑布式和敏捷的混合體

我有些事情要告訴你:你並非真正的敏捷。你可能已經完成了所有的 Scrum 儀式,如站立會議、示範和檢討。你甚至可能有所有必要的工具,如JIRA、使用者故事和Scrum看板。然而,如果心態不正確,那麼某些基本的東西仍然缺失。以下是原因:

你有一個詳細的計劃

你正在堅持嚴格的一年期限。Scrum團隊根據在衝刺計劃期間做出的估算來計算速度。那麼,你怎麼能期待Scrum團隊與高層管理的最佳猜測相符呢?當路線圖是固定的,範圍不變,並且發布計劃不切實際時,你實際上正在遵循瀑布模型。

真正的Scrum Master缺席

你的組織圖上可能有一個Scrum Master,但他們的實際角色是什麼?通常,這個人不是全職的Scrum Master,而是一個項目經理、產品擁有者或者資深開發者,他們並未全心投入這個角色。當Scrum Master兼顧多項責任時,事情就開始出軌。即使你有一個專門的Scrum Master,他們可能也無法解決由於技術複雜性或超出他們工作職責的限制所帶來的實際障礙。

沒有指定的產品擁有者

需要有人負責產品,但通常這個人會被其他優先事項所佔據。如果沒有明確的視野和產品所有權,特性開發可能會出錯。當要求由外部高級主管指導時,這一點尤其正確,導致開發努力被浪費。雖然產品擁有者應該做出這些決定,但很少有人願意冒這些風險,許多人對他們實際想要什麼並不確定。

缺乏預算策略

故事點並不能替代預算。當你操縱估算來獲得更多的資金和時間,或者為了符合預算限制而向下談判,你就會對團隊的真實速度失去了視覺。傳統的會計方法也與敏捷開發不兼容。在預算上吝嗇往往會導致團隊燒休息,而不達到預期的結果。

我對敏捷宣言的看法

以下是我用自己的話來解釋敏捷宣言:把對變化的反應性放在遵循高級管理層設定的嚴格路線圖之上。尊重個人和互動超過辦公室政治。強調工作軟體超過無休止,毫無意義的會議。偏愛客戶合作超過預算談判。實現這一點並非易事,但對於官僚機構來說,這是在數位時代適應和繁榮的唯一途徑。

Deploying a Koa.js Application to an AWS EC2 Ubuntu Instance

I am developing an application using Koa.js, a new web framework created by the team behind Express. In this step-by-step tutorial, I'll guide you through deploying a Koa.js application on an Amazon Web Services (AWS) Ubuntu server.

Launching the Ubuntu Instance on AWS

First, launch an Ubuntu instance on AWS. You'll need to modify the security group settings.

Security Group Settings

If you don't make these changes, attempting to access the public domain in a browser will result in a "Connecting" state until it times out, rendering the site unreachable.

Site Unreachable

By default, the launch wizard only enables SSH.

SSH Only

Click the "Edit" button to add inbound rules for HTTP port 80 and HTTPS port 443.

Edit Inbound Rules

Installing Node.js

SSH into your instance and install Node.js according to the official documentation:

curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs

Setting Up Nginx as a Reverse Proxy Server

Next, install Nginx:

sudo apt-get update
sudo apt-get install nginx

Open the configuration file and make the following edits. Don't forget the semicolons:

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    root /var/www/yourApp;

    location / {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

Save the file and restart the Nginx service:

sudo systemctl restart nginx

Deploying Your Application

Clone your Git repository into the /var/www/yourApp directory. You'll likely encounter a "Permission Denied" error, so change the ownership of the folder:

sudo chown -R ubuntu /var/www

Create a simple app.js to run your server:

var koa = require("koa")
var app = koa()

// logger
app.use(function* (next) {
  var start = new Date()
  yield next
  var ms = new Date() - start
  console.log("%s %s - %s", this.method, this.url, ms)
})

// response
app.use(function* () {
  this.body = "Hello World"
})

app.listen(3000)

Start the server:

node app.js

Open your browser and navigate to your public domain. You should see your Koa.js application running.

App Running

Done! Feel free to leave a comment below if you have any questions. :)

將 Koa.js 應用程式部署至 AWS EC2 Ubuntu 實例

我正在使用 Koa.js 開發一個應用程式,這是一個由 Express 團隊創建的新網頁框架。在這個逐步教學中,我將指導您如何在 Amazon Web Services (AWS) Ubuntu 伺服器上部署 Koa.js 應用程式。

在 AWS 上啟動 Ubuntu 實例

首先,在 AWS 上啟動一個 Ubuntu 實例。您需要修改安全組設定。

Security Group Settings

如果您沒有進行這些更改,試圖在瀏覽器中訪問公共域將導致“連接”狀態,直到超時,導致無法訪問網站。

Site Unreachable

默認情況下,啟動嚮導僅啟用 SSH。

SSH Only

點擊“編輯”按鈕以添加適用於 HTTP 端口 80 和 HTTPS 端口 443 的入站規則。

Edit Inbound Rules

安裝 Node.js

通過 SSH 登入您的實例並根據官方文檔安裝 Node.js:

curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs

設置 Nginx 作為反向代理伺服器

接下來,安裝 Nginx:

sudo apt-get update
sudo apt-get install nginx

打開配置文件並進行以下編輯。別忘了分號:

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    root /var/www/yourApp;

    location / {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

保存文件並重新啟動 Nginx 服務:

sudo systemctl restart nginx

部署您的應用程式

將您的 Git 存儲庫克隆到 /var/www/yourApp 目錄。您可能會遇到“Permission Denied”錯誤,所以更改文件夾的所有權:

sudo chown -R ubuntu /var/www

創建一個簡單的 app.js 來運行您的伺服器:

var koa = require("koa")
var app = koa()

// logger
app.use(function* (next) {
  var start = new Date()
  yield next
  var ms = new Date() - start
  console.log("%s %s - %s", this.method, this.url, ms)
})

// response
app.use(function* () {
  this.body = "Hello World"
})

app.listen(3000)

啟動伺服器:

node app.js

打開您的瀏覽器並導航到您的公共域。您應該看到您的 Koa.js 應用程式正在運行。

App Running

完成!如果您有任何問題,請隨時在下面留言。:)

Lessons Learned from an IoT Project

Last year, I worked on an Internet of Things (IoT) project focused on a Bluetooth smart gadget. The experience differed significantly from pure software development in several ways:

Firstly, integration posed a challenge because the project's mechanical, firmware, mobile app, and design components were outsourced to multiple vendors. These vendors had geographically dispersed teams and varying work cultures. When developers are so specialized in their fields that they work in silos, the Scrum model is unlikely to function effectively.

Secondly, the duration of hardware iterations far exceeded that of software iterations, making it difficult to adapt to changes. Unlike software, which can be easily modularized, many hardware components like chips and motherboards are interconnected. This situation pushes the development process toward a more waterfall-like approach. You either receive the entire prototype or nothing at all; there's no middle ground for delivering a Minimum Viable Product (MVP) for consumer testing. The absence of early user feedback further hampers the feature prioritization process.

Thirdly, diagnosing issues becomes particularly challenging when things go wrong. It's difficult to determine whether the problem lies in the mechanical design, firmware, or mobile app development. Additionally, end-to-end testing becomes more complex as interfaces evolve. Conducting tests without comprehensive hardware automation was also time-consuming. To alleviate this, it's essential to have clearly defined and testable acceptance criteria, ensuring a strict definition of "done."

Effective communication is crucial for the success of any IT project, especially when various aspects aren't progressing as planned. Finger-pointing and defensiveness can severely damage interdepartmental relationships. Effective communication requires empathy; try to understand issues from the other person's perspective instead of reacting emotionally or judgmentally.

Customers assess performance based on the value they derive from a product. Adopting an empathetic and problem-solving mindset can reduce wasted time and effort, thereby improving overall performance. I look forward to the product's release and the positive reactions from its end-users.

從物聯網項目中吸取的教訓

去年,我參與了一個專注於藍牙智能裝置的物聯網(IoT)項目。這個經驗與純軟體開發在幾個方面有顯著的不同:

首先,集成帶來了挑戰,因為項目的機械設計、固件、手機應用程式和設計組件被分包給多個供應商。這些供應商有地理上分散的團隊和不同的工作文化。當開發人員在他們的領域專門化到組織成獨立的群體時,Scrum模型不太可能有效運行。

其次,硬體迭代的時長遠超過軟體迭代,使其難以適應變化。與軟體不同,軟體可以輕易被模塊化,許多硬體組件如晶片和主機板卻是相互關聯。這種情況推動了開發過程向著更像瀑布模型的方向。你只能收到整個原型或者一無所有;沒有傳遞一個用於消費者測試的最小可行產品(MVP)的中間地帶。早期用戶反饋的缺乏進一步阻礙了特性優先級的確定過程。

第三,當事情出錯時,診斷問題尤其具有挑戰性。很難確定問題是出在機械設計、固件還是手機應用程式的開發。此外,隨著介面的演變,端到端的測試變得更加複雜。在沒有全面的硬體自動化的情況下進行測試也很耗時。為了緩解這一點,有必要明確並可驗證的接受準則,確保“完成”的嚴格定義。

對任何IT項目的成功而言,有效的溝通至關重要,特別是當各個方面沒有按計劃進展時。指責和防衛可以嚴重損害部門之間的關係。有效的溝通需要同理心;嘗試從他人的角度理解問題,而不是情緒化或判斷式地反應。

客戶根據他們從產品中獲得的價值來評估性能。採取同理心和解決問題的思維方式可以減少浪費的時間和精力,從而提高整體性能。我期待著產品的發佈和最終用戶的積極反饋。

How to Fix iOS 10 Permission Crash Errors

I've been developing an app that requires access to the user's microphone.

The app worked fine on iOS 9, but after upgrading to iOS 10, it started crashing. The error message displayed in the terminal reads as follows:

> This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSMicrophoneUsageDescription key with a string value explaining to the user how the app uses this data.
> (lldb)

To resolve this issue, edit the Info.plist file as source code and add the following lines:

    <key>NSMicrophoneUsageDescription</key>
    <string>Provide a description explaining why your app needs microphone access.</string>

Additionally, if your app needs access to the user's camera, add the following:

    <key>NSCameraUsageDescription</key>
    <string>Provide a description explaining why your app needs camera access.</string>

If your app requires access to the user's contacts, add this:

    <key>NSContactsUsageDescription</key>
    <string>This app requires access to your contacts.</string>

Happy coding!

如何修復 iOS 10 權限崩潰錯誤

我一直在開發一款需要訪問用戶麥克風的應用程序。

該應用在 iOS 9 上運行正常,但在升級到 iOS 10 之後,它開始崩潰。終端顯示的錯誤消息如下:

> 此應用程序已崩潰,因為它試圖訪問隱私敏感數據而未提供使用說明。應用程序的 Info.plist 必須包含一個 NSMicrophoneUsageDescription 鍵,並提供一個字符串值解釋應用程序如何使用這些數據。
> (lldb)

要解決此問題,按源碼編輯 Info.plist 文件並添加以下行:

    <key>NSMicrophoneUsageDescription</key>
    <string>提供一個說明,解釋您的應用為何需要訪問麥克風。</string>

此外,如果您的應用需要訪問用戶的相機,請添加以下內容:

    <key>NSCameraUsageDescription</key>
    <string>提供一個說明,解釋您的應用為何需要訪問相機。</string>

如果您的應用需要訪問用戶的聯繫人,請添加以下內容:

    <key>NSContactsUsageDescription</key>
    <string>此應用需要訪問您的聯繫人。</string>

祝你編碼愉快!

The Future of FinTech in Hong Kong

I was often told by my teachers that Hong Kong is an international financial center. Indeed, in our highly competitive corporate environment, we enjoy economic success daily. However, Hong Kong currently lags in the FinTech revolution. Singapore has seized this opportunity and has aggressively moved ahead. The Singaporean government has played a crucial role in attracting FinTech companies by providing incentives and clear regulations. Moreover, the extensive client base available to mainland China's FinTech firms has enabled them to thrive in ways that Hong Kong companies haven't.

The challenge is clear: Hong Kong's risk-averse mentality is slowing the progress of the FinTech industry. As an IT consultant, I've heard numerous individuals in the banking sector express concerns about innovations like blockchain, Bitcoin, and mobile payments. They fear these technologies could disrupt their businesses, jeopardize jobs, and result in big companies failing to adapt.

However, there's a silver lining: Hong Kong is home to a large number of innovative and creative individuals. Our community boasts a diverse group of thinkers, builders, and leaders. We have the potential to assemble outstanding teams that can inspire and contribute to the creation of the world's best FinTech ecosystem. Now is the time to elevate our awareness and reimagine what is possible when financial technology serves as a catalyst for positive industry transformation.

In my opinion, this is the desired outcome: we are guiding global financial technology to become more human-centered. Our current legal sandbox policy allows companies to test their innovative ideas in the marketplace. These financial technologies have the potential to positively impact people's lives around the globe. Together, let's utilize the language and tools of FinTech to reestablish Hong Kong as the regional hub for FinTech commerce.

香港金融科技的未來

我經常被我的老師告知,香港是一個國際金融中心。確實,在我們競爭激烈的企業環境中,我們每天都享受著經濟的成功。然而,香港目前在金融科技的革命中落後了。新加坡已經抓住了這個機會,並積極地前進。新加坡政府在吸引金融科技公司方面起著至關重要的作用,他們提供了激勵措施和明確的規章制度。此外,中國內地金融科技公司可用的廣大客戶基礎使得他們能夠以香港公司無法實現的方式蓬勃發展。

挑戰十分明顯:香港過於保守的心態正在減緩金融科技行業的進步。作為一名 IT 顧問,我聽到許多銀行業的人對像區塊鏈、比特幣和移動支付等創新科技表示擔憂。他們擔心這些技術可能會破壞他們的業務,威脅工作,並導致大公司無法適應。

然而,這裡有一線希望:香港擁有大量的創新和創造力的個體。我們的社區擁有多樣化的思考者,建設者,和領導者。我們有可能組建優秀的團隊來啟發並為創造世界上最好的金融科技生態系統做出貢獻。現在是提高我們的意識,重新想象當金融科技作為正向產業轉型的助推器時,可能會發生什麼。

依我看,這是我們期望的結果:我們正引導全球的金融科技變得更以人為本。我們目前的法律沙盒政策允許公司在市場上測試他們的創新想法。這些金融科技有可能對全球人民的生活產生積極的影響。讓我們一起利用金融科技的語言和工具,將香港重新建立為金融科技商業的區域中心。

What is Blockchain and How is It Used?

Many of my friends have been asking about the emergence of the blockchain revolution. According to recent news, four of the world's largest banks have teamed up to develop a new form of digital cash. This digital cash aims to become an industry standard for clearing and settling financial trades over blockchain technology. Meanwhile, Ripple has raised $55 million in Series B funding. In my opinion, there's no doubt that blockchain has the potential to disrupt traditional banking.

What Is It?

Blockchain is a data structure that serves as a digital ledger for transactions. This ledger is shared among a distributed network of computers, numbering in the millions. Utilizing state-of-the-art cryptography, the technology securely manages the ledger. Blockchain operates on a consensus model: every node agrees to every transaction, thereby eliminating the need for a central counterparty (CCP) in traditional settlement processes.

How Is It Used?

Blockchain offers broad implications for cross-currency payments by making them more efficient. It eliminates time delays and reduces back-office costs. In response to growing customer demands for faster, lower-cost global payments, blockchain allows for direct bank-to-bank settlements. Some applications of this technology include remittance services for retail customers, international transactions, corporate payments, and cross-border intra-bank currency transfers.

What is the Innovation?

The technology offers the opportunity for transactions to occur without needing to know who the other party is. Its most innovative feature is the idea of a distributed database, where trust is established through mass collaboration rather than through a centralized institution responsible for authentication and settlement.

What Problems Could Be Solved?

The potential applications of blockchain extend beyond the financial market. This technology could provide an immutable record that can be trusted for various uses. Current identity infrastructure is easily compromised; however, in a blockchain, once a block of data is recorded, it becomes very difficult to alter. Thus, it can be used for genuine privacy protection. Whenever someone attempts to add data to the blockchain, all existing copies run algorithms to verify the transaction. Malicious attempts to defraud the system are rejected, while proposed transactions are approved when a majority of nodes agree on their validity by cross-referencing the blockchain history. As a result, blockchain could serve as the basis for an open protocol for web-based identity verification, creating a 'web-of-trust' and storing data in an encrypted format.

References
  1. Martin Arnold, "Big banks plan to coin new digital currency," Financial Times, August 24, 2016, Financial Times Article
  2. Alyssa Jarrett, "Ripple Raises $55 Million in Series B Funding," Ripple official website, September 15, 2016, Ripple Article
  3. Don Tapscott, Alex, and Rik Kirkland, "How Blockchains Could Change the World," McKinsey & Co, May 8, 2016, ValueWalk Article