I have an updated version of this on my blog here: https://chrisamico.com/blog/2023-01-14/python-setup/.
This is my recommended Python setup, as of Fall 2022. The Python landscape can be a confusing mess of overlapping tools that sometimes don't work well together. This is an effort to standardize our approach and environments.
| " IdeaVim Wiki https://github.com/JetBrains/ideavim/wiki | |
| " Find more examples here: https://jb.gg/share-ideavimrc | |
| " The Essential IdeaVim Remaps https://towardsdatascience.com/the-essential-ideavim-remaps-291d4cd3971b | |
| let mapleader=" " | |
| """ Common settings | |
| set showmode | |
| set scrolloff=5 | |
| " Do incremental searching. |
| "editor.tokenColorCustomizations": { | |
| "textMateRules": [ | |
| { | |
| "scope": [ | |
| "comment", | |
| "comment.block", | |
| "comment.block.documentation", | |
| "comment.line", | |
| "constant", | |
| "constant.character", |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
| def is_valid_state(state): | |
| # check if it is a valid solution | |
| return True | |
| def get_candidates(state): | |
| return [] | |
| def search(state, solutions): | |
| if is_valid_state(state): | |
| solutions.append(state.copy()) |
| # Title of Your Project [](https://twitter.com/intent/tweet?text=Check%20out%20this%20cool%20project&url=https://github.com/Cool/Project&hashtags=project,opensource) | |
|  | |
|  | |
|  | |
|  | |
| #### Description of your project |
| // | |
| // Basic instrumentation profiler by Cherno | |
| // Usage: include this header file somewhere in your code (eg. precompiled header), and then use like: | |
| // | |
| // Instrumentor::Get().BeginSession("Session Name"); // Begin session | |
| // { | |
| // InstrumentationTimer timer("Profiled Scope Name"); // Place code like this in scopes you'd like to include in profiling | |
| // // Code | |
| // } |
Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt
If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a
I will be using the root user, but would suggest creating a new user
Uses native vim regexes (which are slightly different from the regexes used by grep, ack, ag, etc) so the patterns are the same as with vim's within-file search patterns.
You can do a normal within-file search first, then re-use the same pattern to
The big "make everything stateless" hype is just that: hype. Your server-side application code, should usually be stateless, because this makes your application more resilient to errors, easier to scale, and easier to reason about. But there are exceptions to even that, especially for stuff like video game servers.
Your services are almost always going to be stateful, and should be. If you have a database, files, or literally anything that affects the responses the server sends, then the service is not stateless.
So building "stateless" services is a lie. You shouldn't strive to make your services stateless, you should make sure you're putting your state in the correct place.