Skip to content

Commit

Permalink
clean up
Browse files Browse the repository at this point in the history
  • Loading branch information
Huxpro committed Aug 15, 2022
1 parent f69d56d commit f9ae805
Show file tree
Hide file tree
Showing 35 changed files with 517 additions and 190 deletions.
4 changes: 2 additions & 2 deletions _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Hux Blog
SEOTitle: 黄玄的博客 | Hux Blog
header-img: img/home-bg.jpg
email: [email protected]
description: "代码是诗也是 rap,别怕程序员有 swag | 这里是 @Hux黄玄 的个人博客,与你一起发现更大的世界"
description: "这里是 @Hux黄玄 的个人博客,与你一起发现更大的世界 | 要做一个有 swag 的程序员"
keyword: "黄玄, Hux黄玄, Hux, 鬼栈, huxpro, @huxpro, 黄玄的博客, Hux Blog, 博客, 个人网站, 互联网, Web, JavaScript, React, React Native, 前端, 设计"
url: "https://huangxuan.me" # your host, for absolute URL
baseurl: "" # for example, '/blog' if your blog hosted on 'host/blog'
Expand Down Expand Up @@ -74,7 +74,7 @@ ga_domain: huangxuan.me

# Sidebar settings
sidebar: true # whether or not using Sidebar.
sidebar-about-description: "代码是诗也是 rap<br>别怕程序员有 swag"
sidebar-about-description: "要做一个有 swag 的程序员 <br> React Team @ Meta"
sidebar-avatar: https://github.com/Huxpro.png # use absolute URL, seeing it's used in both `/` and `/about/`

