Skip to main content

Posts

這裡當作個人雜記跟讀書心得

最近發生太多事情,但其實有些沒有記錄下來,有點可惜。 第一、就是我他媽克服了中年危機,然後我他媽成長了好多,我看事情的洞見變得更深,我好喜歡這樣的自己。 第二、看完書不寫心得或紀錄真的會忘記,但看書當下的學習感與快樂,仍然是我讀書第一優先;因為我也有本書有寫過心得,但仍然忘記看過,不過這讓我燃起要寫心得與筆記的習慣。應該會放在blogger,而不是個人網站,個人網站是拿來做形象用的。 最後、回來台灣大概兩週了,已經覺得社交能量燃燒殆盡,有點想要回去法國,台北這邊人高密度的交流,既讓人懷念又令我害怕,這種生活模式會令我想躺在床上什麼都不想做,很大的可能是因為很多互動是被迫的,等能自主時間時,就已經無法運作;所以或許我不是有憂鬱症,而是認知能量就那麼低。就像有時候開完線上會,那個時段我就無法工作一樣。
Recent posts

[Web] Using Code Block in Blogger

I have done some researching on how to use code blocks in blogger and I found this awesome tutorial article in Chinese. I tried the steps they provide, and it work perfectly. So I'm just gonna make the steps more clear with some screen shots! What you should do Go to  Prismjs.com and download both js and css files of the theme you like Paste the content of the css file to: Theme->Customise->Advanced->Add Css->Add custom CSS Wrap the content of prism.js with <script></script> Paste it to Layout->Sidebar->Add a Gadget->HTML/Javascript How to use when you write the article, go to html mode and paste the following dom. <pre><code class="language-javascript"> ... Your code here ... </code></pre> it will looks like this: ... Your code here ... and with some code content: let helloString='Hello World!'; console.log(helloString); console.log('Yoda!'); There ...

[Web] Building up Github pages

Before we started... This content was posted originally in my old GitHub pages blog site, but I've abandoned that site, so I post here again in English. I have to say, this post has saved me once when I tried to made another GitHub pages site for my friend, so I hope you find it useful too. Who's this article for? who...wants to have a blog in GitHub  who is not familiar with command line, neither wants to use it Windows users who's never heard of Jekyll、Bash、gem What happened to me? I got a laptop and a PC, both are Windows. After I saw some posts about building website with GitHub, I was so excited about it and tried to do it on my own. First on the GitHub Pages tutorial, they suggested using Jekyll; so without a doubt, I went to Jekyll to see what's on there. But with more tutorial steps, there showed up more stuff I'm not familiar with like Ruby or Ubuntu; and with some tools I tried to install, I encountered a few compatibility problems. Isn...

[Profolio] Winning List

Things you should know... This page lists all the items that a user has won. Users can access the page within buttons on Line Official Account channel. The page is based on a service of Line called LIFF, which is basically an internal browser of Line. Users in this page are able to see items they have earned with interactive activities. Items are shown in the list if it's outdated, redeemed, or still active. I have designed the UI initially and put it in practice, also the back-end behind the page. Sneak peek Customer Practice This is still used by some of my client with some adjustments. (But currently I have not won anything...)

[Profolio] Interactive Image Panel

Things you should know... These components are based on Angular 6. After inserting a photo, users can insert some new blocks, which allow them to resize and move freely. While the block is moved or changed size, the width, height, and positions have to be shown in corresponding areas. While any block is clicked, the block should be high-lightened and showed its information, which are free to change manually also. Sneak peek The UI however wasn't designed by me, I am responsible for all the front-end functions and make it work!

[Book] Being Geek 晉身怪傑

心得 這本書不愧是「Geek」所寫,看完後可以放心地說我不是Geek!因為大部分的內容對我而言都沒有實質幫助,書中許多章節對我來說多是廢話。本書也沒有嚴謹的架構,應是整理過去部落格或是定期文章而成,許多內容頗有「硬」寫之感。 以管理群像這個主題(P88)為例,列舉了五種管理人(質問者、修先排序者、隨機者、提問者、敵人),分別對他們的特質、開會習慣做分析,顯然低估了人的豐富性,並且這樣五個的分類也只是依據作者喜好而分。 當然像這樣的窮舉,偶爾還是有些提點作用,只是以整本書與有幫助的部分比例來說,實在懸殊,我會推薦資訊人 避開 這本書,因為有更多值得參考「軟技巧」類的書,例如:軟技能代碼之外的生存指南 (Soft Skills : The software developer's life manual)或是程序員思維修煉(Pragmatic Thinking and Learning: Refactor Your Wetware ( Pragmatic Programmers ))。 筆記 (以下內容都有改寫) P85 講真話: 是不是我們在跟人對話時,即使很順利,仍忽略掉了什麼,可以談些什麼話題,即使微不足道都能令這段對話更有價值?可能是對同事、朋友或家人(尤其父母)。 在停止找藉口後,我們有沒有沒採用那些腦中一閃而過更有價值的話題?而不是說些廢話。每次開口說話時, 我們都有機會創造某些東西 ,要由這個角度切入,而不是誰是誰非那種情緒性的藉口。 P105 嘆息(本書最棒的章節): 當危機出現時,如果缺少溝通的平台,會使困惑誕生於團隊,人們可能: 1. 缺乏有力資訊下,腦補資訊空洞,試圖建立看似有結構的東西,但通常只會讓情況更混亂。 2. 雖然成員彼此不停討論危機,但並沒有創造新的內容,只是對危機的反雛;如果只是討論危機如何如何, 不過是減輕內心的焦慮 ,對危機處理沒有任何幫助。 3. 缺乏溝通,所有人又都要知道所有事情,導致大家想:我要知道一切,並且我也有特別的東西想加進去,而且最好能讓我這樣做! 作者提出三種會議解決危機: 1. 與下屬1:1會議:你在擔心什麼?我擔心的是這些。討論...(即使你跟工作夥伴再熟,1:1會議都不該被省略) 2. 工作人員會議:我們在何處?我們要做什麼?我們要怎麼做。專案...

[Book]臣服實驗:從隱居者到上市公司執行長,放手讓生命掌舵的旅程

概念 Going with the flow;不依自己的「喜好」做決定,原則上當有機會呈獻時就把握。 批評 如果作者的故事都屬實,作者應該是個天賦異稟的聰明人,很多人在完成學業上,即使努力了也不見得能完成;但我認為整本書最讓人詬病的地方在於,作者判斷生命是否豐盛的方法,仍屬俗世,判斷這個「Going with the flow」很棒,是因為他事業順利、靈性社團擴張、官司勝訴? 這些我們姑且稱為「奇蹟」好了,但這難道真是好的靈性態度嗎?難道不應該欣然接受所有成敗嗎?而不是強調成功,並以此為基準。 另外,生存者偏差也完全能套用在這樣的情境中;如果一個完全以此心態過活的人,活得沒那麼好,此時是否又會對他說一切都是試煉呢?