Introduction · Go-SCP
Introduction Go Language - Web Application Secure Coding Practices is a guide written for anyone who is using the Go Programming Language and aims to use it for web development. This book is collaborative effort of Checkmarx Security Research Team and it follows the OWASP Secure Coding Practices - Quick Reference Guide v2 (stable) release. The main goal of this book is to help developers avoid com
jQuery Coding Standards & Best Practices
All variables that are used to store/cache jQuery objects should have a name prefixed with a $. Always cache your jQuery selector returned objects in variables for reuse. var $myDiv = $("#myDiv"); $myDiv.click(function(){...}); Use camel case for naming variables. Use ID selector whenever possible. It is faster because they are handled using document.getElementById(). When using class selectors, d
API design guide  | Cloud API Design Guide  | Google Cloud
Send feedback API design guide Stay organized with collections Save and categorize content based on your preferences. Changelog Introduction This is a general design guide for networked APIs. It has been used inside Google since 2014 and is the guide that Google follows when designing Cloud APIs and other Google APIs. This design guide is shared here to inform outside developers and to make it eas
GitHub - RichardLitt/standard-readme: A standard style for README files
Standard Readme started with the issue originally posed by @maxogden over at feross/standard in this issue, about whether or not a tool to standardize readmes would be useful. A lot of that discussion ended up in zcei's standard-readme repository. While working on maintaining the IPFS repositories, I needed a way to standardize Readmes across that organization. This specification started as a resu
DHHã¯ã©ã®ã‚ˆã†ã«Railsã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã‚’書ãã®ã‹ | POSTD
ç§ãŸã¡ã®æ•‘世主DHHâ„¢ã¯æœ€è¿‘ã® Full Stack Radioã®ã‚¤ãƒ³ã‚¿ãƒ“ュー ã§ã€ Basecamp ã®æœ€æ–°ç‰ˆã§å½¼ãŒã©ã®ã‚ˆã†ã«Railsã®ã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã‚’書ã„ãŸã‹ã‚’説明ã—ã¦ã„ã¾ã™ã€‚下記ã¯ã€å½¼ã®ã™ã°ã‚‰ã—ã„話を書ãå–ã£ãŸã‚‚ã®ã§ã™ã€‚ ã“ã‚Œã¾ã§ã«æ€ã†ã‚ˆã†ã«ãªã£ã¦ããŸã®ã¯ã€ã€ŒRESTã®åŽŸå‰‡ã«å¾“ã†ã«ã¯ã€ã©ã®ã‚¿ã‚¤ãƒŸãƒ³ã‚°ã§æ–°ãŸãªã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã‚’作るã¹ãã‹ã‚’一度決ã‚ãŸã‚‰ã€ã»ã¼ç•°ä¾‹ãªããã®åŽŸå‰‡ã‚’éµå®ˆã™ã‚‹ã¹ãã ã€ã¨ã„ã†ã“ã¨ã§ã™ã€‚ã„ã¤ã ã£ã¦ãã®æ–¹ãŒã†ã¾ãã„ãã‚“ã§ã™ã€‚自分ã®ä½œã£ãŸã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã®çŠ¶æ…‹ã‚’悔やむã®ã¯æ±ºã¾ã£ã¦ã€ä½œã£ãŸã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã®æ•°ãŒå°‘ãªã™ãŽãŸæ™‚ã§ã™ã€‚多ãã®å‡¦ç†ã‚’ä»»ã›ã‚ˆã†ã¨ã—ã™ãŽã¦ã—ã¾ã†ã‚“ã§ã™ã€‚ ãã“ã§Basecamp 3ã§ã¯ã€ã‚る程度ç†ã«ã‹ãªã£ãŸã‚µãƒ–リソースãŒã‚ã‚Œã°ã€æ¯Žå›žã‚³ãƒ³ãƒˆãƒãƒ¼ãƒ©ã‚’分割ã—ã¦ã„ãã¾ã™ã€‚フィルタãªã©ã®å ´åˆã§ã™ã。例ãˆã°ç”»é¢ãŒã‚ã£ã¦ã€ãã‚ŒãŒã‚る状態ã«ãªã£ã¦ã„ã‚‹ã¨ã—ã¾ã™ã€‚ã‚‚ã—ã“ã‚Œã«ã„ãã¤ã‹ã®ãƒ•ã‚£
SQL style guide by Simon Holywell
Overview General Do Avoid Naming conventions General Tables Columns Aliasing or correlations Stored procedures Uniform suffixes Query syntax Reserved words White space Indentation Preferred formalisms Create syntax Choosing data types Specifying default values Constraints and keys Designs to avoid Appendix Reserved keyword reference Column data types SQL style guide Overview You can use this set o
https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml
Revision 0.9 This style guide contains many details that are initially hidden from view. They are marked by the triangle icon, which you see here on your left. Click it now. You should see "Hooray" appear below. Hooray! Now you know you can expand points to get more details. Alternatively, there's an "expand all" at the top of this document. This style guide documents guidelines and recommendation
planningcenter/flux-patterns · GitHub
README.md Flux Following are proposed guidelines for using React with Flux. A Loose Pattern "Flux" is a loose pattern. Every company represented at React.js Conf 2015 builds their Flux apps in a slightly different way, and even different groups within Facebook didn't agree on a single way to implement Flux apps. Because of that, you can take the following guidelines fairly loosely and adapt to you
大è¦æ¨¡Reactアプリケーションを構築ã™ã‚‹ãŸã‚ã®ãƒ™ã‚¹ãƒˆãƒ—ラクティス | POSTD
Sift Scienceã§è£½ä½œã«Reactを使ã„始ã‚ã¦ã‹ã‚‰ã»ã¼1å¹´ã«ãªã‚Šã¾ã—ãŸã€‚ãã®é–“ã€Backbone+Reactã¨ã„ㆠフランケンシュタインã®ã‚ˆã†ãª 複åˆã‚¢ãƒ—リケーションをã€Reactコンãƒãƒ¼ãƒãƒ³ãƒˆã‹ã‚‰ãªã‚‹ã€ã‹ãªã‚Šå¤§ããª1ã¤ã®éšŽå±¤ã«è‚²ã¦ä¸Šã’ã¾ã—ãŸã€‚ã“ã®è¨˜äº‹ã§ã¯ã€UIä¸å’Œã‚’最å°é™ã«ã—ãªãŒã‚‰ã€ã‚³ãƒ¼ãƒ‰ãƒ™ãƒ¼ã‚¹ã‚’スケーリングã™ã‚‹ãŸã‚ã«å½¹ç«‹ã£ãŸæŠ€æ³•ã¨ãƒ™ã‚¹ãƒˆãƒ—ラクティスを紹介ã—ã¾ã™ã€‚ã¾ãŸã€ä¸€èˆ¬çš„ãªã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆã®ãƒ‡ã‚¶ã‚¤ãƒ³ãƒ‘ターンã«ã¤ã„ã¦ã€ã„ãã¤ã‹èª¬æ˜Žã—ã¾ã™ã€‚ ã“ã®è¨˜äº‹ãŒçš†ã•ã‚“ã®æ™‚é–“ã®ç¯€ç´„ã¨ç²¾ç¥žè¡›ç”Ÿã®ç¶æŒã«å½¹ç«‹ã¡ã€UIãŒè¤‡é›‘ã«ãªã£ã¦ã‚‚Reactコードベースã®ä¿å…¨æ€§ã‚’ç¶æŒã™ã‚‹ï¼ˆç ´ç¶»ã™ã‚‹ã®ã§ã¯ãªã）ãŸã‚ã®æ–°ã—ã„ツールをæä¾›ã§ãã‚Œã°å¹¸ã„ã§ã™ã€‚ componentDidUpdateã§ã€ã‚‚ã£ã¨ã§ãã‚‹ Reactã®æœ¬è³ªã¯ã€DOMã®æ›´æ–°ã¨ã„ã†ã‚¿ã‚¹ã‚¯ã‚’命令的ãªã‚‚ã®ã‹ã‚‰å®£è¨€çš„ãªã‚‚ã®ã«å¤‰ãˆã‚‹ã¨ã„ã†ã“ã¨ã§ã™ã€‚ä»–ã®ã‚¿ã‚¤ãƒ—ã®å‘½
React Style Guide を日本語訳ã—㟠- Qiita
react-style-guideã®æ—¥æœ¬èªžè¨³ãŒè¦‹ã¤ã‹ã‚‰ãªã‹ã£ãŸã®ã§ã€ã–ã£ã¨èªã‚€ã ã‘ã§ãªã英語ã®å‹‰å¼·ãŒã¦ã‚‰ã‚ªãƒ¬ã‚ªãƒ¬ãªå’Œè¨³ã‚’ã—ã¦ã¿ãŸã€‚（åŠåˆ†ãらã„個人用メモ状態ã§ã™ï¼‰ （ã‚ã‹ã‚‰ãªã„部分ã¯Google翻訳ã«é ¼ã£ãŸã—諦ã‚ãŸã‚Šã—ãŸã‚Šã—ãŸã—）もã®ã™ã”ã„誤訳æ„訳å£èªžè¨³å¤šæ•°ã ã¨æ€ã†ã®ã§ã€æŒ‡æ‘˜ç‰ã„ãŸã ã‘ã‚‹ã¨å¹¸ã„ã§ã™ã€‚ Reactã®"独特ãª"考ãˆæ–¹ã¯ä»Šã¾ã§ã“ã‚Œã¨ã„ã£ã¦ã‚¹ãƒƒã‚リã¨æ›¸ãã“ã¨ãŒã§ããªã‹ã£ãŸã€‚ ã ã‹ã‚‰ç§ã¯ã€æ‰€å±žã™ã‚‹ãƒãƒ¼ãƒ ã§éŽåŽ»æ•°ãƒ¶æœˆã®é–“ã§ä½¿ã£ã¦ã¿ãŸã‚¤ã‚±ã¦ã‚‹æ„Ÿã˜ã®Reactã®æ›¸ãæ–¹ã«ã¤ã„ã¦ã¾ã¨ã‚ã¦ã¿ã‚ˆã†ã¨è€ƒãˆãŸã€‚ ã“ã®è¨˜äº‹ã¯ã€React-Componentsã«é™å®šã—ãŸç¯„囲ã§ã®è©±ã‚’ã—ã¾ã™ã€‚ (JavaScriptã®)プãƒã‚°ãƒ©ãƒŸãƒ³ã‚°å…¨ä½“ã®ã‚¹ã‚¿ã‚¤ãƒ«ã‚„ã€componentization（Web Componentsを用ã„ãŸé–‹ç™º?）ã€Fluxã®æ¦‚念ã¨ã‹ã®è©±ã§ã¯ãªã„ã§ã™ã€‚ åŒæ§˜ã«ã€ãƒ‰ã‚ュメントã¯ç”Ÿãã¦ã„ã¾ã™ã—ã€ã“ã‚Œ
Felix's Node.js Style Guide(和訳)
node.jsアプリケーションã®ã‚¹ã‚¿ã‚¤ãƒ«ã‚’支é…ã™ã‚‹å…¬çš„ãªæ–‡ç« ã¯ã‚ã‚Šã¾ã›ã‚“。ã“ã®ã‚¬ã‚¤ãƒ‰ã¯ã‚ãªãŸãŒç¾Žã—ãã€ä¸€è²«ã—ãŸã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã‚’作れるよã†ã«ãªã‚‹æ•™è¨“を与ãˆã‚ˆã†ã¨ã™ã‚‹ç§ã®ç‹¬æ–ã®è©¦ã¿ã§ã™ã€‚ ã“ã®ã‚¬ã‚¤ãƒ‰ã¯ã‚ãªãŸãŒnode.jsã®ã¿ã‚’対象ã«ã—ã¦ã„ã‚‹ã¨ä»®å®šã—ã¦ã„ã¾ã™ã€‚ã‚‚ã—ã‚ãªãŸã®ã‚³ãƒ¼ãƒ‰ã‚’ブラウザãªã©ä»–ã®ç’°å¢ƒã§ã‚‚å‹•ã‹ã™å¿…è¦ãŒã‚ã‚‹ã®ãªã‚‰ã€ã„ãã¤ã‹ã®ã‚¬ã‚¤ãƒ‰ã¯ç„¡è¦–ã—ã¦ãã ã•ã„。 様々ãªãƒ‘ッケージã ã‘ã§ã¯ãªãnode.jsã‚‚ã¾ãŸã€ãã‚Œãžã‚Œè‡ªä½“ã®ã‚¹ã‚¿ã‚¤ãƒ«ã‚’æŒã£ã¦ã„ã¾ã™ã€‚ãªã®ã§ä½•ã‹ã®ãƒ‘ッケージã®é–‹ç™ºã«è²¢çŒ®ã™ã‚‹ã“ã¨ã«èˆˆå‘³ãŒã‚ã‚‹ã®ãªã‚‰ã°ã€ãã‚Œãžã‚Œã®ãƒ«ãƒ¼ãƒ«ã«å¾“ã£ã¦ã‚³ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã‚’楽ã—ã‚“ã§ãã ã•ã„。 Tab vs Spaces ã¾ãšã¯ã“ã®å®—教的ãªå•é¡Œã®è©±ã‚’ã—ã¾ã—ょã†ã€‚ç§é”ã®æ…ˆæ‚²æ·±ã„独è£è€…様ã¯nodeã®ã‚³ã‚¢ã«2スペースã®ã‚¤ãƒ³ãƒ‡ãƒ³ãƒˆã‚’é¸æŠžãªã•ã£ãŸã®ã§ã€å½¼ã®ç§©åºã«å¾“ã†ã®ãŒè³¢æ˜Žã§ã—ょã†ã€‚ セミコãƒãƒ³ ã‚ãªãŸã‹ã‚‰ã‚»ãƒŸã‚³ãƒãƒ³ã‚’奪ãŠã†ã¨ã™ã‚‹
React Tips and Best Practices - ÆFLASH
I've spent a good deal of the past year working with React. I've written, refactored, and re-written many components in that time, and I've seen some best practices and anti-patterns emerge. I'm not going to get into what React is or why you should use it — there are plenty of articles about React floating around the internet. I'm also going to assume you know the basics of working with React and
An opinionated guide to React.js - Best practices and conventions - Web Design Weekly
An opinionated guide to React.js – Best practices and conventions I’ve been using React.js for a little while now, both in my 9 to 5 job and for my own projects, and during that time I have started evolving my own set of React.js best practices. The following guidelines mostly focus on component structure and JSX. However, they are not hard and fast rules, but more of an opinionated set of guideli
React Style Guide
The idea of "idiomatic" React hasn’t been explicitly written on, so I thought I’d offer some conventions that my team at Tune has been using during the past few months of adoption. For the sake of this article, scope will be limited to coding style in React components - not styling, componentization, or Flux strategies. Also, this is meant to be a living document - and I am sure there are better i
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - recruit-lifestyle/swift-style-guide
api-guidelines/Guidelines.md at master · microsoft/api-guidelines
Google JSON Style Guide
CodeReviewComments
GitHub - hiloki/flocss: CSS organization methodology.
GitHub - chantastic/react-patterns: moved to to https://github.com/chantastic/sites/tree/master/reactpatterns.com
{{#tags}}- {{label}}
{{/tags}}