’ve been studying notebooks for over a decade and I still haven’t landed on a perfect organization method. I have, however, found the perfect pen: uni-ball signo, .38mm. I discovered them while teaching in Korea in 2008 and haven’t looked back.

A content-based system (like a book’s table of contents) would mean that you would have to adhere to a single structure forever (decades in advance!).

Lisa Jacobs, the founder and chief executive of Imagine It Done, a home organization service in New York City, said that out of hundreds of projects in the past few years, she can recall only three requests to organize books. In one of those examples, the arranged books were treated as a backdrop — to be admired, but not read. “The clientele that has collected books through the years are not as numerous for us,” she said.

For every minute spent in organizing, an hour is earned.by Benjamin Franklin

This is the absolute hardest part of the writing process, in my mind. The most exciting, too, because you’re never quite sure where it’s going to end up.

I’ve also got a vague sense in my head of how they should be organized — that is, what the structure of the book is going to be. This is generally when I write the formal book proposal. I know enough about the topic, now, that I have a good idea of what my central arguments are going to be and how I am going to organize the chapters.

it is not part of Svelte but it is part of Svelte Preprocess github.com/sveltejs/svelte-preprocess#global-style

git_workspace/ ├── .vscode │ └── settings.json # global settings, my preferred ones ├── my-personal-projects/ │ └── project1/ │ └── .git/ └── company-projects/ ├── .vscode │ └── settings.json # local settings, overrides some of my personal ones ├── project2/ │ └── .git/ └── project3/ └── .git/

How do you make sure you don’t lose track of cards? I don’t make sure I don’t lose track of cards. As I said above and as some of the people below talk about, one of the joys of the system is when you surprise yourself, when you rediscover, when you find the perfect card while you were looking for something else.

Most men's notes are useless stuff to others, useless even to them-selves with the passage of time, and useless especially because ofchaotic arrangement.

Note: Safari is not WebKit. Safari bugs should be reported to Apple.

Mosca backs up histhesis with this assertion: It's the power of organization thatenables the minority always to rule. There are organizedminorities and they run things and men. There are unorganizedmajorities and they are run.

A personal file is thesocial organization of the individual's memory; it in-creases the continuity between life and work, and it per-mits a continuity in the work itself, and the planning of thework; it is a crossroads of life experience, professionalactivities, and way of work. In this file the intellectualcraftsman tries to integrate what he is doing intellectuallyand what he is experiencing as a person.

In particular, it allowed for organizing common traits (such as extensibility, or different ways of showing examples as schemas that can be mixed in to the main object definitions.

2) The kanji are organized in chapters with wide themes (respectively: world, food, animals, people, body, spirit, power, learn, tools, places, journey). These chapters are in turn divided up into mini-themes dealing with each chapter (for example, different animals and ideas associated with them). This helped me a lot in mentally organizing kanji and their meanings.

If this fits your style and you don’t get any value out of having cards with locators like 3a4b/65m1, then don’t do that (for you) useless make-work. Make sure your system is working for you and you’re not working for your system.

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

As I was thinking through this on Friday, Culture Study subscriber and organizer Siena Chiang articulated the framework I needed. In a thread dedicated to the repeal of Roe in the Culture Study Discord, people were asking what so many of us were asking: what do we do. “Get organized,” Siena said. “Not just mobilized, which is showing up at a rally once or twice. Organized means acting in coordination with others who have a long term strategy. Finding a local group doing direct, tangible work and asking them how to help. They’re probably inundated right now so commit to following up in the coming month. Go in person if that’s appropriate, don’t just email. Show up thoughtfully. Be consistent and reliable. Follow their lead.”

The Essential Habits ofDigital Organizers

You never knowwhen the rejected scraps from one project might become the perfectmissing piece in another. The possibilities are endless.

We are organizing for actionability

Instead of organizing ideas according to where they come from, Irecommend organizing them according to where they are going

The goal of organizing our knowledge is to move our goalsforward, not get a PhD in notetaking.

