In Ruby, if you have several files called foo.rb in different directories of $LOAD_PATH and execute require "foo" the first one found gets loaded, and the rest are ignored.

Stigmergy (/ˈstɪɡmərdʒi/ STIG-mər-jee) is a mechanism of indirect coordination, through the environment, between agents or actions.

three steps required to solve the all-importantcorrespondence problem. Step one, according to Shenkar: specify one’s ownproblem and identify an analogous problem that has been solved successfully.Step two: rigorously analyze why the solution is successful. Jobs and hisengineers at Apple’s headquarters in Cupertino, California, immediately got towork deconstructing the marvels they’d seen at the Xerox facility. Soon theywere on to the third and most challenging step: identify how one’s owncircumstances differ, then figure out how to adapt the original solution to thenew setting.

I find some of XDG's default dirs, especially ~/.local/share/whatever, to be very annoying. (Almost as annoying as having ~/snap polluting my home dir, but for a different reason.) I shouldn't have to type such long paths or navigate three folders deep in order to access my data files. I therefore make use of the XDG_DATA_HOME environment variable for XDG-style programs, so they will put my files somewhere convenient. However, I don't think Snap can honor that variable, because AppArmor rules require fixed paths. Given 1 & 2, I think ~/.snap/data is a sensible compromise, at least until the underlying components are flexible enough to let the user choose.

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

import * as utils from '../../../../../../../shared/utils';

Saying that web devs used to be fine with relative imports is like saying that human beings used to be fine living without refrigerators. Sure we did. But was it better than it is now? No. No, it wasn't.

Everyone working in a TypeScript project that grows beyond a certains limit will eventually experience the situation commonly described as path hell, the snippet below is an example of such hell.

No more shit-coding paths in Node like so:

I was reading about path-mapping in tsconfig.json and I wanted to use it to avoid using the following ugly paths:

However, I just went through the same exercise of moving from relative paths everywhere to module paths.

Unlike some other languages, Sass doesn’t require that you use ./ for relative imports. Relative imports are always available.

The sass-loader uses Sass's custom importer feature to pass all queries to the Webpack resolving engine. Thus you can import your Sass modules from node_modules. Just prepend them with a ~ to tell Webpack that this is not a relative import: @import '~bootstrap';

It’s a risky blanket statement that causes bloat by including all the mistakes you made while building the original product.

The react community has become a big cargo cult. There are some good ideas in the community and many Bad Ideas™. Paving the bad idea cowpaths lends a sense of legitimacy to these bad technical ideas that is not merited.

I agree that "it feels gross" is a bad reason. "not paving a bad cowpath" is a much better reason.

If the react cargo cult didn't have the JSX cowpath paved for them and acclimated to describing their app interface with vanilla javascript, they'd cargo cult around that. It's really about the path of least resistance and familiarity.

To make this even easier, you can also simply import @testing-library/react/dont-cleanup-after-each which will do the same thing.

var webpack = require('webpack');

const path = require('path'); 

path: 'dist'

path: path.resolve(__dirname, 'dist')

Many subjects and ideas link together Leveling-up in one area can mean also leveling-up in another You don’t have to learn everything about a subject The learner (with some prompting) can decide the learning goal It’s OK to jump around a bit while learning