-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
22ffa72
commit 7114f05
Showing
93 changed files
with
2,239 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
.DS_Store |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
# 贡献指南 | ||
如果您有想要发表在本站的文章,可以通过以下两种方式来投稿。请注意,本站的所有内容将遵循 署名-非商业性使用-相同方式共享 4.0 国际 (CC BY-NC-SA 4.0) 协议公开,这意味着您的作品也会被采用该协议进行分享。 | ||
|
||
## 使用 Git | ||
您可以将您的文章以 Markdown 的格式提交到我们的 Git 仓库,遵循以下的步骤: | ||
|
||
打开我们的仓库并 Fork 我们的项目到您的 Github 账号。 | ||
```bash | ||
git clone https://github.com/NJUPT-SAST/sast-wiki-md | ||
cd ./info | ||
git remote add <YOUR-GITHUB-USERNAME> <YOUR FORKED URL> | ||
git checkout -b <BRANCH-NAME> | ||
``` | ||
注意!不要将您的改动直接放置在 main 分支。 | ||
|
||
将您的 Markdown 文稿放置在内容相关的目录内,并使之符合写作格式一节的要求。 如果您有需要插入的图片,我们建议您将其放置在 `assets/img/<YOUR-TITLE>` 内一并提交。 | ||
目录索引 | ||
|
||
``` | ||
git add --all | ||
git commit --message "YOUR COMMIT MESSAGE" | ||
git push --set-upstream <YOUR-GITHUB-USERNAME> <BRANCHNAME> | ||
``` | ||
|
||
提交信息格式可以为 add post: `<TITLE>` | ||
|
||
然后前往我们的仓库,提交 Pull Request | ||
|
||
我们会尽快处理您的请求,如果有什么不合理之处,也会在 Pull Request 的讨论区回复。 | ||
|
||
## 发送邮件 | ||
如果您不熟悉 Git 操作,也可以通过将您的文章发送到 SAST 邮箱 ([[email protected]](mailto:[email protected])) 来投稿。但是,我们建议您使用 Git 提交,以便更好地追踪和记录您的贡献。 | ||
|
||
# 其他贡献 | ||
如果您发现了本站的一些 Bug 和使用体验问题,也可以在 Github 仓库的 issue 区反馈,当然,您也可以直接提交一个 Pull Request,流程与投稿文章大致类似,只不过,您可能需要在本地设置 MkDocs 环境并充分测试您的改动。 | ||
|
||
如果您希望举办活动,参加科协以进一步贡献,也可以发送邮件深入咨询。 | ||
|
||
# 写作格式 | ||
我们推荐您下载合适的 Markdown 编辑器,如 Obsidian 或者 VSCode 并花些时间来学习一下 Markdown 的基本语法。 | ||
|
||
本站使用 MkDocs 进行驱动,因此,您需要将您的 Markdown 文件改动来符合解析要求。 | ||
|
||
将您的文章文件名改为 YYYY-MM-DD-TITLE 的格式 | ||
在您的文档开头添加元信息,具体格式为 | ||
```yaml | ||
--- | ||
draft: true | ||
date: 2023-01-31 | ||
categories: | ||
- Hello | ||
- World | ||
tags: | ||
- Foo | ||
- Bar | ||
authors: | ||
squidfunk: | ||
name: Max | ||
description: SASTer | ||
avatar: https://avatars.githubusercontent.com/u/60775796 | ||
--- | ||
``` | ||
其中 layout、 author 和 permalink 为必填项。如果您希望以您的文章开头作为摘要,请在合适的地方添加 `<!--more-->` 标签。 | ||
|
||
插入图片的格式为: `![DESCRIPTION](/assets/img/<TITLE>/<FILE-NAME>.png)`,并将相应图片移至该目录下。 | ||
其余与一般 Markdown 语法相同,本站支持插入行内和块级公式。 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# 这是什么? | ||
欢迎来到南京邮电大学大学生科学技术协会(以下简称 SAST)的信息公示站,在这里您可以寻找到: | ||
|
||
- 校科协的介绍 | ||
- SAST 成员和嘉宾撰写的技术博客,心得体会和其他文章 | ||
- 公开分享的讲义、资料和有价值的链接 | ||
- 南邮生活指南 | ||
|
||
本站的搭建离不开以下工具和开源项目的支持,在此一并鸣谢: | ||
|
||
- [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/) | ||
- [南邮黄页](https://github.com/Wonz5130/NJUPT-Yellow-Page) | ||
- [南科手册](https://sustech.online/surroundings/) | ||
|
||
# 贡献 | ||
如果你想贡献内容,请仔细阅读 [CONTRIBUTION.md](/contribution.html) | ||
|
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Empty file.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
document$.subscribe(({ body }) => { | ||
renderMathInElement(body, { | ||
delimiters: [ | ||
{ left: "$$", right: "$$", display: true }, | ||
{ left: "$", right: "$", display: false }, | ||
{ left: "\\(", right: "\\)", display: false }, | ||
{ left: "\\[", right: "\\]", display: true } | ||
], | ||
}) | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
window.MathJax = { | ||
tex: { | ||
inlineMath: [["\\(", "\\)"]], | ||
displayMath: [["\\[", "\\]"]], | ||
processEscapes: true, | ||
processEnvironments: true | ||
}, | ||
options: { | ||
ignoreHtmlClass: ".*|", | ||
processHtmlClass: "arithmatex" | ||
} | ||
}; | ||
|
||
document$.subscribe(() => { | ||
MathJax.typesetPromise() | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
authors: | ||
ChenKS: | ||
name: ChenKS | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
陈汤林: | ||
name: 陈汤林 | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
Offensive77: | ||
name: Offensive77 | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
Jisu-Woniu: | ||
name: Jisu-Woniu | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
linyuqi9: | ||
name: linyuqi9 | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
multicoloredstone: | ||
name: multicoloredstone | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
EnderHorror: | ||
name: EnderHorror | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
Brethland Yang: | ||
name: Brethland Yang | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
J.C: | ||
name: J.C | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
xjzsq: | ||
name: xjzsq | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL | ||
NONE: | ||
name: 匿名 | ||
description: SASTer | ||
avatar: https://aliyun.sastimg.mxte.cc/images/2023/12/17/QQ20220819164336a533d1c9c523e00b.th.jpg | ||
slug: url # Author profile slug | ||
url: https://wiki.sast.fun # Author website URL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
# 科协文章 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
--- | ||
title: JavaScript中的原型链以及this指向问题 | ||
date: 2020-07-10 | ||
authors: | ||
- ChenKS | ||
categories: | ||
- blog | ||
tags: JavaScript | ||
--- | ||
|
||
JavaScript本身是没有类继承的,但是我们又可以使用ES6中的`class`关键字来写一个类,它的底层实现是原型链。原型链的介绍在[MDN--原型链](https://developer.mozilla.org/zh-CN/docs/Web/JavaScript/Inheritance_and_the_prototype_chain)上的介绍已经很详细了,但我想分享一下我的理解,如果不正确的地方,欢迎指出。 | ||
|
||
<!--more--> | ||
|
||
|
||
|
||
## 什么是原型链 | ||
|
||
在chrome的devtool中,我们打印一个引用类型的变量时可以看到这个变量一般会有个`__proto__`属性。这个对应的就是这个变量的原型。每个引用类型的变量都会有其对应的原型,然后其对应的原型又有其对应的原型 ~~套娃警告⚠️~~ ,这样的一条链被称为原型链,最终`__proto__`会指向null。 | ||
|
||
![__proto__](../../assets/img/blog/javascript-prototype-chain/1.png) | ||
|
||
就以上图为例子,我们需要先了解两个事实。首先js中的数组也是一个对象,第二 js的数组通过下表访问数组元素时,本质上是使用了方括号表示法的属性访问器来获取对象的属性。 | ||
|
||
![__proto__](../../assets/img/blog/javascript-prototype-chain/2.png) | ||
|
||
可能会疑惑我们常用的js的push方法,没有出现在这里。这其实是没有问题的,当我们调用`a.push()`的时候,首先会查看对象`a`上是否有`push`方法,没有则继续查看其`__proto__`上是否有`push`方法,以此类推,直到`__proto__`为null时,说明a上不存在`push`,因而报错,对于其他引用类型的变量也是同样的道理。我们使用构造函数new一个新的对象时,新对象的`__proto__` 指向的就是这个构造函数的`prototype`。这样,我们将一个构造函数的`prototype`的`__proto__`指向另一个构造函数的`prototype`,就可以用js的原型链实现类的继承。 | ||
|
||
## js中的令人迷惑的this指向 | ||
|
||
js中的this指向和函数的调用方式有关,我们可以分为以下几种方式。 | ||
|
||
1. 当作为普通函数调用时,this指向的就是全局对象,这里的全局对象具体是什么,需要看运行环境。 | ||
|
||
2. 如果函数是作为对象的方法时,`this`指向的就是这个对象。 | ||
|
||
3. 如果函数是作为构造函数的话,那么this会指向这个`new`产生的新对象。 | ||
|
||
4. 除此之外还可以通过`call`,`apply`,`bind`这些方法来修改this的指向。 | ||
|
||
|
||
```javasc | ||
function func1(){ | ||
console.log(this); | ||
} | ||
const obj1 = { | ||
func:func1 | ||
} | ||
const person = { | ||
name:'chen' | ||
} | ||
func1(); // 函数作为普通函数调用 | ||
obj1.func(); // 函数作为对象的方法调用 | ||
const obj2 = new func1(); // 函数作为构造函数调用 | ||
func1.call(person); // 使用call来修改this指向 | ||
obj1.func.apply(person); // 使用apply来修改this指向 | ||
``` | ||
**建议跟着敲一遍代码,有助于理解** | ||
|
||
说到了this指向问题,不得不提一下`箭头函数`。`箭头函数`不仅仅是使函数的写法更加简短,箭头函数的this指向也与其他普通函数不同。箭头函数的this指向不会因为它的调用方式不同而不同,它的this指向的是定义函数处的this。 | ||
|
||
```javascript | ||
setTimeout(function(){ | ||
console.log(this); | ||
}) | ||
|
||
setTimeout(() => { | ||
console.log(this); | ||
}) | ||
``` | ||
|
||
|
||
|
||
## 结语 | ||
|
||
理解原型链和js中的this指向问题以及箭头函数的一些特性可以帮助自己在写代码时,少踩挺多坑的。相关的有意思的问题还有挺多的,也有一些安全方面的问题,像原型链污染之类的。 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
title: 关于 NJUPT Lambda 的一些小事 | ||
date: 2020-06-10 | ||
authors: | ||
- Brethland Yang | ||
categories: | ||
- blog | ||
tags: Lambda 琐记 | ||
--- | ||
|
||
NJUPT Lambda 的建立自有点子起大致也有一周年了,从本来一个不成熟的构想到确确实实有过活动举办和传承的一个科协小组,作为亲历者的我期间有很多感想和故事。今天就想和大家聊一聊这些小事。 | ||
|
||
<!--more--> | ||
|
||
## 从 Haskell 说起 | ||
|
||
Lambda 组的最初雏形来自于2019年初,一个试验性质的举措。在我大一第二学期,Copper 学长(姐)开设了 Haskell 组。科协的芳草地课堂历来有个不太好的特点,到了下半学年,由于人员的流失,前来参加活动的人也日渐减少。不仅仅是 Haskell 组,大部分其他活动也面临着这个问题。我们自知不是强校,有时也很难将层次拉的有多么高,将“内卷”做的有多么激烈,但是至少在校科协的活动中可以让大家收获点什么。当然这个人员流失的现象也可以从另一方面去解释:大家都慢慢找到自己真正想做的事情了。这就是另一番话题了。 | ||
|
||
我接触函数式编程和其他知识大致也是从大一下学期开始,被 Copper 各种推荐和许多讨论下,我渐渐从一头雾水到产生兴趣,从一开始的只是尝试一门“新语言”的娱乐心态,到抛弃之前的各种先入之见,以近乎朝圣者的虔诚重新进入计算机科学的大门。这种转变的重要性是显而易见的,它似乎也昭示着我将走上一条与之前截然不同的道路。 | ||
|
||
临近学期末,换届工作就要开始了。Haskell 组的建立只是个试验性质,当然谈不上继任者。但是基于上文所述的问题,如果在上学期就开始给新生讲授函数式编程和其他一些国内科班很少涉及到的知识,效果又会如何呢?一个理想的大学,应该给身处其中的人提供近乎无穷的不一样的道路选择,这在日益后现代和同质化的现在是难能可贵的。一开始争取的时候,我是抱着稍微妥协的计划,在后端组兼任的同时开展非正式 Lambda 组的活动,但之后的许多事情,包括我的个人原因和科协的变化,让 NJUPT Lambda 变成了现在的这个样子,不得不说是一个很好的开始。 | ||
|
||
## 分裂、缩减和扩大 | ||
|
||
Lambda 的建立还包含着我的另一个设想,即探索新形式的知识交互的可能性,以及将科协作为一个学术性社团对待的极限所在。关于在招新时讲述的 Lambda 组的活动形式,包括讨论和轻松的氛围,宽泛的主题等,一方面是来源于我未进大学前的理想,另一方面,也参照了诸如 ZJU Lambda 和 TUNA 等的经验,具体在实现时,也是抱着尽力的想法去努力的。 | ||
|
||
美好的设想往往赶不上现实的脚步。作为科协史上少数经历很多变故的一届,许多的计划都不再能拿过去的标准评判。现代信息网会让人人产生自己是特别的感觉,因此这种想法其实并不怎么准确,但就实际情况看来,摆着我们面前的问题主要有两个:软件研发中心的分裂和招新人数的缩减。这两件事可以说有着近乎一样的起因,也可以说代表着几乎一样的风向。 | ||
|
||
一个技术社团的氛围是十分重要的前提,尽管带来的可能也会是 Peer Pressure,但也正是这种压力驱使着人们进步。营造氛围的需求使得技术团体面临着一个难题:精英化的趋势和普及性宣传的责任。一个或许更大的探讨是:技术应该无门槛地被任何人获取吗?具有一定讽刺意味的是,就算是再怎么倡导这个命题的黑客团体和圈子,结构也有很大程度上是精英化的。现代科学已经到了一个极度专业化的时代,要理解整栋大厦的结构极其耗费心智。而我相信科协在某种程度上也具有这样的二律背反:小众化?抑或是大众化? | ||
|
||
更现实的问题可能是,资格化的自我认同是公开和平等很大的一个阻碍。我并不赞成将科协成员的身份作为自我的资本,相反,它更像是一张通往可能的资源和机会的入场券,而不是所谓的资格书。为此,Lambda 组将坚持无门槛和无界限的活动开展,不管是入门的知识介绍,还是有一定深度和创造意味的头脑风暴,沙龙,我们都会试着去开拓。这也是科协面向未来的扩大化举措,也是“开源平等”的具体体现。 | ||
|
||
## 天翻地覆 | ||
|
||
接近第二学期的尾声,是时候来给本学期的 Lambda 组下个结论了。 | ||
|
||
本来将是重心的2020年上半年,因为诸多不愉快的事情而成为了不尽如人意的半年。本想作为在 NJUPT 完成的最后一件事,然后将其好好地交给他人的设想也消逝干净了。当然这不仅仅是 Lambda 组的问题,自我愧疚也无法解决问题。毋宁说,事后揽责反而会是自负的表现。 | ||
|
||
大疫情流行下我试着整理心绪,理解是什么出了问题,接下来该怎么办。事实上,在这种非日常下我们却获得了近乎无限的日常,这半年或许是最有可能做出改变,尝试新事物和找到可能性的半年。这段时间我也试着参与和体验了一次(可能还会有多次)的小圈子中的“读书会”,并希冀以之为基础在 Lambda 组织一次真正的沙龙。我希望在暑假我们会有一些活动的开展,无关于可能的身份认同,或是拘谨的自我胆怯,我们希望更多的人能参与进来,让 NJUPT Lambda 真正成为 NJUPT 的 Lambda。 | ||
|
||
群星里将人类定义为具有理想本心的种族,那么相对应的,NJUPT Lambda 的理想本心是什么?我们认为,每个人都有平等的获知和接触计算机科学和技术的权利,并为函数式编程和计算机科学知识的普及做出不懈努力。 | ||
|
||
那么,新的一年也希望能多多关照了! | ||
|
Oops, something went wrong.