Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weekly/58 for 2016/11/09 #5

Closed
2 of 11 tasks
arrowrowe opened this issue Nov 4, 2016 · 11 comments
Closed
2 of 11 tasks

Weekly/58 for 2016/11/09 #5

arrowrowe opened this issue Nov 4, 2016 · 11 comments
Assignees

Comments

@arrowrowe
Copy link
Member

arrowrowe commented Nov 4, 2016

2016/11/09, 第十四循环第一次, 总第五十八期 -> @dyweb/mos

投稿:

Web

MOS

注: 从第十四循环起, 计划用 dyweb/mos#1 提出的自动化工具生成周报.

@arrowrowe arrowrowe self-assigned this Nov 4, 2016
@arrowrowe
Copy link
Member Author

arrowrowe commented Nov 4, 2016

投稿模板: (评论放在 yaml 块之后)

```yaml
name: 
link: 
description: 
quote: 
cc: 
```

详细规范请参考 dyweb/mos#1 (comment)

关于 YAML,

@arrowrowe
Copy link
Member Author

name: Awesome Perf Cpp
link: https://fenbf.github.io/AwesomePerfCpp/
description: a curated list of awesome C/C++ performance resources: talks, articles, books, libraries, tools libraries, sites. Inspired by awesome.
quote: 
cc: 

@arrowrowe
Copy link
Member Author

name: The Power of Ten
link: http://spinroot.com/p10/
description: 10 Rules for Writing Safety Critical Code
quote: |
    1. Restrict to simple control flow constructs.
    2. Give all loops a fixed upper-bound.
    3. Do not use dynamic memory allocation after initialization.
    4. Limit functions to no more than 60 lines of text.
    5. Use minimally two assertions per function on average.
    6. Declare data objects at the smallest possible level of scope.
    7. Check the return value of non-void functions, and check the validity of function parameters.
    8. Limit the use of the preprocessor to file inclusion and simple macros.
    9. Limit the use of pointers. Use no more than two levels of dereferencing per expression.
    10. Compile with all warnings enabled, and use one or more source code analyzers.
cc: ComMouse

@at15
Copy link
Member

at15 commented Nov 4, 2016

name: xxHash
linke: https://github.com/Cyan4973/xxHash/
description: extremely fast non-cryptographic hash algorithm

@at15
Copy link
Member

at15 commented Nov 5, 2016

name: Portainer
link: http://portainer.io/
description: a lightweight management UI which allows you to easily manage your Docker host or Swarm cluster
cc: gaocegege

@arrowrowe
Copy link
Member Author

name: RPyC
link: https://github.com/tomerfiliba/rpyc
description: Remote Python Call, a transparent library for symmetrical remote procedure calls, clustering, and distributed-computing.
quote: 
cc: mrmiywj

@arrowrowe
Copy link
Member Author

name: The Art of Command Line
link: https://github.com/jlevy/the-art-of-command-line
description: master the command line, in one page.
quote: 
cc: 

@arrowrowe
Copy link
Member Author

name: 10 principles for smooth web animations
link: https://blog.gyrosco.pe/smooth-css-animations-7d8ffc2c1d29
description: the complete guide to getting 60fps animations with CSS.
quote: 
cc: gaocegege LukeXuan

@at15
Copy link
Member

at15 commented Nov 8, 2016

name: css-architecture
link: https://github.com/jareware/css-architecture
description: 8 simple rules for a robust, scalable CSS architecture
cc: swaylq ComMouse

@arrowrowe
Copy link
Member Author

name: "Top-down learning path: Machine Learning for Software Engineers"
link: https://github.com/ZuzooVn/machine-learning-for-software-engineers
description: 
quote: |
    This is my multi-month study plan for going from mobile developer (self-taught, no CS degree) to machine learning engineer.

    My main goal was to find an approach to studying Machine Learning that is mainly hands-on and abstracts most of the math for the beginner. This approach is unconventional because it’s the top-down and results-first approach designed for software engineers.
cc: 

@arrowrowe
Copy link
Member Author

name: Benefits of using tmux - lessons from streamlining a development environment
link: https://blog.bugsnag.com/benefits-of-using-tmux/
description: 
quote: 
cc: 

@dyweb dyweb locked and limited conversation to collaborators Nov 10, 2016
@arrowrowe arrowrowe removed the working label Nov 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants