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
When it comes to finding the right class name, it can quickly drive you to despair. Even the most experienced CSS developers don't always find the right class name right away. This tool aims to help you to not get lost in the BEM cosmos by giving you naming-suggestions for some of the most common web components. If you still have no idea what BEM means, we have added some helpful links below. For
Welcome - The Naming Convention Project The Naming Convention Project is an effort to identify, collect and maintain a set of guidelines for best naming practices. How we work: We accept recommendations from all enthusiastic who care about the quality. The suggested recommendations will be submitted to website by collaborative consensus based processes. Naming Convention topic list: C# Git Java PH
We use git branches at DeepSource to organize ongoing work to ensure that software delivery stays effective. If you use git today, there are high chances that you're either using the famed git-flow or the more recent GitHub flow. Both these workflows depend extensively on using branches effectively — and naming a new branch is something many developers struggle with. A consistent branch naming con
こんにちは。ROUTE06 Tech Blogの編集チームです。 ROUTE06のエンジニアによる対談を、連載でお届けします。 第2回は、CTOの重岡 正さんと星野 剛志(ほしの つよし)さんです。 現在、Ruby on Railsエンジニアとしてエンタープライズ向けAPIプラットフォーム「Plain」のAPI開発に関わる星野さん。実は、Rubyに出会ったことをきっかけに、営業職からエンジニアへ転向するというキャリアを歩んできました。 星野さんに、Rubyの好きなところや日々の開発で大切にしているコミュニケーション、そして「naming」へのこだわりについて聞きました。 プロフィール 星野 剛志 HOSHINO Tsuyoshi 1982年生まれ。東京都出身。 営業企画職として働きながら、独学でRubyを学び、2014年にエンジニアとして株式会社フィードフォースへ入社。その後、株式会社スマ
url.js `B�y�U pJ�y�U /* href ┌────────────────────────────────────────┴──────────────────────────────────────────────┐ origin │ ┌────────────┴──────────────┐ │ │ authority │ │ ┌───────────────┴───────────────────────────┐ │ │ │ host resource │ │ ┌──────────┴─────────────────┐ ┌────────────┴───────────┬───────┐ │ │ hostname │ pathname │ │ │ │ ┌──────────────┴────────────┐ │ ┌──────┴───────┐ │ │ pro
Developers spend most of their time reading code, understanding it and exploring other ways to use existing solutions. Frankly, in our profession, there is very little time on actually writing new libraries and creating new interfaces in real-life development. So it is quite important to have some help in the most common activities. Naming conventions is one such thing that improves readability an
Design tokens have provided a visual foundation of many design systems since Salesforce pioneered the concept in 2014. I wrote an impassioned article on design tokens in 2016, and my energy on the topic continues to grow. As systems of visual style spread across a widening landscape of components, platforms and outputs, design tokens — and their names — are increasingly important. Effective token
Reading Time: 9 minutes Phil Karlton has famously said that the two hardest things in computer science are naming things and cache invalidation1. That’s still kinda true in front-end development. Naming stuff is hard, and so is changing a class name when your stylesheet is cached. For quite a few years, I’ve had a gist called “Tiny Rules for How to Name Stuff.” Which is what you think: little tiny
Originally posted at michaelzanggl.com. Subscribe to my newsletter to never miss out on new content. There is a convention to prefix boolean variables and function names with "is" or "has". You know, something like isLoggedIn, hasAccess or things like that. But throughout my career I have seen and written code where this convention was just thrown out the window. So let's check out some of these e
Regarding Git and Branch Naming June 23, 2020 Both Conservancy and the Git project are aware that the initial branch name, ‘master’, is offensive to some people and we empathize with those hurt by the use of that term. Existing versions of Git are capable of working with any branch name; there's nothing special about ‘master’ except that it has historically been the name used for the first branch
Why do the virus and the disease have different names? Viruses, and the diseases they cause, often have different names. For example, HIV is the virus that causes AIDS. People often know the name of a disease, but not the name of the virus that causes it. There are different processes, and purposes, for naming viruses and diseases. Viruses are named based on their genetic structure to facilitate
Linux Daily Topics 2020年11月24日テクノロジの世界から差別的な言葉をなくそう! ―IBM、Red Hatなどが「Inclusive Naming Initiative」を設立 「ブラックリスト/ホワイトリスト」「マスター/スレーブ」などこれまでITの世界であたりまえに使われてきた差別的で不明瞭な用語を廃していくことをゴールに、IBMやRed Hat、The Linux Foundationなどが参加する「Inclusive Naming Initiative」の設立が11月19日(米国時間)、開催中のバーチャルカンファレンス「KubeCon North America 2020」で発表された。 Inclusive Naming Initiative URL:https://inclusivenaming.org/ 同イニシアティブは設立の主旨として「ソフトウ
🛑 This file is source code, not the primary documentation location! 🛑 See https://typescript-eslint.io/rules/naming-convention for documentation. Enforcing naming conventions helps keep the codebase consistent, and reduces overhead when thinking about how to name a variable. Additionally, a well-designed style guide can help communicate intent, such as by enforcing all private properties begin w
Context At Inturn we spend a lot of time debating and crafting best practices around common patterns. Recently, after converting our styling system to emotion (a styled component library), we ran into a question: “How should we name these things?” Problem The issue we were running into mostly stemmed from our styled container components. Traditionally, when using classes, you would give the root e
Follow on FacebookA JavaScript naming conventions introduction by example -- which gives you the common sense when it comes to naming variables, functions, classes or components in JavaScript. No one is enforcing these naming convention rules, however, they are widely accepted as a standard in the JS community. JavaScript Naming Conventions: VariablesJavaScript variables are case sensitive. Theref
Design tokens are the single source of truth for design primitives like colors or tokens. If you are new to the topic, you may want to learn the basics of design tokens first. Note: This article aims to be an exhaustive reference for naming design tokens. If you find some information is missing, please do let me know via a comment or email so I can add it. Naming token levelsTokens are commonly sp
The other day, while in a planning poker session, the question of the naming of a particular table arose. During that conversation, one of our developers suggested that the table shall have a singular name, while others questioned that idea and thought that every table names should be plural. This led me to ask this question: is there a better choice? Should table names be singular or plural? It’s
Naming's a hard problem, right? Well, coming up with the names can be hard. After that, it's just a simple matter of typing. Here are a few of my naming conventions for React or even handling in general. For propsWhen defining the prop names, I usually prefix with on*, as in onClick. This matches the built-in event handler convention. And by matching it, we declare that these props will house simi
“Naming things is hard” goes the software engineering axiom and CSS is no exception. Here are some collected thoughts related to naming CSS Custom Properties. I’m going to use use the terms “variable” and “custom property” interchangeably since they are effectively the same thing for the purposes of what to call them. Disclaimer: What follows is not gospel. CSS to me is a very poetic language, the
There are only two hard things in Computer Science: cache invalidation and naming things. — Phil Karlton Our application is divided into 2 products: A line platform (private) and A Community (public). Those products share the same code base and most of the time the same components, in a set of 300+ React Components.
Determining the best name for something (e.g., a class, variable, or function) in software engineering often feels like an imperfect science. A handful of blog posts and small sections in various books have described some aspects of good names, but we don’t have a thorough, canonical set of principles that describe what makes a name a good name. The Naming Things book describes a set of principles
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く