[B! documentation] hiyangã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

hiyang id:hiyang

documentationã«é–¢ã™ã‚‹hiyangã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (10)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

ã‚¨ã‚¯ã‚»ãƒ«ã§æ‰‹é †æ›¸ã‚’ä½œã‚‹ã®ã¯ãã£ã¨ã‚„ã‚ãŸæ–¹ãŒã„ã„ - Qiita
Deleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article? è¿½è¨˜(2017-01-05) ã€Œã‚¨ã‚¯ã‚»ãƒ«ã€€æ‰‹é †æ›¸ã€ã§ã‚°ã‚°ã£ãŸã‚‰ä¸Šã®æ–¹ã«ãã‚‹ã‚ˆã†ã«ãªã£ãŸã®ã§ã™ãŒã€ãã®æ¤œç´¢çµæžœãƒšãƒ¼ã‚¸ã«ã¯æ¥å‹™æ‰‹é †æ›¸ã‚’ã‚¨ã‚¯ã‚»ãƒ«ã§ä½œã‚‹ã¨ã‹ãã†ã„ã†ã®ãŒã‚ã‚Šã€ãªã‹ãªã‹ã‚«ã‚ªã‚¹ã§ã™ã€‚ ã‚ã¨ã‹ã‚‰è¦‹ã‚‹ã¨ä¸»èªžãŒå¤§ãã„æ°—ãŒã—ãŸã®ã§ã€ã™ã“ã—è£œè¶³ã‚’ã„ã‚Œã¾ã™ã€‚ã‚ãã¾ã§ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢æ¥ç•Œã§ã€ç‰¹ã«ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚„ã€ã‚µãƒ¼ãƒã®ç’°å¢ƒæ§‹ç¯‰ãªã©ã®æ‰‹é †æ›¸ã«ã¯ã‚¨ã‚¯ã‚»ãƒ«ã¯ä¸å‘ããªã®ã§ã¯ã€ã¨ã„ã†å®Ÿä½“é¨“ã«åŸºã¥ã„ãŸãŠè©±ã§ã™ã€‚ ã‚ã‚‹è£½å“ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ‰‹é †æ›¸ã‚’ä½œã‚‹ã“ã¨ã«ãªã‚Šã€å‚è€ƒè³‡æ–™ã¨ã—ã¦éŽåŽ»ã®æ¡ˆä»¶ã§ä½œã£ãŸã‚‚ã®ã‚’ã‚‚ã‚‰ã£ãŸã®ã ãŒã€ãã‚Œã¯ã‚¨ã‚¯ã‚»ãƒ«ãƒ•ã‚¡ã‚¤ãƒ«ã ã£ãŸã€‚ ã©ã†ã„ã†
hiyang 2016/03/25
æ›¸ãæ°—ãŒãªã„ã‹ã‚‰ç§˜ä¼ã®Excelæ‰‹é †æ›¸ã‚’ãƒ†ã‚ãƒˆãƒ¼ã«ã‚³ãƒ”ãƒ¼ã™ã‚‹ã®ã§ã¯ãªã„ã‹ãªã€‚ã¾ã¨ã‚‚ã«æ–‡æ›¸ä½œæˆã™ã‚‹æ°—ãŒã‚ã‚Œã°ãã‚‚ãã‚‚Excelã‚’é¸ã³ã™ã‚‰ã—ãªã„ã¨æ€ã†ã€‚

documentation
ãƒªãƒ³ã‚¯
API Blueprint | API Blueprint
API Blueprint. A powerful high-level API description language for web APIs. API Blueprint is simple and accessible to everybody involved in the API lifecycle. Its syntax is concise yet expressive. With API Blueprint you can quickly design and prototype APIs to be created or document and test already deployed mission-critical APIs. Tutorial Tools section Focused on Collaboration API Blueprint is bu
hiyang 2015/02/10
rest

