Thaddeus Jiang ThaddeusJiang

時雨堂のお手伝い募集

更新:	2024-01-21
作者:	@voluntas
バージョン:	2024.5
url:	https://voluntas.github.io/

ありがたいことにたくさんの応募をいただきましたので、一旦応募を締め切りました。

My tech interview flow

背景

为什么应聘我们公司？

有明确判断标准

bugfix of your own code
add feature of your own code

```mermaid
sequenceDiagram
    participant dotcom
    participant iframe
    participant viewscreen
    dotcom->>iframe: loads html w/ iframe url
    iframe->>viewscreen: request template
    viewscreen->>iframe: html & javascript
 iframe-&gt;&gt;dotcom: iframe ready

Configuring Jest Tests in GitLab CI

1. Add GitLab CI configuration file in the root

In the root of your project, add .gitlab-ci.yml with the configuration below.

image: node:latest

stages:

How to write a Twitter link in Markdown


[![Twitter URL](https://img.shields.io/twitter/url/https/twitter.com/bukotsunikki.svg?style=social&label=Follow%20%40bukotsunikki)](https://twitter.com/bukotsunikki)

author

恢复上一个关闭的窗口 cmd+shift+t
跳转到地址栏 cmd+l
切换 tab ctrl + tab

This API was removed in React 17

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

	(ns defclass.test-framework)

	(def all-test (atom {}))
	(def ^:dynamic test true)

	(defmacro is [expr]
	`(let [result# ~expr]
	(when-not result#
	(set! test false)
	(printf "FAILED: %s%n" '~expr))))

	const defaultProps = {
	editable: {
	name: true,
	age: true,
	}
	}

	<Card /> // ok
	<Card editable={{ name: false }} /> // NG, because you lose `editable.age`