Beethoven, despite his unruly reputation and wild romantic image, waswell organized. He saved everything in a series of notebooks that were organizedaccording to the level of development of the idea. He had notebooks for rough ideas,notebooks for improvements on those ideas, and notebooks for finished ideas,almost as if he was pre-aware of an idea’s early, middle, and late stages.

Jean-Claude Gardin (3 April 1925 - 8 April 2013) was a French archaeologist who is recognized as being one of the founders of archaeological computing.

over the past decade and change a dynamic ecosystem has developed around cryptocurrencies and blockchains. And it’s constantly getting more complicated. We’ve now got non-fungible tokens, or NFTs, unique digital bits purchased with crypto that have mostly been associated with weird pieces of digital art and are an arena that looks very much like a bubble. There are stablecoins, cryptocurrencies that are supposed to be less volatile, pegged to something like the US dollar. There’s also the burgeoning world of decentralized finance, or DeFi, which tries to replicate a lot of the financial system but without intermediaries, and there are decentralized autonomous organizations, or DAOs, essentially internet collectives. Now, much of this is falling under the still-nascent umbrella of Web3, a relatively fuzzy reimagining of the internet on blockchains.

This art of method was understood by Ramus and Ramists as its own efficacious art of memory. InScholae in liberales artes, Ramus is explicit about his disdain for the visual mnemonic rules suggested byclassical sources.“The art of memory,”he counters,“consists entirely in division and composition. If weseek then an art which will divide and compose things, we shall find the art of memory”(qtd. in Yates 233).Ramus thus enfolds the fourth canon into his methodical framework, linking memorization of content withits“division and composition,”that is, with its organization.

In this week’s leaked draft of a Supreme Court opinion overturning Roe v. Wade, Justice Samuel Alito wrote, “The inescapable conclusion is that a right to abortion is not deeply rooted in the Nation’s history and traditions.” Yet abortion was so “deeply rooted” in colonial America that one of our nation’s most influential architects went out of his way to insert it into the most widely and enduringly read and reprinted math textbook of the colonial Americas—and he received so little pushback or outcry for the inclusion that historians have barely noticed it is there. Abortion was simply a part of life, as much as reading, writing, and arithmetic.

The justices held their final arguments of the current term on Wednesday. The court has set a series of sessions over the next two months to release rulings in its still-unresolved cases, including the Mississippi abortion case.

There are project layouts that put implementation files and test files together.

If you want to organize said migrations in their purpose you'll probably have a folder for the struture ones and another for the data ones.

db/migrate/core/user/

The second reason might support positive change. The existence of tokens and decentralization means that it’s possible to build resilient open source communities where early contributors and supporters benefit handsomely over time. No one owns these communities, and we can hope that these communities will work hard to serve themselves and their users, not the capital markets or other short-term players.

Because of the constantly growing number of volumes, and to minimize coordination issues, Gottfried van Swieten emphasizes a set of instructions for registering all the books of the court library. Written instructions are by no means common prior to the end of the eighteenth century. Until then, cataloging takes place under the supervision of a librarian who instructs scriptors orally, pointing out problems and corrections as every-one goes along.

There are endless ways of organizing your notes—by book, by author, by topic, by the time of reading. It doesn’t matter which system you use as long as you will be able to find the notes in the future.

Like the spatial hierarchies presented in the Philosophia botanica, he wanted asimple form of linear order that allowed him to access his sheets quickly. Such a desire led himto reject the spatial divisions featured in many contemporary curiosity and medical cabinets, thatis, closed drawers that were stacked in multiple columns. This rejection was probably linked tothe fact that he had already seen a better way forward in the form of filing systems that werephysical instantiations of commonplace divisions used so often in books.

This works nicely wherever we show authors, but after we deploy to production, the folks from other parts of the world won’t get notified anymore about their songs. Mistakes like these are easy to make when using concerns.

This compatibility simply means that you can have a .githooks folder at the root of your project, where you can organize your individual hooks into folders.

