Build 2018 大會系列 Part 2: Windows Development

// Build 2018 對於 Windows Development 提出了很多内容,包括:更進階的 Fluent Design, .NET Core 3.0, MSIX, Windows 10 on ARM … 等,這篇將整理每個 Sessions 的重點,方便大家更快瞭解。
Continue reading

Posted in Windows | Tagged , , , , , , , , , , , | Leave a comment

Build 2018 大會系列 Part I: The Future of C#

Part I 比較特別一點,其他篇會是濃縮重點為主,不過因為是關於語言的,除了把 //Build 2018 的 The Future of C# 中的重點節錄外,也順便自己也整理了一些 C# 7.0 ~ 7.3 的新特性,覺得 C# 7 的幾個新的特性的調整主要算是效能為主,讓我們往下看下去。
Continue reading

Posted in Windows | Tagged , , , | Leave a comment

Google I/O 2018 Android 相關 Session 摘要 – 上集

今年 2018 我們也針對 Google I/O 影片中的 Android 相關議題做了懶人包分享,雖然說是各影片的摘要,但篇幅還是有點長,不過還是建議從事 Android App 開發工作的朋友們讀讀,對於了解這一年過去及未來即將發生的事會很有概念。
Continue reading

Posted in Android, KKBOX | Leave a comment

Google I/O 2018 Android 相關 Session 摘要 – 下集

今年 2018 我們也針對 Google I/O 影片中的 Android 相關議題做了懶人包分享,雖然說是各影片的摘要,但篇幅還是有點長,不過還是建議從事 Android App 開發工作的朋友們讀讀,對於了解這一年過去及未來即將發生的事會很有概念。
Continue reading

Posted in Android, KKBOX | Leave a comment

KKBOX 的 WWDC 2017 讀書會影片

又到了歡樂的 WWDC 讀書會時間,今年我們挑選了12個主題來研讀。相信大家也跟我們一樣,每年到這個時候總會很『開心』的學習 Apple 發佈的新技術 \O/

  1. Swift and Foundation
  2. Xcode Debug
  3. Xcode IDE
  4. UIKit
  5. UIKit-Drag and Drop
  6. WatchOS (watchOS, webView)
  7. Notifications, Layout
  8. SiriKit, Core Spotlight
  9. Security (Networking, Apple pay, Device check)
  10. Performance, Testing
  11. Audio, AirPlay 2
  12. Core Image

Swift and Foundation – Liyao


Xcode Debug – Oliver


Xcode IDE – Hardy


UIKit – QQ


UIKit-Drag and Drop – Mario


WatchOS (watchOS, webView) – Dada


Notifications, Layout – Jefferey


SiriKit, Core Spotlight – Seraph


Security (Networking, Apple pay, Device check) – Antony


Performance, Testing – Hokila


Audio, AirPlay 2 – Dolphin


Core Image – Daniel Tien


Posted in Code, iOS, KKBOX, Uncategorized | Tagged , , , , , | Leave a comment

[KKS Tech. talk] 輕輕鬆鬆認識專利

之前在整理隨身碟裡的文件時,看到一份在前公司時做的投影片,是有關專利知識的介紹, 身處科技爆發時代的大家,對於了解一些專利常識滿有興趣,所以當時的反應不錯。因此,有了把文件做增修後,於KKStream再次介紹的想法,也希望透過一些專利實例,讓研發人員們理解一些發明概念及創新的可能方向。

從過去案例中(Polaroid vs Kodak, eBay vs MercExchange),可體認到專利制度對於產業的影響,其實除了採主動積極的保護專利權人權益外,將手上的專利權作為談判籌碼的”護身符”模式也是一種專利的應用方向(HTC vs Apple透過交互授權達成和解協議)。但是將發明申請專利,有其伴隨的義務要付出: 公開發明內容與繳納各項費用,公開發明內容在申請18個月後進行,以發明專利審查期長達2~4年來說,也就是專利核准前(還不知未來是否會過關)就得公開。將來若有他人侵權發生,是否有能力/財力去維護專利權也會是申請專利時的考量,只能說這是有錢人才能玩的遊戲啊~

撇開這些考量,那什麼可以申請專利呢? 基本上只要不在專利法裡負面列表,且符合專利實質審查所要求的三大專利要件:新穎性(無習知技術(prior art)). 進步性(非顯而易見). 具產業利用性。

那究竟發明難不難呢? 從現有的專利中,我們可以整理出幾個較為簡單的創新方向:
* 組合發明- 將多個現有產品組合出新用途。
* 逆向思考- 思維轉個彎,也許會就有新作法。
* 使用上的痛點,表示有改進空間,是可以研究的地方。

