| local java_cmds = vim.api.nvim_create_augroup('java_cmds', {clear = true}) | |
| local cache_vars = {} | |
| local root_files = { | |
| '.git', | |
| 'mvnw', | |
| 'gradlew', | |
| 'pom.xml', | |
| 'build.gradle' | |
| } |
Based on this blogpost.
To sign Git commits, you need a gpg key. GPG stands for GNU Privacy Guard and is the de facto implementation of the OpenPGP message format. PGP stands for ‘Pretty Good Privacy’ and is a standard to sign and encrypt messages.
Install with Homebrew:
$ brew install gpg
| #!/usr/bin/env bash | |
| # Uses ~/.mailcap from https://gist.github.com/Konfekt/9797372146e65a70a44c1e24a35ae0a2 | |
| # to read binary files | |
| set -o noclobber -o noglob -o nounset -o pipefail | |
| IFS=$'\n' | |
| ## If the option `use_preview_script` is set to `true`, | |
| ## then this script will be called and its output will be displayed in ranger. |
| for (const button of document.getElementsByClassName('artdeco-button--secondary')) button.click(); |
Generally, there are two major types of technical interviews that companies have in India:
If you're aiming the traditional giants like Google, Microsoft, Amazon, etc, then you should focus solely on problem-solving & data structures (PS/DS).
Block computer for input, but remain graphical output as usual. Can be used for example to watch a movie on your laptop but forbid any input during that.
Not tested thouroughly yet, and only tested on Debian 9
i3wm makes it easy to assign applications to workspaces and save and restore layouts - which is e.g. useful for auto-starting always needed software.
To make these assignments, you need specific window properties so that you can tell i3 to assign [class="Your-app"] → 1 (in this example, Your-app will be assigned to workspace 1).
In many cases this just works. However, there are also many popular programs that do not initially set the correct window class or other properties on startup, which can be frustrating. This cheat sheet aims to show the problems and possible resolutions (or worse: workarounds) for more or less problematic applications.
If you haven’t worked with JavaScript in the last few years, these three points should give you enough knowledge to feel comfortable reading the React documentation:
let and const statements. For the purposes of the React documentation, you can consider them equivalent to var.class keyword to define JavaScript classes. There are two things worth remembering about them. Firstly, unlike with objects, you don't need to put commas between class method definitions. Secondly, unlike many other languages with classes, in JavaScript the value of this in a method [depends on how it is called](https://developer.mozilla.org/en-US/docs/Web/Jav
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.