We’ve broken our project up into three different types of packages: apps which are preact apps intended to be bundled and deployed somewhere, modules which are plain npm packages for node/browsers and do not bundle their dependencies, and workers which are either Worker or ServiceWorker scripts entirely bundled up with no imports or exports. We don’t have to keep these three types of packages separated, but it helps us navigate around.

Most of the matchers provided by this gem are useful in a Rails context, and as such, can be used for different parts of a Rails app: database models backed by ActiveRecord non-database models, form objects, etc. backed by ActiveModel controllers routes (RSpec only) Rails-specific features like delegate

A litmus test on whether an option belongs to adapter config or kit config, would be to ask whether the option becomes irrelevant when you switch the adapter to static.

CSS seems like the right place to put visual information. On the other hand, few would argue that image "src" should not be specified as an attribute and the height/width seem as tied to the binary image data as the "src" is.

Famously, he found many of the answers in state, local, and even neighborhood institutions. He wrote approvingly of American federalism, which “permits the Union to enjoy the power of a great republic and the security of a small one.” He liked the traditions of local democracy too, the “township institutions” that “give the people the taste for freedom and the art of being free.” Despite the vast empty spaces of their country, Americans met one another, made decisions together, carried out projects together. Americans were good at democracy because they practiced democracy. They formed what he called “associations,” the myriad organizations that we now call “civil society,” and they did so everywhere:Not only do [Americans] have commercial and industrial associations in which all take part, but they also have a thousand other kinds: religious, moral, grave, futile, very general and very particular, immense and very small; Americans use associations to give fêtes, to found seminaries, to build inns, to raise churches, to distribute books, to send missionaries to the antipodes; in this manner they create hospitals, prisons, schools … Everywhere that, at the head of a new undertaking, you see the government in France and a great lord in England, count on it that you will perceive an association in the United States.

As of May 24, 2016, antimicro has moved from https://github.com/Ryochan7/antimicro to https://github.com/AntiMicro/antimicro. Additionally, project management has passed from Travis (Ryochan7) to the AntiMicro organization due to Travis having other interests and priorities.

Another thing I don’t like: our asset behavior is decoupled from the assets. If you’re mucking around in your app/assets folder, then you have to first know that such a config exists, and then hunt it down in a totally different config folder. It would be nice if, while we’re working in asset land, we didn’t have to mentally jump around.

An activity is a high-level concept to structure code flow

Whether this is the life-cycle of a <user> entity or just a sign-up function, it has to be defined and coded somewhere.

Trailblazer strikes when it comes to organizing business code.

In the past 1 ½ years something weird happened: a real core team formed around the Trailblazer gems. I say “real” because in the past 15 years of OSS, I’ve had people come and go, being of great help but never staying and taking over long-term responsibilities - which I found to be the pivotal element of a core team. Eventually, those kids convinced me to start the Trailblazer organization on Github and move over all “apotonick gems”. Over the course of time, I saw myself giving away that aforementioned responsibility with a smile on my face, adding owners and collaborators to gems, yes, even giving away entire gems, letting people work on documentation and just trusting someone and their skills. I have no words to describe how good that feels!

Trailblazer extends the conventional MVC stack in Rails. Keep in mind that adding layers doesn't necessarily mean adding more code and complexity. The opposite is the case: Controller, view and model become lean endpoints for HTTP, rendering and persistence. Redundant code gets eliminated by putting very little application code into the right layer.

Trailblazer offers you a new, more intuitive file layout in applications.

Instead of grouping by technology, classes and views are structured by concept, and then by technology. A concept can relate to a model, or can be a completely abstract concern such as invoicing.

ActiveInteraction plays nicely with Rails. You can use interactions to handle your business logic instead of models or controllers.

Why is all this interaction code better? Two reasons: One, you can reuse the FindAccount interaction in other places, like your API controller or a Resque task. And two, if you want to change how accounts are found, you only have to change one place.

It must be called during the component's initialisation (but doesn't need to live inside the component; it can be called from an external module).

Keep your patches colocated with the code that depends on them.