因此,透過專利,除了是理解現今產業的遊戲規則外,也是一種能快速了解別人技術. 產業方向,以及幫助自身發展創新的途徑。

整理了一下今天下午分享會裡的一些討論, 以及附上今天的投影片:
Q: 若是在台灣申請到了發明專利,兩三年後才想到要去美國申請專利,這樣還適用WTO會員國的國際優先權嗎?
A: 不適用,發明專利的優先權期是12個月。所以產品在未來要上市前就需要規劃好將來的專利佈局,包含產品裡哪些技術是需要申請專利的,以及將來產品是要銷往哪些市場,事先就規劃好在將這些技術在哪些國家申請專利。

Q: 如P.19頁投影片裡,假設我發明了配有鉛筆的帽子,但是帽子本身的專利是握在其他人手裡,那這樣我還可以生產配有鉛筆的帽子嗎?
A: 不行,雖然你握有鉛筆帽子的發明專利,但是也同時踩在別人的專利權上,所以必須先得到帽子的授權,才能生產鉛筆帽子。

Q: 申請專利大概要花多少錢啊?
A: 各項目的價目表:台灣專利規費清單美國專利規費整理

Q: 既然專利法是屬地主義,那如果我在某個小國家裡,看到一個東西不錯,拿去美國申請專利,這樣會過關嗎?
A: 如果在2011年美國專利法修法前申請的,可能會過,之前的prior art範圍限於美國境內,但2013年開始實施新法後,prior art範圍擴張到全球,只要審查時被發現,申請案便會因新穎性不足而被駁回,或是事後被他人舉發(新穎性不足)導致專利無效。

Q: 將來如果英國脫離歐盟,會影響他在歐洲專利局的成員身份嗎?
A: 歐洲專利局(EPO)是歐洲國家處理專利申請的統一窗口,有自己的會員國組織,也非歐盟機構,所以將來英國脫離歐盟,不會影響他EPO成員身份。

 

Posted in KKStream, KKV | Tagged , | Leave a comment

Google I/O 2017 Android 相關 Session 摘要 – 上集

部門內總是習慣大家分著看東西,再互相分享,這是我們團隊內保持快速移動的有效方法之一,今年我們也針對 Google I/O 2017 上百部影片中的 Android 相關議題做了分享,算一算這是我們第四年分享懶人包了呢 :P
Continue reading

Posted in Android | Leave a comment

Google I/O 2017 Android 相關 Session 摘要 – 下集

部門內總是習慣大家分著看東西,再互相分享,這是我們團隊內保持快速移動的有效方法之一,今年我們也針對 Google I/O 2017 上百部影片中的 Android 相關議題做了分享,算一算這是我們第四年分享懶人包了呢 :P
Continue reading

Posted in Android | Leave a comment

Brainstorming, Brain Storming, Brain and Storming

So the story started like this. CMS team has been developing some first-class and highly customized content management system at enterprise level for some time now. We have reached a point where we can boldly called our product stablized, of which allows us to explore more with experiences gained from current product. It was a simple casual small chat with Drake one morning that there has always been a blind side of engineers to view a product from users’ perspective while eighty or even more percent of CMS users are not engineers. Drake suggested to hold an event much like coding day we had few months ago to inspire creativity in constructing CMS v2. One small chat led to consequent discussions with various personnels to bring brainstorming into reality. Big thanks to Vicky and Elaine of all the planning, suggestions, and mostly, their effort to offer anything within or without their personal boundaries. Without them, there would not be an event hosted in KH nor would there be an elegant afternoon tea time.

I did not sense much excitement the first time CMS v2 brainstorming event was announced to CMS team in KH. Since CMS team will play an important role in the event, I have secretly considered myself doomed from the beginning. I myself was a virgin of event planning. I have little to none experience in ordering food and even for the few times I did, I never could get the numbers right. This is just how much I was doomed. In the area, where in my narrow mindedness, was considered a wild wild west (and here I missed all my capable friends in Taipei), I have no event planning skills with a team of shy engineers like me. If it has been a declaration of a war, after much deliberation, as Spark would say, it would only seem logical to simply surrender.

6:30 Friday night before Monday event.

Timing is a tricky thing. To CMS team, production release is a big thing. We have zero failure tolerance policy for production release. Testing usually lasts around a week if everything goes well. On top of regular production release effort, we are also a scrum team. Sprint tasks are expected to be carried out on-schedule by all means. Brainstorming event was caught in the middle of our release cycle, which means even with careful plannings, the team still would have to suffer much overtime work to accommodate any additional effort for the event. As always, a great achievement comes with much hard works and sacrifices. It was then I realized I have worked with some really talented people with much endurance and willingness. It was Friday night close to the end of the day, last working day before the event took place. I stood up hoping to grab someone for an update on preparation on brainstorming event, and I realized all CMS team members has vanished from their desk. To my amazement, all of them has managed to find themselves a quiet corner to craft for the event.

