There is no flag forpoor rights, after all.

Why the name "CLOG?" Aren't there enough catchy acronyms? Yes! Agreed. We don't need more acronyms. Originally, I used the generic term "log," but quickly realized that whenever I wanted to search for my logs, I would inevitably bring up notes related to "blogs," "logging," "logical," "logrolling," "slog," "flog," and basically any word ending in "-ology." It was a mess. Since I am not a wooden shoe maker, my vault is relatively free of "clog" derivatives.

“e mind is for having ideas,not holding them.”7 Taken from David Allen’s seminal text on productivity,Getting ings Done, this idea, above all others, binds lawyers to Luddites,helping thousands who struggle to put ideas into action.

whoever it may be, if he does his workwelly then that work will look very easy.

Because the substantial surplus expropriated by the few allowed them to invest their time into developing a state, military, and cultural apparatus that reproduced their exploitative position of privilege, the collective consciousness ruling this sociopolitical body tended to comprehend its free citizenship abstractly, as if a natural given, with little consciousness of the contribution of the laboring body

Free and open-source licenses use these existing legal structures for an inverse purpose

I enjoyed this podcast but got the feeling they see PKM as a kind of grueling Fordist production line. The process in your book seems a lot less like a grind and a lot more like fun!

For years developers have followed the same arcane dozen steps to create a long-lived daemon process on Unix-based systems. These steps were state of the art in 2000 but they are no longer best practice today.

Modern parallel languages have much easier to use execution models. The thread model was one of the original parallel execution models, which may account for why it has persisted despite being difficult to use.

Kroustgrafologist Greek kroustiki is Percussion Graf for writing Ologist for study

And what I assume you shall assume, For every atom belonging to me as good belongs to you.

Monopoly is not played on a cartesian plane. It's played on a directed circular graph. Therefore, it is inappropriate to use the Euclidean distance metric to compare the distances between places on the board. We must instead use minimum path lengths. Example: If we used Euclidean distance, then you would have to agree that the distance between, say, Go and Jail is equal to the distance between the Short Line and the Pennsylvania Railroad. Clearly, this is not the intention. In your example, the "nearest railroad" would be the railroad square having the shortest path from wherever you stand. With the game board representing a directed graph, there are no "backwards" paths. Thus, the distance from the pink Chance square to the Reading railroad is not 2. It's 38.

human beings don't do that we understand that the chair is not a specifically shaped object but something you consider and once you understood that concept that principle you see chairs everywhere you can create completely new chairs

How can I wait for container X before starting Y? This is a common problem and in earlier versions of docker-compose requires the use of additional tools and scripts such as wait-for-it and dockerize. Using the healthcheck parameter the use of these additional tools and scripts is often no longer necessary.

Bind mounting your host's daemon socket is safer, more flexible, and just as feature-complete as starting a dind container.

As of right now the full build takes over an hour to run, and this makes cycling for PRs and quick iterative development very difficult.

It will be seen from the foregoing that care isrequired in the appKcation of the card system,and that neglect must sooner or later lead to failure. There wasindeed a time when it seemed doubtful whether the card systemwould survive the first attempts. It was even tried and abandonedby some. These early failures were in the main due to the absenceof expert labour and to the higher order of accuracy required ascompared with the book system. The systems were not thenplanned out with that care that is bestowed upon them now. Onesystem would be started and presently there would be a decisionto alter it so as to fall in with riper experience. In the absenceof one system consistently adhered to the files soon got into achaotic condition until at last they had to be abandoned, for infact they had become useless.

Many GTDers have fallen for The Toolbox Fallacy.

Classification is the process of grouping organisms together either based on features they have in common, or based on their ancestry, or sometimes both. This results in the arrangement of living things into groups.

Prepare to transition away from Google Sync Google Sync doesn’t support OAuth authentication, 2-factor authentication, or security keys, which leaves your organization’s data less secure.

a blog post that deals with integrating The Today System into the Bullet Journal Method!

Autoloading in Rails was based on const_missing up to Rails 5. That callback lacks fundamental information like the nesting or the resolution algorithm being used. Because of that, Rails autoloading was not able to match Ruby's semantics, and that introduced a series of issues. Zeitwerk is based on a different technique and fixed Rails autoloading starting with Rails 6.