It seeks to empower us, help us organize, and improve our communication.

a co-op of worker-owners, and hopefully one day a platform co-op (communities owning themselves? absurd)

Our team is building open source community tools and Svelte fits our identity as an independent labor of love with an organic community.

in which business logic (JavaScript) is collocated with styles (CSS) and markup (HTML-like templating syntax).

The project organization is a bit weird because we have a mono-repository that contains projects and libraries. The projects are grouped by company and by browser / server / universal.

In my opinion, deleting a user is not a function executed by an item on itself but is a function done by the holder of the array. So in your case you would be better of moving the deleteUser up to App.

A resource route maps a number of related requests to actions in a single controller.

This simplifies maintenance and keeps things clean by allowing related code to be grouped before inclusion elsewhere.

withindex.js, we have a single source of truth, giving fine grained control on what we expose to the outside world.

import statements will become much smaller, as we will be importing stuff from less files. For example AbstractNode.js has only on import statement now, where it had two before.

The reason that this solves our problem is: we now have full control over the module loading order. Whatever the import order in internal.js is, will be our module loading order.

Here are few, real-life commits of refactorings that make use of this solution:

The crux of this pattern is to introduce an index.js and internal.js file.

Yeah I see what you're saying. In my case, I had a group of classes that relied on each other but they were all part of one conceptual "module" so I made a new file that imports and exposes all of them. In that new file I put the imports in the right order and made sure no code accesses the classes except through the new interface.

In some cases, I could also create a component without any <script> tag at all. So in that way, I could actually bulk up the logic in one place if I could get some help from the #with block.

Separately, I wondered about having a central registry of warnings, since they're a bit scattered around at the moment. That way, we could check that someone wasn't trying to ignore a non-existent warning.

took advantage of your imposed staycation

I'm also persuaded by the arguments that it will be easier to track stuff down by co-location.

I also think this would be great in terms of colocation. If I need some intermediate result I no longer have to jump between script and markup.

I'm persuaded that co-locating just this one type of logic will be useful.

I like this, mostly because it allows me to write small components without creating another separate sub-component for holding the value simple computation. I get annoyed every time I need to create a component just to hold a variable, or even move the computation away from the relevant location. It reminds me of the days where variables in C had to be declared at the top of the function.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

When I say that my experience is that it means it's time to split up your components, I guess I mean that there tends to be a logical grouping between all the things that care about (for example) sqr_n, and in Svelte, logical groupings are expressed as components.

Keep the local state isolated.Think about which state is local to a particular UI representation — and don’t hoist that state higher than necessary.

Principle #8: Organize your notes by context, not by topic

instead of filing things away according to where they came from, you file them according to where they’re going. This is the essential difference between organizing like a librarian and organizing like a writer.

I took the same approach with _layout.svelte and not just for the svelte-apollo client. Except I put all of that setup into another module (setup.js) and imported from _layout. I just couldn't stomach having all that code actually in my _layout file. It's for layout, supposedly, but it's the only component that is a parent to the whole app.

I got this working by using _layout.svelte as the point to initialise and set the Client we can then use getClient in each route that uses this layout.

The RFC is more appropriate because it does not allow a parent to abritrarily control anything below it, that responsibility still relies on the component itself. Just because people have been passing classes round and overriding child styles for years doesn't mean it is a good choice and isn't something we wnat to encourage.

there is one major weakness to this approach and to scoped CSS: organization gets very hard – you end up with styles everywhere!

Keeping the CSS with the HTML for organization may have value however.

Because of that, it's easy to end up in a situation where the styles for a given piece of markup are defined far away (in terms of number of lines) from the markup itself, which reduces the advantage of having styles and markup co-located in the first place.

but adding logic to the <script> is unfortunate

It’s become increasingly common to divide code into components, rather than by file type. React, for example, allows for the collocation of a components markup and JavaScript. In Svelte, this is taken one logical step further: the Javascript, markup and styling for a component can all exist together in a single `.svelte`​ file