Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| # -*- coding: utf-8 -*- | |
| """Operations on cartesian geographical grid.""" | |
| import numpy as np | |
| EARTH_RADIUS = 6371000.0 # m | |
| def _guess_bounds(points, bound_position=0.5): | |
| """ | |
| Guess bounds of grid cells. |
| #!/bin/bash | |
| # Usage: | |
| # | |
| # curl -sL https://gist.githubusercontent.com/archan937/d35deef3b1f2b5522dd4b8f397038d27/raw/setup-dnsmasq.sh | sudo bash | |
| # | |
| DOMAIN=".test" | |
| ensure_ping() { |
This means, on your local machine, you haven't made any SSH keys. Not to worry. Here's how to fix:
*nix based command prompt (but not the default Windows Command Prompt!)cd ~/.ssh. This will take you to the root directory for Git (Likely C:\Users\[YOUR-USER-NAME]\.ssh\ on Windows).ssh folder, there should be these two files: id_rsa and id_rsa.pub. These are the files that tell your computer how to communicate with GitHub, BitBucket, or any other Git based service. Type ls to see a directory listing. If those two files don't show up, proceed to the next step. NOTE: Your SSH keys must be named id_rsa and id_rsa.pub in order for Git, GitHub, and BitBucket to recognize them by default.ssh-keygen -t rsa -C "your_email@example.com". Th
| <?php | |
| $server = "localhost"; | |
| $user = "root"; | |
| $password = ""; | |
| $nama_database = "pendaftaran_siswa"; | |
| $db = mysqli_connect($server, $user, $password, $nama_database); | |
| if( !$db ){ | |
| die("Gagal terhubung dengan database: " . mysqli_connect_error()); |
| /** | |
| * This resolver forces Jest to look at a *custom* `"jest"` condition in `package.json#exports`. | |
| * | |
| * Whenever you use self-referencing imports or subpath imports in the source code (or tests) | |
| * the default behaviour of Jest is to go to the package's manifest for information, and resolve | |
| * the import by choosing one of the conditions that are used by Node ("node", "default", etc.). | |
| * | |
| * The issue is that "node"/"default" usually points to transpiled `.js` files, whereas if you decide to | |
| * run the tests on the `.ts` source code (with the help of a transformer such as ts-jest or @swc/jest), | |
| * you need Jest to **only** load the `.ts` files. Otherwise, you end up with duplicated classes, |
let's say you have a C++ project in Nix that you want to work on with CLion so that the nix dependencies are available.
.nix utility directory in your project directory.nix-run.sh and nix-cmake.sh in the .nix directory..nix directory create symlinks for make, gcc, g++ - and maybe more tools, that need to have the nix dependencies and build tools available - and point them to nix-run.shnix-cmake.sh and point all other build tools to the symlinks you've created.
| # Makefile for python code | |
| # | |
| # > make help | |
| # | |
| # The following commands can be used. | |
| # | |
| # init: sets up environment and installs requirements | |
| # install: Installs development requirments | |
| # format: Formats the code with autopep8 | |
| # lint: Runs flake8 on src, exit if critical rules are broken |
tl;dr: If you want to just know the method, skip to How to section
Clangd is a state-of-the-art C/C++ LSP that can be used in every popular text editors like Neovim, Emacs or VS Code. Even CLion uses clangd under the hood. Unfortunately, clangd requires compile_commands.json to work, and the only way to painlessly generate it is to use CMake.
But what if I tell you you can quickly hack your way around that, and generate compile_commands.json for any project, no matter how compilcated? I have used that way at work for years, originaly because I used CLion which supported only CMake projects - but now I use that method succesfully with clangd and Neovim.
Basically what we need to achieve is to create a CMake file that will generate a compile_commands.json file with information about:
| <?php | |
| return [ | |
| 'frontend' => [ | |
| 'yourvendor/webmanifest' => [ | |
| 'target' => \YourVendor\Sitepackage\Middleware\Webmanifest::class, | |
| 'before' => [ | |
| 'typo3/cms-frontend/page-resolver', | |
| ], | |
| 'after' => [ |