may define Foo, instead of reopen it

Since require has global side-effects, and there is no static way to verify that you have issued the require calls for code that your file depends on, in practice it is very easy to forget some. That introduces bugs that depend on the load order.

In API design, exceptional use cases may justify exceptional support. You design for the common case, and let the edge case be edge. In this case, I believe lib deserves ad-hoc API that allows users to do exactly that in one shot:

ActiveRecord::Base.normalizes declares an attribute normalization. The normalization is applied when the attribute is assigned or updated, and the normalized value will be persisted to the database. The normalization is also applied to the corresponding keyword argument of query methods, allowing records to be queried using unnormalized values.

Are you spending too much time transferring uncompleted tasks to tomorrow’s schedule?

What do you do for a calendar? I'm considering moving from a moleskine GTD system to index cards for reasons you mention (waste paper, can't re-order), but love my 2-year calendar at the front

three things happened

The main usage difference is that dependency can be used in a second sense as a "concrete" noun to mean a person or thing which depends on something/someone else. But note that in the programming context it's not uncommon to see it used to mean a software resource upon which some piece of software depends (i.e. - reversing the need/provide relationship).

And as others have pointed out, there is potential for ambiguity: if A is dependent on B, then a dependence or dependency (relationship) exists; but referring to either A or B as the dependency demands context.

To take advantage of this wonderful opportunity, put #! /bin/sh at the left margin of the first line of your shell scripts.

Guys and gals, we are selling out our stock and closing the Capturewallet shop. This is just a heads-up that when we shortly are sold out - we will not restock. Thanks for all of you that have bought from us since 2019! It's been a treat to serve the GTD community!

In fact, it might be good if you make your first cards messy and unimportant, just to make sure you don’t feel like everything has to be nicely organized and highly significant.

Zettelkasten in one or several language(s)? .t3_15wo3f2._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }

I make a file named: app/models/active_storage/attachment.rb. Because it's in your project it takes loading precedence over the Gem version. Then inside we load the Gem version, and then monkeypatch it using class_eval: active_storage_gem_path = Gem::Specification.find_by_name('activestorage').gem_dir require "#{active_storage_gem_path}/app/models/active_storage/attachment" ActiveStorage::Attachment.class_eval do acts_as_taggable on: :tags end The slightly nasty part is locating the original file, since we can't find it normally because our new file takes precedence. This is not necessary in production, so you could put a if Rails.env.production? around it if you like I think.

Please do not use the issue tracker for personal support requests. Stack Overflow or GitHub Discussions is a better place for that where a wider community can help you!

I think we have a responsibility not only to ourselves, but also to each other, to our community, not to use Ruby only in the ways that are either implicitly or explicitly promoted to us, but to explore the fringes, and wrestle with new and experimental features and techniques, so that as many different perspectives as possible inform on the question of “is this good or not”.

If you’ll forgive the pun, there are no constants in programming – the opinions that Rails enshrines, even for great benefit, will change, and even the principles of O-O design are only principles, not immutable laws that should be blindly followed for the rest of time. There will be other ways of doing things. Change is inevitable.

It is unfortunate that the German word for a box of notes is the same as the methodology surrounding Luhmann.

If you implement this system using the user table you risk impatient users requesting a second code and them arriving out of order.

This leads to an override of the controller as well

‘‘I think it lets us be more thoughtful and more deliberate about safety issues,’’ Altman says. ‘‘Part of our strategy is: Gradual change in the world is better than sudden change.’’

Finding good names is quite difficult. Single words are also almost always better than combined names, even though one is a bit limited with single words alone. There are exceptions though. For example .each_with_index or .each_index are good names, IMO.

People know it’s bad but not how bad. This gap in understanding remains wide enough for denialists and minimisers to legitimise inadequate action under the camouflage of empty eco-jargon and false optimism. This gap allows nations, corporations and individuals to remain distracted by short-term crises, which, however serious, pale into insignificance compared with the unprecedented threat of climate change.

The ID suffix was added because I use external tools to add notes to my vault so I needed a means to ensure there would never be a collision. For example, Alfred. If I accidentally typed the name of a note that already exists into it I didn’t want it to accidentally overwrite an existing note,

