(a guide by sylvie (@lostkagamine). tested, should work fine.)
(Korean version / 한국어 버전 / Chinese version / 中文版)
New: FAQ has been updated for ReShade 5.7.0 features.
If you are having issues like the screen turning black, read the mini-FAQ at the bottom of this document!
How do I determine the correct "max-old-space-size" for node.js?
The configured max-old-space-size had a higher limit than the total amount of RAM that the machine had. – Borjante
Worth trying --optimize-for-size to reduce memory usage. – Constantinos
This document now exists on the official ASP.NET core docs page.
| #!/usr/bin/env bash | |
| if [ "$EUID" -ne 0 ];then | |
| >&2 echo "This script requires root level access to run" | |
| exit 1 | |
| fi | |
| if [ -z "${WORDPRESS_DB_PASSWORD}" ]; then | |
| >&2 echo "WORDPRESS_DB_PASSWORD must be set" | |
| >&2 echo "Here is a random one that you can paste:" |
I saw this poll on Twitter earlier and was surprised at the result, which at the time of writing overwhelmingly favours option 1:
I've always been of the opinion that the (req, res, next) => {} API is the worst of all possible worlds, so one of two things is happening:
This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.
I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.
But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.
If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.
| { | |
| "listeners": { | |
| "*:8080": { | |
| "pass": "routes/wordpress" | |
| } | |
| }, | |
| "routes": { | |
| "wordpress": [ | |
| { | |
| "match": { |
| export default (function create(options = {}) { | |
| const client = { | |
| headers: options.headers || {}, | |
| create | |
| }; | |
| const events = {}; | |
| client.emit = (type, e) => { | |
| events[type] && | |
| events[type].slice().map(fn => { |
| /* eslint-disable no-unused-vars */ | |
| /* eslint-disable no-else-return */ | |
| // JSX constructor, similar to createElement() | |
| export const h = (type, props, ...children) => { | |
| return { | |
| type, | |
| // Props will be an object for components and DOM nodes, but a string for | |
| // text nodes | |
| props, |