documentation
ãƒªãƒ³ã‚¯
Promiseæœ¬ã§å–ã‚Šçµ„ã‚“ã é›»åæ›¸ç±ã®é–‹ç™ºãƒ„ãƒ¼ãƒ«ã€CIã€ç¶™ç¶šçš„ãƒªãƒªãƒ¼ã‚¹ã«ã¤ã„ã¦
Promiseæœ¬ã®å–ã‚Šçµ„ã¿ JavaScript Promiseã®æœ¬ã®é–‹ç™ºã§å–ã‚Šçµ„ã‚“ã äº‹ã¨å–ã‚Šçµ„ã‚“ã§ãŠãã¹ã(è€ƒæ…®ã—ã¦ãŠãã¹ã)ã ã£ãŸã“ã¨ã«ã¤ã„ã¦ã®ãƒ¡ãƒ¢æ›¸ã æŠ€è¡“æ›¸ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªæ§‹æˆã¨ã‹å‚è€ƒã«ãªã‚‹ã‚‚ã®ãŒã‚ã‚“ã¾ã‚Šãªãã¦é©å½“ã«ä½œã£ãŸã®ã§ã€ãã®è¾ºã‚’æ•´ç†ã‚’ã—ãŸã„ç›®çš„ã§æ›¸ã„ã¦ã¾ã™ã€‚ ã¯ã˜ã‚ã« ã“ã“ã§æ›¸ã„ãŸPromiseæœ¬ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªæ§‹æˆã‚„CIã€ãƒ†ã‚¹ãƒˆæ‰‹æ³•ã€ä½¿ã£ãŸãƒ„ãƒ¼ãƒ«ãªã©ã«ã¤ã„ã¦ã¯ä»¥ä¸‹ã«å¤§ä½“æ›¸ã„ã¦ã‚ã‚Šã¾ã™ã€‚ JavaScript Promiseã®æœ¬ ä»˜éŒ² ä¸Šè¨˜ã®ä»˜éŒ²ã®ã‚½ãƒ¼ã‚¹ : promises-book/Appendix-Note at master Â· azu/promises-book promises-book/CONTRIBUTING.md at master Â· azu/promises-book ãªã®ã§ã€çµæ§‹çœã„ã¦æ›¸ã„ã¦ã‚‹ã®ã§ã¡ã‚ƒã‚“ã¨è¦‹ãŸã„äººã¯ä»˜éŒ²ã¨ã‹ã®æ–¹ã‚’è¦‹ã¦ä¸‹ã•ã„ã€‚ å¾Œã€æ›¸ç±ã®æ–‡
hiyang 2015/01/07
documentation
ãƒªãƒ³ã‚¯
jax-doclets
This is pre-release software, please bear with it. This book is produced by the Wikbook tool. Wikbook is an open source project for converting wiki files into a set of docbook files.
hiyang 2014/09/22
jax-rs

rest

java

documentation
ãƒªãƒ³ã‚¯
tbaggery - A Note About Git Commit Messages
19 Apr 2008 I want to take a moment to elaborate on what makes a well formed commit message. I think the best practices for commit message formatting is one of the little details that makes Git great. Understandably, some of the first commits to rails.git have messages of the really-long-line variety, and I want to expand on why this is a poor practice. Hereâ€™s a model Git commit message: Capitaliz
hiyang 2014/07/28
documentation

communication

scm

.inbox
ãƒªãƒ³ã‚¯
language agnostic - How to write a good README - Stack Overflow
As others have noted, README should be simple and short, but a good README can save time especially if it's for something like command-line parameter parsing library. Here's what I think it should include: name of the projects and all sub-modules and libraries (sometimes they are named different and very confusing to new users) descriptions of all the project, and all sub-modules and libraries 5-l
hiyang 2014/04/30
README

documentation
ãƒªãƒ³ã‚¯
Asciidoctor | A fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML5, DocBook, PDF, and other formats.
A fast text processor & publishing toolchain for converting AsciiDoc to HTML5, DocBook & more. = Hello, AsciiDoc! Doc Writer <[email protected]> An introduction to http://asciidoc.org[AsciiDoc]. == First Section * it em 1 * it em 2 [source,ruby] puts "Hello, World!" Asciidoctor is a fast, open source, Ruby-based text processor for parsing AsciiDocÂ® into a document model and converting it to output for
hiyang 2013/04/10
documentation
ãƒªãƒ³ã‚¯
GitHub - kmuto/review: Re:VIEW is flexible document format/conversion system
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
hiyang 2013/03/21
é›»åæ›¸ç±