There were 12 participants for this event where we decided to equally divide them up into three competing groups. With each competing group, there is going to be a owner leading and answering questions. Team owners are responsible to design a logo and motto for their team. Every CMS team members were also asked to do a bit of background research on each participant.

Songs on demand

QR code to help people access songs-on-demand system. A brief instruction is listed below QR code. Instruction was placed on each table.

In order to better facilitate this event, we asked Dada, an intern engineer in CMS team, to assist us with music that matched theme of each session. Much to my surprise, not only did he made a decent selection of music to play, he managed to assemble a songs-on-demand system that allowed participants to order songs of their preferences.

Brainstorming event was scheduled at 12 o’clock but team started arranging meeting place three hours prior to the beginning of the event. We wanted to kick start the meeting with more casual settings, to ease participants into thinking mode after a long trip with some mild constraints. Hence there were six categories named from our past experience with content management system development. Every category was assigned an owner responsible in conducting their own sales package. This part of activity was designed with dual purposes. First of all, owners were to gain more insightful knowledge on their designated category. In the meantime, participants received digested information in understandable representation through interactions with category owners. To make this activity even more challenging for CMS team, category owners were asked to act as sales representatives of their category. They need to gather enough ideas from people to fulfill his or her sales target. Otherwise category owners had to draft ideas to make up their sales target.

Categories specially designed by each CMS team member.

It was 9:30, out of blue moon, Drake slacked to ask for KH office address. He was in the U.S. for Google conference only a day before and decided to come to us directly from Taoyuan international airport after 14 hours of flight. Upon arrival, he went through event programme one last time before everyone arrives in the hopes to refine it with more insights. He has pointed out that the last part of the programme, which consisted a 1.5 hour long of idea crafting session, might be dreadful to participants while regular human concentration span lies around 30 minutes. As an agile team, we were accustomed to changes. Although it was not in my nature to embrace sudden change to the plan, I bowed to the suggestion for it did show a blind spot in our programme. Hence one idea crafting session was splitted into two sessions with the first one lasted thirty minutes and the second one forty-five to sixty minutes. This change was later on proven a success. People were more clear on how to present and implement on their ideas after brief retrospective session of the first idea crafting session.

Weekly meeting.

We started out with weekly meeting. It was a memorable time in the history that KH team has generally equivalent number of personnels in comparison with Taipei team. We invited all the POs, key personnels of the operation teams, one designer, QA leader, and HR to join us in KH. The first time KH is no wild wild west anymore. We may be wild but we are no longer a deserted place where one has to memorize hard enough to bring up in a conversation.

KKStar team logo

I have prepared myself with some worse case scenarios. After all, all that it counts for algorithm is computation of Big-O, the worst-case scenario. As proud engineers, we calculate for the worst.

The first bad thing that could happen would be people spent too much time eating lunch. Officially, CMS v2 brainstorming event started right after lunch. Time was tightly planned with each session precisely scheduled. With possible delay in return from lunch, meeting might be strained off time and there goes worse-case scenario number one.

Apple team logo

In the first session, we would ask people to start drafting their ideas as individuals on post-it and stick it to the category where it belongs. I could almost foresee for those who has no prior experience with content management system, drafting individual ideas would be a conversation killer. With too many people wondering blankly on the side and our shy CMS team as sales representatives, the whole session would easily pass by in silence. There! I can see how this would end. The meeting died and the rumors passed around like this, KH is not a fun place. The team is boring. Worse-case scenario number Two!

I lost count of worse-case scenario after number two. It was all too depressing. So I crossed my fingers, waited for people to scatterly return from their lunch. At around 1:30, people have all returned from lunch satisfied and happy. Worse case scenario one pass!

Kiwi team logo

The first session, we named it “I have a dream session”. That is to say, if you do have a dream. From my point of view, if you do not know the existence of an Extera-Terrestrial, i.e. ET, would you even dream of it coming to you?

Albeit all the speculations and dramas that took place in my head, the first session went interestingly well. People were curious. They showed interests in the things unheard of. People were attentive. Lots of individual conversations went on with each category owner. By the end of the first session, every category had reached its sales target.

In the following session, three pre-chosen group owners played back-to-back scissors, paper, and rock to pick out members for each competing group. This would be one of high peaks of the day. Each group owner demonstrated their mottos before the game started. Each group was paired with a recorder who would not participate in any activity but serve as a neutral observer. Recorders would share what they have learned from observing interactions among group members the next day.