Post a publicly viewable comment on the MOC asking why you haven't received it yet

Result of lots of searching on net is that pre-checkout hook in git is not implemented yet. The reason can be: There is no practical use. I do have a case It can be achieved by any other means. Please tell me how? Its too difficult to implement. I don't think this is a valid reason

Since Rails creates callbacks for dependent associations, always call before_destroy callbacks that perform validation with prepend: true.

That tends to be the biggest cop out excuse for libraries. Just do a major version release. The fact this library lies about the encodingis extremely problematic and causes numerous bugs. Any program currently using this library is already incorrect because of this behavior. Actually exposing the problem makes it easier for people to fix.

Agree, but we're stuck with API compatibility for a good while.

Thinking it might be about performance is plain wrong for at least two reasons. Please read this info about the performance aspect

In this case, if the constant Admin::User was already loaded at the time Admin::UserManager.all was called, then it would return Admin::User objects.However, if Admin::User was not yet auto-loaded, but User was, Admin::UserManager.all would instead return User objects!

So when configuring Capybara, I'm using ignore_default_browser_options, and only re-use this DEFAULT_OPTIONS and exclude the key I don't want Capybara::Cuprite::Driver.new( app, { ignore_default_browser_options: true, window_size: [1200, 800], browser_options: { 'no-sandbox': nil }.merge(Ferrum::Browser::Options::Chrome::DEFAULT_OPTIONS.except( "disable-features", "disable-translate", "headless" )), headless: false, } )

The lowest strata represents Generative ambiguity. Here, words are used as symbols for ideas that are very hard to express; an individual gives a name to a nebulous collection of ideas or thoughts. They struggle to make this approach make sense to others.

And David Allen was there at the beginning. He had this idea of full capture where he said all of your tasks should be a trusted system that you review regularly, not in your head. He actually adapted that idea from a previous business thinker named Dean Acheson, unrelated to President Truman’s Secretary of State, same name, different person, who had first developed, I believe in the 1970s, this notion of full capture and David Allen expanded it.

This quadrant is busywork at scale. It’s the domain of productivity gurus, shiny tech tools (like Superhuman, Notion or Hey.com), Zapier automations, Text Expanders and the budding no-code movement.

Yes, it was right, but nowadays Dockerfiles are not specific to Docker. Dockerfiles also work with Buildah & Podman (and there might be other ones in the future) and they have generalized the naming: “Containerfile.”

Synchronously waiting for the specific child processes in a (specific) order may leave zombies present longer than the above-mentioned "short period of time"

Do yourself and your peers a favor, write code with them in mind.

Also, the chances of breaking something are really high, because not even you remember how the code actually works.

Filter gives me the impression of inclusion... so if I filter by fruits, I expect to see apples, oranges, and bananas. Instead, this is more like filter out fruits... remove all the fruits, and you're left with the rest. Filter in/out are both viable. One means to include everything that matches a condition, and the other is to exclude everything that does not match a condition. And I don't think we can have just one.

Multiple different people have been discussing multiple different problems, and asking for examples of the other problems, talking past each other and generally this thread got to an unreadable point due to this confusion.

git -c log.follow= log: that will unset log.follow, just for that one git log instance.

I would not change the project structure to accommodate Docker (or any build tools).

The interaction operator strict requires a strict sequencing (order) of the operands on the first level within the combined fragment

The interaction operator seq means that the combined fragment represents a weak sequencing between the behaviors of the operands.

Title for My Book

I just learned today that extend apparently doesn't override class methods that are already defined, even though the extend happens later:

Looking for books with wider margins for annotations and notes

It's a great way to test various limits. When you think about this even more, it's a little mind-bending, as we're trying to impose a global clock ("who is the most up to date") on a system that inherently doesn't have a global clock. When we scale time down to nanoseconds, this affects us in the real world of today: a light-nanosecond is not very far.

I think actually the most critical component is going to be leveraging existing security mechanisms that have been built for resilience and incorporating those into these devices, which is actually what I'm building right now. That's what Thistle Technologies is doing, we're trying to help companies get to that place where they've got modern security mechanisms in their devices without having to build all the infrastructure that's required in order to deliver that. 

