cast
naming-cheatsheet
| cast | naming-cheatsheet | |
|---|---|---|
| - | 24 | |
| 0 | 13,671 | |
| - | - | |
| 0.0 | 0.6 | |
| almost 7 years ago | 2 months ago | |
| Haskell | ||
| BSD 3-clause "New" or "Revised" 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.
cast
We haven't tracked posts mentioning cast yet.
Tracking mentions began in Dec 2020.
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?
visx - 🐯 visx | visualization components
naming-convention - Templates for naming convention - TSQL, JavaScript, C#, R, Python, Powershell
Front-End-Checklist - 🗂 The perfect Front-End Checklist for modern websites and meticulous developers
modern-php-cheatsheet - Cheatsheet for some PHP knowledge you will frequently encounter in modern projects.
markdown-wikitext - A cheatsheet mirroring Markdown and Wikitext
scaffdog - :dog: scaffdog is Markdown driven scaffolding tool.
explainshell - match command-line arguments to their help text
react-error-boundary - Simple reusable React error boundary component
bulletproof-react - 🛡️ ⚛️ A simple, scalable, and powerful architecture for building production ready React applications.
react-router - Declarative routing for React
fiddle - :electron: 🚀 The easiest way to get started with Electron
take-action - This is an action to assign yourself to an issue for a repo you are not a contributor to.