Grawl

TL;DR

With ASDF, you can manage version of Node, Yarn, PNPM, PHP, Python, and more than 400 other tools, languages and binaries.

1. Uninstall nvm

2. Install asdf

3. Install nodejs plugin for asdf

   Add legacy_version_file = yes to ~/.asdfrc file

4. Install gnupg

Sudok

Note: this assumes you are using ZSH shell.


## Installation

Install [asdf](https://github.com/asdf-vm/asdf):
```
$ git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.4.0
$ echo -e '\n. $HOME/.asdf/asdf.sh' >> ~/.zshrc
$ echo -e '\n. $HOME/.asdf/completions/asdf.bash' >> ~/.zshrc

MWins

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

TrevorJTClarke

var devices = [
  { name: 'Desktop - Huge', width: 2880, height: 1800, ratio: 2, type: 'desktop' },
  { name: 'Desktop - Extra Large', width: 1920, height: 1080, ratio: 1, type: 'desktop' },
  { name: 'Desktop - Large', width: 1440, height: 900, ratio: 1, type: 'desktop' },
  { name: 'Desktop - HiDPI', width: 1366, height: 768, ratio: 1, type: 'desktop' },
  { name: 'Desktop - MDPI', width: 1280, height: 800, ratio: 1, type: 'desktop' },
  { name: 'Laptop with HiDPI screen', width: 1440, height: 900, ratio: 2, type: 'desktop' },
  { name: 'Laptop with MDPI screen', width: 1280, height: 800, ratio: 1, type: 'desktop' },
  { name: 'Laptop with touch', width: 1280, height: 950, ratio: 1, type: 'desktop' },
  { name: 'Tablet - Portrait', width: 768, height: 1024, ratio: 1, type: 'tablet' },

anthony2025

"Beginners get confused as to why a file doesn’t disappear from history when they place it into their .gitignore file.
The answer to this is quite simple! When you tell Git to ignore files, it’s going to only stop watching changes for that file,
and nothing else. This means that the history will still remember the file and have it.
If you want to remove a file from the repository, but keep it in your working directory, simply use:
git rm --cached <file>
However, this will still keep the file in history. If you actually want to remove it from history, you really have two options:
rewrite your repository’s commits, or start over.
Both options really suck, and that’s for a good reason: Git tries hard not to lose your data.
Just like with rebasing, Git forces you to think about these kinds of options since they are destructive operations.
If you did actually want to remove a file from history, git filter-branch is the hacksaw you’re looking for.

Kartones

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)