naming-convention
naming-cheatsheet
| naming-convention | naming-cheatsheet | |
|---|---|---|
| 1 | 24 | |
| 1,796 | 13,644 | |
| - | - | |
| 4.2 | 0.6 | |
| 5 months ago | about 2 months ago | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
naming-convention
naming-cheatsheet
-
My team lead always fails my code
This guide is my go-to recommendation for freshers for "naming things": https://github.com/kettanaito/naming-cheatsheet
- Clean code (la juniori)
-
Some scripts work weirdly
Use better naming. What's variablename? var iab; len(name)? What does reader do? Read a book? https://github.com/kettanaito/naming-cheatsheet
-
Help with this password generator
Not an answer, but https://github.com/kettanaito/naming-cheatsheet
-
Variable inside a function with the same name?
But why would you need variable inside a function with the same name? https://github.com/kettanaito/naming-cheatsheet
-
Live coding preparation tips
Use the programming language you're most comfortable with if requirements are not strictly coupled to one programming language. Share your thoughts while you're coding so the interviewers can feel your way of thinking and problem-solving. Also, ask questions when something needs to be clarified for you. Try not to write pieces of code you don't fully understand, for example, using IIFE and not knowing how to pass an argument into it, using ; in front of it, and not knowing why it's used. Try to write readable code with understandable variable and function names. Avoid writing too nested statements, so it's not easy to understand the code's flow. Try to write code that is easy to cover with the tests.
- What are some things you look for during a code review?
-
Great resources for learning React and Typescript
Naming Convention Cheatsheet
-
How to cope with varying writing styles in code docs and logging messages?
Enforce style with a linter. In the js world there is also prettier. Agree upon a naming style for instance this naming cheatsheet although that is harder to enforce
-
What does it take to be a good programmer?
What a great answer :)
Regarding naming things, this comes to my mind: https://github.com/kettanaito/naming-cheatsheet
What are some alternatives?
DataLemur-SQL-Challenges - This repository contains solutions to the SQL challenges posted on DataLemur website using PostgreSQL environment
visx - 🐯 visx | visualization components
US-Cities-Database - :us: SQL dump of U.S. cities data containing latitude and longitude
Front-End-Checklist - 🗂 The perfect Front-End Checklist for modern websites and meticulous developers
DataAccessGeneration - Better SQL Server stored procedure calls from C#
modern-php-cheatsheet - Cheatsheet for some PHP knowledge you will frequently encounter in modern projects.
pljson - PL/JSON is a generic JSON object written in PL/SQL. Using PL/SQL object syntax, users instantiate a JSON object and then add members, arrays and additional JSON objects. This object type can store JSON data, in Oracle, persistently.
markdown-wikitext - A cheatsheet mirroring Markdown and Wikitext
TheLoadingLibrary - The Loading Library aims to make programming in c# easier.
scaffdog - :dog: scaffdog is Markdown driven scaffolding tool.
sqlserver-kit - Useful links, scripts, tools and best practice for Microsoft SQL Server Database
explainshell - match command-line arguments to their help text