In the following session, three pre-chosen group owners played back-to-back scissors, paper, and rock to pick out members for each competing group. This would be one of high peaks of the day. Each group owner demonstrated their mottos before the game started. Each group was paired with a recorder who would not participate in any activity but serve as a neutral observer. Recorders would share what they have learned from observing interactions among group members the next day.

Proudly presented by Kiwi team.

First round of idea presentations, each team was able to present an idea with roughly 60 ~ 70 % of completion level. The idea itself was innovative and interesting. They are fresh but a bit immature. People were groaning at limited amount of time and resources that had prevented them from producing a perfect result. It was, however, deliberately designed. We had given the approach of this part of the event with deep considerations and decided to resemble real-world scenarios where you never get enough time and resource to do a job. However, for the times we made something unsatisfactory, we reflect and learn from our failures. It was from reflective experiences that we learn to do better each time.

Proudly presented by Apple team.

Brainstorming is an exploration and extraction of ideas deeply buried in our minds. It was through intense conversation and listening that the ideas are to be shaped into presentable forms. Almost every team picked on one or more ideas related to AI (artificial intelligence) or ML (machine learning), however nature of abstraction the ideas were. Ninety percent of the AI or ML ideas were unfortunately dropped after group discussion. AI or ML is something we got a hunch that tells us it is the future but we are probably not matured to the point to implement a product base on it.

Afternoon tea time was another highlight of the day. Fried chicken, fries, hot pressed toast and lots of cake.

Because we decided to split one discussion session into two, afternoon snack arrived exactly around the time after our first retrospective.

The second idea crafting session started after snack time. This is something of a bliss. In the original plan there was no break time at all due to our tight schedule. Albert, our brainstorming consultant thoughtfully introduced to us by Peter, mentioned it might stress people out without even a single break. I did not put too much thought into basic human needs. People really need a break as it turned out. By the end of first session, people were agitated and ready to do more but they are tired. We took around 30 mins break which end up a great result on the second session.

Proudly presented by kkStar team.

All three competing groups seemed ready to jump on the second chance to prove the excellence of their ideas by the end of 30-min break. In this round, group discussions were optimized. As it seemed, members of each group has obtained the mind of a best friend to each other. People simply turned telepathic.

At the end of second session, we have one group with two different implementations on two relatively distinct ideas. Two groups expanded further on their original thoughts. Since each group has to answer questions for their own implementations, it was clear that this time, speakers were more well-prepared and sophisticated for their own topics.

We concluded the first day of the event with a retrospective of the day and arranged the morning time on the second day to announce the winner, decoration of the winning team, and a reflection initiated by three recorders from three groups.

Something we would always remember.

A perfect conclusion was tough. There are few options to initiate and conclude an event. We could lecture for lessons we learn, raise an open question, sing a song, ask people to sing a song, or provide another round of happy meal for satisfaction. Since Drake has fully regained his consciousness after a night of rest. He was able to engage into the lessons we learned with open questions at the end.

Crowning

More or less this event was a success of which I marked a success level around 75%. The lost of 25% depends on the level of impact this event has brought upon people. The result would be a continuous counting then.

Posted in Events, KKStream | Leave a comment

MPEG-DASH 開源專案

據說,在參加了某一場 AWS Taiwan 舉辦的活動後,
我們曾對著一群人,豪邁的說出了「我們來在台灣辦例行性的 streaming workshop」吧!
然後,與大部分的政客一樣,只有發聲,沒有行動,遲遲沒有任何動作。
當時一時興起,以為,只要有人先說出口,
就自然會有其它人出來接棒,執行。當然,我也會全力協助與參與…

但就像 g0v 的座右銘

「不要問為何沒有人做這個,先承認你就是『沒有人』」。
因為,「沒有人」是萬能的。

過了快一年,似乎沒有因此產生什麼變化,
想說先做點什麼一個人可以做的,簡單一點的事好了。
於是有了這麼一篇,從分享簡單而公開的資訊開始。
夾雜點個人觀點,然後期待有人跳出來指正我哪寫錯了,
或是提供 patch ;D

MPEG-DASH 起始於 2010 年,2011 年有了草案。
同年,成為國際標準。於 2012 年以 ISO/IEC 23009-1:2012 的型式發佈。
這樣的一個標準,因為 video streaming 成了新世界的載體,漸漸成為基礎建設。
於是有不少開源專案:

Continue reading

Posted in KKV, Streaming, Video | Tagged , , , | Leave a comment