documentation
ãƒªãƒ³ã‚¯
Javadoc ã®æ›¸ãæ–¹ - ã‚¤ãƒˆã‚¦ ã‚¢ã‚¹ã‚« blog
ã¿ãªã•ã‚“ã€Javadoc æ›¸ã„ã¦ã¾ã™ã‹ï¼Ÿã€€Javadoc ã¯ã€ŒAPI ãƒ‰ã‚ãƒ¥ãƒ¡ãƒ³ãƒˆã€ã¨è¨€ã‚ã‚Œã‚‹ã“ã¨ãŒå¤šã„ã‚ˆã†ã«ã€ä¸»ã«ãƒ©ã‚¤ãƒ–ãƒ©ãƒªçš„ãªãƒ—ãƒã‚°ãƒ©ãƒ ã§æ›¸ã„ã¦ã“ãã®ã‚‚ã®ã ã¨æ€ã£ã¦ã„ã‚‹æ–¹ã‚‚ã„ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ã€‚ã—ã‹ã—ãªãŒã‚‰ã€ä»•æ§˜æ›¸ã‚’ Word ã‚„ Excelï¼ˆç¬‘ï¼‰ã§åˆ¥é€”ä½œã‚‹ã¨ã€ãƒ—ãƒã‚°ãƒ©ãƒ ã¨ä»•æ§˜æ›¸ã®åŒæœŸãŒã¨ã‚Œã¦ãªã„ã¨ã„ã†ã¯ã‚ã«é™¥ã‚Šæ˜“ããªã‚Šã¾ã™ã®ã§ã€Javadoc ã¯ã©ã‚“ãªã¨ãã‚‚æ´»ç”¨ã—ãŸã„ã¨ã„ã†ã®ãŒç§ã®è€ƒãˆæ–¹ã§ã™ã€‚ ã¾ãšã€overview.html ã‚’æ›¸ã‘ Javadoc ã‚³ãƒ¡ãƒ³ãƒˆã‚’ã„ãã‚‰ã‹æ›¸ãã‚ˆã†ãªäººã§ã‚‚ã€overview.html ã‚’æ›¸ãäººã¯æ„å¤–ã¨å°‘ãªã„ã®ã§ã¯ãªã„ã§ã—ã‚‡ã†ã‹ã€‚ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ãŒä½•åº¦ã¨ãªãè¡Œã‚ã‚Œã‚‹ã‚¢ã‚¸ãƒ£ã‚¤ãƒ«é–‹ç™ºã®ç¾å ´ã§ã¯ã€ã‚¯ãƒ©ã‚¹ã®æ§‹æˆãŒã‚ˆãã‹ã‚ã‚Šã¾ã™ã®ã§ã€ã„ã¡ã„ã¡è©³ã—ã„ã‚³ãƒ¡ãƒ³ãƒˆã‚’æ›¸ã„ã¦ã„ã‚‰ã‚Œãªã„ã¨ã„ã†ã“ã¨ã¯ã‚ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ãŒã€overview.html ã¯ãã‚Œã»ã©ä½•åº¦ã‚‚æ‰‹ã‚’ã¤ã‘ã‚‹ã‚ˆã†ãªã‚‚
hiyang 2013/03/06
overview.htmlã¯æ›¸ã‹ãªã„ã¨ãªã€‚

java

documentation
ãƒªãƒ³ã‚¯
HowToWriteAnEffectiveDesignDocument - è¨è¨ˆæ–‡æ›¸ã®ã†ã¾ã„æ›¸ãæ–¹
HowToWriteAnEffectiveDesignDocument - è¨è¨ˆæ–‡æ›¸ã®ã†ã¾ã„æ›¸ãæ–¹ ç›®æ¬¡ ã“ã®æ–‡æ›¸ã«ã¤ã„ã¦ è¨è¨ˆæ–‡æ›¸ã®ã†ã¾ã„æ›¸ãæ–¹ ãªãœè¨è¨ˆæ–‡æ›¸ã‚’æ›¸ãã®ã‹ è‰¯ã„è¨è¨ˆã¨ã¯ä½•ã‹ åŒåƒšã®é–‹ç™ºè€…ã«å‘ã‘ã¦æ›¸ã ç¬¬ 1 ç¯€ã«æ›¸ãã“ã¨: ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆ/ã‚µãƒ–ã‚·ã‚¹ãƒ†ãƒ ã®ç›®çš„ã‚’ç¤ºã™ ç¬¬ 2 ç¯€ã«æ›¸ãã“ã¨: è¨è¨ˆã«ä½¿ã†é«˜ãƒ¬ãƒ™ãƒ«ãªã‚¨ãƒ³ãƒ†ã‚£ãƒ†ã‚£ã‚’å®šç¾©ã™ã‚‹ ç¬¬ 3 ç¯€ã«æ›¸ãã“ã¨: å€‹ã€…ã®ã‚¨ãƒ³ãƒ†ã‚£ãƒ†ã‚£ã«é–¢ã™ã‚‹ä½Žãƒ¬ãƒ™ãƒ«ã®è¨è¨ˆã‚’æ›¸ã ä½¿ã„æ–¹ è¨å®š ãƒ¢ãƒ‡ãƒ« ç›¸äº’ä½œç”¨ ç¬¬ 4 ç¯€ã«æ›¸ãã“ã¨: åˆ©ç‚¹, å‰æ, ãƒªã‚¹ã‚¯/æ‡¸å¿µäº‹é … ãƒžãƒãƒ¼ã‚¸ãƒ£å‘ã‘ã«æ›¸ãã“ã¨ æœ€å¾Œã« è¨è¨ˆæ–‡æ›¸ã®ã†ã¾ã„æ›¸ãæ–¹ ã“ã®æ–‡æ›¸ã«ã¤ã„ã¦ "How to Write an Effective Design Document" ã®æ—¥æœ¬èªžè¨³ã§ã™. http://blog.slickedit.com/?p=43 æŽ¨æ•²æ“è¿Ž: èª¤è¨³, ã‚¿ã‚¤ãƒ, è¨³èªžã®ä¸çµ±ä¸€,
hiyang 2007/09/24
writing

documentation
ãƒªãƒ³ã‚¯
1