4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.

Defects found in peer review are not an acceptable rubric by which to evaluate team members. Reports pulled from peer code reviews should never be used in performance reports. If personal metrics become a basis for compensation or promotion, developers will become hostile toward the process and naturally focus on improving personal metrics rather than writing better overall code.

Interestingly, Rails doesn't see this in their test suite because they set this value during setup:

Create a new controller to override the original: app/controllers/active_storage/blobs_controller.rb

Are there relevant IPs buried in other projects you’ve worked onin the past?

Douglas Adams noted, "Capital letters were always the best way of dealing with things you didn't have a good answer to."

We document the order of hooks, but I don't think we document where in that order we integrate Rails helpers which makes this confusing, I do sort of think this is a bug but as we use RSpec to integrate Rails here and RSpec Core has no distinction that matches before / after teardown its sort of luck of the draw, we could possibly use prepend_after for Rails integrations which would sort of emulate these options.

The lateral keyword allows us to access columns after the FROM statement, and reference these columns "earlier" in the query ("earlier" meaning "written higher in the query").

This latter equivalence does not hold exactly when more than two tables appear, because JOIN binds more tightly than comma. For example FROM T1 CROSS JOIN T2 INNER JOIN T3 ON condition is not the same as FROM T1, T2 INNER JOIN T3 ON condition because the condition can reference T1 in the first case but not the second.

A LATERAL item can appear at top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that are on the left-hand side of a JOIN that it is on the right-hand side of.

This allows them to reference columns provided by preceding FROM items.

All known use cases of require_dependency have been eliminated with Zeitwerk. You should grep the project and delete them.

Rails 7.0 will aim to give you a default setup based on import maps, and leave the Webpacker approach as an optional alternative.

NVIDIA periodically drops older cards off of its support matrix for NVENC/NVDEC, even if they do have the required hardware. This makes it appear, at first glance to current information sources, that Kepler GPUs do not support NVENC, so we responded as such.

The reason for the new name is that the "dist-upgrade" name was itself extremely confusing for many users: while it was named that because it was something you needed when upgrading between distribution releases, it sounded too much as though it was only for use in that circumstance, whereas in fact it's much more broadly applicable.

The danger of working at "internet time" is that hasty decisions may be poor, and rapid changes may cause troubling turbulence for many users.

Dispatch a custom event. This differs from Svelte's component event system, because these events require a DOM element as a target, can bubble (and do by default), and are cancelable with event.preventDefault(). All SMUI events are dispatched with this instead of Svelte's createEventDispatcher.

Checks are usually done in this order: 404 if resource is public and does not exist or 3xx redirection OTHERWISE: 401 if not logged-in or session expired 403 if user does not have permission to access resource (file, json, ...) 404 if resource does not exist or not willing to reveal anything, or 3xx redirection

Google/gmail calls apps that don't support OAuth2 "less secure". But, that doesn't make them insecure. So what it means is gmail's meaning of LessSecureApp is basically anything that doesn’t use OAuth2.

existe una mayor probabilidad de contratación si se cuenta con una carrera universitaria.

Manually reorder the reactive declaration statements, especially when there's an implicit dependency of the order of execution.

if you put the reactive statement $: validate(inputValue); after the function updateInputValue declaration, it's working as expected:

you can define locally parse and it should take precedence over the one in the library: interface JSON { parse(text: string, reviver?: (key: any, value: any) => any): unknown; }

Object.hasOwn() is recommended over hasOwnProperty(), in browsers where it is supported.

serverFetch name is unclear. That the docs need to say in bold that it's external is a bit of a code smell.

Rename to externalFetch. That it runs on the server is already implied by it being located in hooks

Inflections go the other way around.In classic mode, given a missing constant Rails underscores its name and performs a file lookup. On the other hand, zeitwerk mode checks first the file system, and camelizes file names to know the constant those files are expected to define.While in common names these operations match, if acronyms or custom inflection rules are configured, they may not. For example, by default "HTMLParser".underscore is "html_parser", and "html_parser".camelize is "HtmlParser".

They are deliberately dumbing the browser down further and further and it'll probably end up eventually becoming completely unuseable because of this.

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.