naming-cheatsheet
starship
Our great sponsors
naming-cheatsheet | starship | |
---|---|---|
24 | 298 | |
13,629 | 40,834 | |
- | 3.3% | |
0.6 | 9.7 | |
about 2 months ago | 3 days ago | |
Rust | ||
MIT License | ISC 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-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
starship
-
Atuin β Magical Shell History
Agreed, I use this in conjunction with Starship [1], both initialized specifically for Fish in the config. I love this shell so much.
[1] - https://starship.rs/
- Starship.rs: minimal, fast prompt for any shell
- Starship: The minimal, fast, and customizable prompt
-
Oh My Zsh
starship is the new spaceship, yo
https://starship.rs/
- Starship: Minimal, fast, infinitely customizable prompt for any shell
-
Z β Jump Around
It seems like the Rust community is quite happy to support alternative shells. Iβve seen couple of projects, now, that support way more esoteric shells than I would expect, like βxonshβ. Starship (https://starship.rs/) immediately comes to mind.
- MacOS tools to make your life easier
-
[MacOS] Setting up zsh in MacOS, any hints, dos/don'ts, advice, or guides?
Until now I have been using bash on Windows with Starship as the prompt. The only reason I went with Starship, is that it was easy to setup and at the time I did not have much free time to devout to the shell/prompt configuration.
-
Monaspace
I'm staying on BitstromWera Nerd Font. Works great with Starship.
https://www.nerdfonts.com/font-downloads
https://starship.rs
-
Organizing Multiple Git Identities
I use conditional includes for this, but I also add a single letter describing which Git identity I'm currently using to my PS1 so that it appears before $ in my shell prompt. This prevents me from committing code with the wrong identity, in case I'm using a git checkout that's anywhere not covered by the conditional include rules.
I use Starship (https://starship.rs) to manage my prompt, and wrote a short script that only runs if I'm somewhere in a git repo, and if so finds my Git user's email and looks up the corresponding letter in an associative array declared in my ~/.config/starship-zsh/.zshenv:
git_email=$(git config --get user.email | perl -pe 'chomp if eof')
What are some alternatives?
visx - π― visx | visualization components
oh-my-posh - The most customisable and low-latency cross platform/shell prompt renderer
naming-convention - Templates for naming convention - TSQL, JavaScript, C#, R, Python, Powershell
spaceship-prompt - :rocket::star: Minimalistic, powerful and extremely customizable Zsh prompt
Front-End-Checklist - π The perfect Front-End Checklist for modern websites and meticulous developers
powerlevel10k - A Zsh theme
modern-php-cheatsheet - Cheatsheet for some PHP knowledge you will frequently encounter in modern projects.
ohmyzsh - π A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
markdown-wikitext - A cheatsheet mirroring Markdown and Wikitext
zsh-autocomplete - π€ Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
scaffdog - :dog: scaffdog is Markdown driven scaffolding tool.
alacritty - A cross-platform, OpenGL terminal emulator.