# Featured Tags
Expand Down
2 changes: 1 addition & 1 deletion _includes/about/zh.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Hey,我是黄玄(a.k.a. Hux, _@huxpro_),一个略懂计算机科学与
现为 <del>Facebook</del> Meta 签约软件工程师,就职于开源技术<del>网红</del>团队 [React](https://beta.reactjs.org/community/meet-the-team#react-core),曾参与 [Hermes JavaScript 引擎](https://hermesengine.dev/)[ReasonML](https://reasonml.github.io/) (现 [ReScript](https://rescript-lang.org/)),以及 [Reality Labs](https://tech.fb.com/ar-vr/) 某保密项目等。在国内期间,曾被招募为阿里巴巴 · [阿里旅行(飞猪)](http://alitrip.com)· 前端工程师、微影时代 · 微票儿 · 前端基础设施工程团队负责人、[饿了么](https://ele.me/) · 大前端团队 · [PWA 顾问](https://medium.com/elemefe/upgrading-ele-me-to-progressive-web-app-2a446832e509) 等。


目前的物理活动范围主要在美帝纽约与硅谷,也想当个数字游<del>民</del>侠。虚拟分身日常出没于[博客](https://huangxuan.me)[微博](https://weibo.com/huxpro)[知乎](https://www.zhihu.com/people/huxpro/pins/posts)[B站](https://space.bilibili.com/43271611)[Instagram](https://www.instagram.com/huxpro/)[推特](https://twitter.com/Huxpro/)[Github](https://github.com/huxpro) 等。
目前的物理活动范围主要在美帝纽约与硅谷,也想当个数字游<del>民</del>侠。虚拟分身日常出没于[微博](https://weibo.com/huxpro)[知乎](https://www.zhihu.com/people/huxpro/pins/posts)[B站](https://space.bilibili.com/43271611)[Instagram](https://www.instagram.com/huxpro/)[推特](https://twitter.com/Huxpro/)[Github](https://github.com/huxpro) 等。

##### 演讲与分享

Expand Down
3 changes: 0 additions & 3 deletions _posts/2014-01-29-hello-2015.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,6 @@ author: "Hux"
header-img: "img/post-bg-2015.jpg"
catalog: true
tags:
- 生活
- Meta
---

Expand Down Expand Up @@ -73,5 +72,3 @@ Theme 的 CSS 是基于 Bootstrap 定制的,看得不爽的地方直接在 Les
如果你恰好逛到了这里,希望你也能喜欢这个博客主题。

—— Hux 后记于 2015.10


2 changes: 1 addition & 1 deletion _posts/2014-08-16-miui6.markdown
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "「知乎」如何评价 MIUI 6?"
title: "如何评价 MIUI 6?"
date: 2014-08-16 12:00:00
author: "Hux"
header-img: "img/post-bg-miui6.jpg"
Expand Down
8 changes: 4 additions & 4 deletions _posts/2014-09-04-is-pure-android-better.markdown
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "「知乎」对中国用户而言,Pure Android 是否比 MIUI 或 Flyme 体验更好?"
title: "对中国用户而言,Pure Android 是否比 MIUI 或 Flyme 体验更好?"
subtitle: ""
date: 2014-09-04 12:00:00
author: "Hux"
Expand All @@ -20,9 +20,9 @@ tags:
<br><b>毕竟是回答问题嘛,先给一个明确的答案</b>:
<br>
<br><b>否。(</b><b>对中国用户而言,Pure Android 并不比 MIUI 或 Flyme 体验更好。</b><b>)</b>

<p>从下面「 居然比关注数还多」的回答中,就可以看出大家都是急于站队的样子:</p>

<ul>
<li>Google Service!翻墙很轻松好吗!Geek站过来,有品味绝逼原生阿。</li>
<li>没用过Pure,国内Google能用!?本地化多重要,易用果断MIUI/Flyme 啊!(咦 米粉和魅粉居然在一致对外上达成了共识)</li>
Expand All @@ -35,7 +35,7 @@ tags:
<br>

<p>先说好理解的:</p>

<ul>
<li><b>为什么 Geek 用户 都爱使用Pure Android?:</b>
</li>
Expand Down
3 changes: 1 addition & 2 deletions _posts/2014-10-01-why-alibaba-ux-sucks.markdown
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "「知乎」为什么阿里系软件体验都不好?"
title: "为什么阿里系软件体验都不好?"
subtitle: "或许这就是所谓的企业 DNA "
date: 2014-10-1 12:00:00
author: "Hux"
Expand Down Expand Up @@ -66,4 +66,3 @@ tags:
<br>
<br>
</div>

4 changes: 2 additions & 2 deletions _posts/2014-11-20-responsive-web-design.markdown
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
layout: post
title: "「知乎」你们觉得响应式好呢,还是手机和PC端分开来写?"
title: "你们觉得响应式好呢,还是手机和PC端分开来写?"
date: 2014-11-20 12:00:00
author: "Hux"
header-img: "img/post-bg-rwd.jpg"
tags:
- 知乎
- Web
- Web
---

> 这篇文章转载自[我在知乎上的回答](http://www.zhihu.com/question/25836425/answer/31564174)
Expand Down
3 changes: 1 addition & 2 deletions _posts/2014-12-13-wechat-block-kuaidi.markdown
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "「知乎」如何看待微信屏蔽快的打车事件?"
title: "如何看待微信屏蔽快的打车事件?"
subtitle: "恰有小感。"
date: 2014-12-13
author: "Hux"
Expand Down Expand Up @@ -68,4 +68,3 @@ tags:
<br>
<br>
</div>

7 changes: 2 additions & 5 deletions _posts/2015-03-10-apple-event-2015.markdown
Original file line number Diff line number Diff line change
@@ -1,9 +1,10 @@
---
layout: post
title: "「知乎」如何评价 2015 年 3 月 9 日 Apple 春季发布会?"
title: "如何评价 2015 年 3 月 9 日 Apple 春季发布会?"
subtitle: "聊聊科技与新式奢侈品"
date: 2015-03-10 12:00:00
author: "Hux"
hidden: true
header-img: "img/post-bg-apple-event-2015.jpg"
tags:
- 知乎
Expand Down Expand Up @@ -56,7 +57,3 @@ tags:
<br>
<br>有人说 Apple Watch 简直是 Jony Ive 这个一心向往做奢侈品设计的天才将 Apple 引入了歧途里,而我却觉得<b>科技与时尚的结合为何就不是一件美丽的事情?</b>
</div>




14 changes: 7 additions & 7 deletions _posts/2015-03-31-e2e_user_scenarios.markdown
Original file line number Diff line number Diff line change
@@ -1,30 +1,31 @@
---
layout: post
title: "Definition of End to End User Scenarios"
date: 2015-03-31
date: 2015-03-31
author: "Hux"
header-img: "img/post-bg-e2e-ux.jpg"
published: false
lang: en
tags:
- UX/UI
- 🇬🇧
- En
---


### End to end?

To explain what is "End to End User Scenarios", we should first explain what is "End to End", which we can called E2E for short.

There is not a very clear definition of E2E in wiki.<sup>[[1]](#ref1)</sup> In dictionary, it can both refer to "throughout" or "the end of one object connect to the end of another object".<sup>[[2]](#ref2)</sup>
There is not a very clear definition of E2E in wiki.<sup>[[1]](#ref1)</sup> In dictionary, it can both refer to "throughout" or "the end of one object connect to the end of another object".<sup>[[2]](#ref2)</sup>

E2E is usually used in Logistics, Computer Networking and Software Testing. For example, End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish. The entire application is tested in a real-world scenario.

So in my view, the most essential part of E2E is that **we must focus on the entire process, including every parts in a use case.**


### User Scenarios!
### User Scenarios!

User scenarios is a common term in UX Design,<sup>[[3]](#ref3)</sup><sup>[[4]](#ref4)</sup> which expands upon our persona and user stories by including details. It told us about users' motivation, goals and actions on our products.
User scenarios is a common term in UX Design,<sup>[[3]](#ref3)</sup><sup>[[4]](#ref4)</sup> which expands upon our persona and user stories by including details. It told us about users' motivation, goals and actions on our products.

To make it better, there comes **"End to End User Scenarios", not just tell a fragment of users' activities, but pay attention to the entire process the user undergoes.**

Expand All @@ -39,7 +40,7 @@ We just put the two terms together and give it a explanation, but it can be fart

* **Extend the scope**

There is a interesting instance <sup>[[5]](#ref5)</sup> told that sometimes we are already satisfy of our designed UX, but if we look beyond the both ends of the designed experience by extending the scope of the timeline before and after… we may sadly realize that it’s a complete car crash outside the scope of the designed experience...
There is a interesting instance <sup>[[5]](#ref5)</sup> told that sometimes we are already satisfy of our designed UX, but if we look beyond the both ends of the designed experience by extending the scope of the timeline before and after… we may sadly realize that it’s a complete car crash outside the scope of the designed experience...

Try to extend the scope and consider more, so can we design a much broader experience for our user.

Expand Down Expand Up @@ -75,4 +76,3 @@ That's all, thank you.
4.<a id="ref4">[How to Create User Stories, Scenarios, and Cases](https://www.newfangled.com/how-to-tell-the-users-story/)</a>

5.<a id="ref5">[Designing end-to-end user experiences. | 90 Percent Of Everything](http://www.90percentofeverything.com/2008/11/11/designing-end-to-end-user-experiences/)</a>

4 changes: 2 additions & 2 deletions _posts/2015-05-11-see-u-ali.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ date: 2015-05-11
author: "Hux"
header-img: "img/post-bg-see-u-ali.jpg"
tags:
- 生活
- Meta
- 阿里
---

Expand Down Expand Up @@ -101,4 +101,4 @@ Hi all

**Hey,这里是编号 79717**

![img](/img/in-post/post-c-u-ali-079717.png)
![img](/img/in-post/post-c-u-ali-079717.png)
5 changes: 3 additions & 2 deletions _posts/2015-05-25-js-module-loader.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ date: 2015-05-25
author: "Hux"
header-img: "img/post-bg-js-module.jpg"
catalog: true
published: false
tags:
- 笔记
- Web
Expand Down Expand Up @@ -101,7 +102,7 @@ var Employee = require("types/Employee");

function Programmer (){
//do something
}
}

Programmer.prototype = new Employee();

Expand Down Expand Up @@ -270,7 +271,7 @@ Sea.js 借鉴了 RequireJS 的不少东西,比如将 FlyScript 中的 module.d
**虽然两者目前都兼容各种风格,但其底层原理并不相同,从其分别推荐的写法就可以看出两者背后原理的不同:**

1. 对于依赖的模块,AMD 是**提前执行**,CMD 是**懒执行**。(都是先加载)
* CMD 推崇**依赖就近**,AMD 推崇**依赖前置**
* CMD 推崇**依赖就近**,AMD 推崇**依赖前置**

看代码:

Expand Down
8 changes: 3 additions & 5 deletions _posts/2015-06-15-alitrip-strategy.markdown
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "聊聊「阿里旅行 · 去啊」—— 行业与战略 "
title: "聊聊「阿里旅行 · 去啊」"
subtitle: "聊聊在线旅行行业与老东家的产品思路"
date: 2015-06-15
author: "Hux"
Expand All @@ -10,8 +10,6 @@ tags:
- 产品
- 阿里
---
> 本篇为该系列第一篇 —— 行业与战略,让我们聊聊行业、战略与格局。

## 前言

Expand All @@ -27,7 +25,7 @@ O2O 领域已经有了非常多成功的案例:从最早的千团大战,到
* 地产: 二手房、租房
* 医疗、家电、教育、票务……

当然,还有我们的在线旅游行业,BAT 纷纷入局,盛况空前。
当然,还有我们的在线旅游行业,BAT 纷纷入局,盛况空前。


## 正文
Expand Down Expand Up @@ -113,7 +111,7 @@ Channel,即**渠道模式**。通过优化用户的体验路径,在用户和

**首先是切入时机太晚**

阿里其实 2010 年就开始做淘宝旅行了,一直划分在淘宝网下,由那时的淘宝北研(淘宝 UED 北京研发)团队负责,这个团队吸纳了大批雅虎中国的精英,技术水平相当高。
阿里其实 2010 年就开始做淘宝旅行了,一直划分在淘宝网下,由那时的淘宝北研(淘宝 UED 北京研发)团队负责,这个团队吸纳了大批雅虎中国的精英,技术水平相当高。
可是 2010 年才切入这个市场实在是太晚了,携程、去哪儿的口碑和用户习惯早都养成好几年了,没人会去你淘宝上搜航班酒店,你有大入口也没有用。

**二是资源倾斜不足**
Expand Down
11 changes: 2 additions & 9 deletions _posts/2015-10-28-how-designer-learn-fe.markdown
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
layout: post
title: "「知乎」设计师如何学习前端?"
title: "设计师如何学习前端?"
subtitle: "How designers learn front-end development?"
date: 2015-10-28 12:00:00
author: "Hux"
header-img: "img/home-bg-o.jpg"
tags:
- 知乎
- Web
- UX/UI
- UX/UI
---

> 这篇文章转载自[我在知乎上的回答](https://www.zhihu.com/question/21921588/answer/69680480),也被刊登于[优秀网页设计](http://www.uisdc.com/head-first-front-end)等多个网站上 ;)
Expand Down Expand Up @@ -187,10 +187,3 @@ $('.className').click(function(){
<br>
<br>
<br>咦,这个结尾怪怪的……







2 changes: 1 addition & 1 deletion _posts/2016-09-22-the-open-web.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ header-img: "img/post-bg-web.jpg"
header-mask: 0.4
tags:
- Web
- Wechat
- 微信
---

> 本文首发于我的知乎专栏 [The Little Programmer](https://zhuanlan.zhihu.com/p/22561084),转载请保留链接 ;)
Expand Down
4 changes: 2 additions & 2 deletions _posts/2017-01-09-wechat-miniapp-ux.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ header-img: ""
header-bg-css: "linear-gradient(to right, #24b94a, #38ef7d);"
tags:
- Web
- Wechat
- 微信
- UX/UI
---

Expand Down Expand Up @@ -136,4 +136,4 @@ tags:

「这不是我想要的未来。」

会是你们的吗?
会是你们的吗?
6 changes: 3 additions & 3 deletions _posts/2017-04-06-html-document.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: 「知乎」如何理解 <code>document</code> 对象是 <code>HTMLDocument</code> 的实例?
title: 如何理解 <code>document</code> 对象是 <code>HTMLDocument</code> 的实例?
subtitle: Why is <code>document</code> an instance of <code>HTMLDocument</code>?
author: "Hux"
header-style: text
Expand All @@ -26,7 +26,7 @@ document instanceof HTMLDocument // true
// document 的 [[prototype]] 指向 HTMLDocument 的原型
document.__proto__ === HTMLDocument.prototype // true

// HTMLDocument 伪类继承于 Document
// HTMLDocument 伪类继承于 Document
HTMLDocument.prototype instanceof Document // true
HTMLDocument.prototype.__proto__ === Document.prototype // true
```
Expand Down Expand Up @@ -60,4 +60,4 @@ Node.__proto__ == EventTarget

留一个课后作业,有兴趣的话可以看看 Document.prototype 与 HTMLDocument.prototype 里分别都有什么?在不同浏览器里都试试。

以上。
以上。
4 changes: 2 additions & 2 deletions _posts/2017-05-28-sw-precache.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ lang: en
tags:
- Web
- PWA
- 🇬🇧
- En
---

[_SW-Precache_](https://github.com/GoogleChrome/sw-precache) _is a great Service Worker tool from Google. It is a node module designed to be_ _integrated_ _into your build process and to generate a service worker for you._ _Though_ _you can use sw-precache out of the box, you might still wonder what happens under the hood. There you go, this article is written for you!_
Expand Down Expand Up @@ -253,4 +253,4 @@ BTW, if you are using HTML5 Application Cache before, sw-precache is really a pe
Sw-precache is just one of awesome tools that can help you build service worker. If you are planing to add some service worker power into your website, Don’t hesitate to checkout sw-toolbox, sw-helper (a new tool Google is working on) and many more from communities.
That’s all. Wish you enjoy!
That’s all. Wish you enjoy!
11 changes: 6 additions & 5 deletions _posts/2017-10-06-css-complaints.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
layout: post
title: "「知乎」为什么 CSS 这么难学?"
title: "为什么 CSS 这么难学?"
subtitle: "Why I dislike CSS as a programming language"
author: "Hux"
header-img: "img/post-bg-css.jpg"
Expand All @@ -10,16 +10,17 @@ header-mask: 0.4
tags:
- Web
- CSS
- 知乎
---

> 这篇文章转载自[我在知乎上的回答](https://www.zhihu.com/question/66167982/answer/240434582)
对我来说,CSS 难学以及烦人是因为它**「出乎我意料之外的复杂」**且让我觉得**「定位矛盾」**

[@方应杭](//www.zhihu.com/people/b90c7eb6d3d5a4e2ce453dd8ad377672) 老师的答案我赞了:CSS 的属性互不正交,大量的依赖与耦合难以记忆。

[@顾轶灵](//www.zhihu.com/people/596c0a5fdd9b36cea06bac348d418824) [@王成](//www.zhihu.com/people/c02ec74a44ee4a6784d002c33e293652) 说得也没错:CSS 的很多规则是贯彻整个体系的,而且都记在规范里了,是有规律的,你应该好好读文档而不是去瞎试。


**CSS是一门正儿八经的编程语言,请拿出你学C++或者Java的态度对待它**

Expand All @@ -36,7 +37,7 @@ tags:

这种不上不下的感觉就让我觉得很「矛盾」,你既没法把 CSS 当一个很简单的布局标记语言去使用,又没办法把它作为一个像样的编程语言去学习和使用。


在写 CSS 和 debug CSS 的时候我经常处在一种「MD 就这样吧反正下次还要改」和「MD 这里凭什么是这样的我要研究下」的精分状态,可是明明我写 CSS 最有成就感的时候是看到漂亮的 UI 啊。

以上。
以上。
Loading

0 comments on commit f9ae805

Please sign in to comment.