Because the official images are intended to be learning tools for those new to Docker as well as the base images for advanced users to build their production releases, we review each proposed Dockerfile to ensure that it meets a minimum standard for quality and maintainability. While some of that standard is hard to define (due to subjectivity), as much as possible is defined here, while also adhering to the "Best Practices" where appropriate.

it is highly encouraged to switch to zeitwerk mode because it is a better autoloader

though we recommend Jest as our preference, the library works with any framework

Using ~ is deprecated and can be removed from your code (we recommend it)

ℹ️ We highly recommend using Dart Sass.

⚠ Node Sass does not work with Yarn PnP feature and doesn't support @use rule.

The Rails server will also compile your assets if the dev server is not running, but this is much slower vs running separate processes and not recommended.

However, this style is not recommended in new code, unless you are often passing a Hash as a positional argument, and are also using keyword arguments

https://github.com/rycus86/githooks is a really option for managing hooks It is... safe (it uses an opt-in model, where it will ask for confirmation whether new or changed scripts should be run or not (or disabled)) configurable handles a lot of the details for you lets you keep your hooks nicely organized. For example:

This meant that we owned both sides of the product implementation. For unit testing on the frontend, we stayed with Angular’s suggestion of Jasmine. For unit testing on the backend, we went with rspec-rails. These worked well since unit tests don’t need to cross technology boundaries.

Or if you're looking for a core extension that adds this to the Array class, I'd recommend the facets gem (require 'facets/array/average'). Then you can just do array.average. And, from looking at the source, it turns out they do the exact same thing as the instance_eval approach above. The only difference is that it's implemented as a method—which of course already has self pointing to itself—instead of a block): def average; return nil if empty?; reduce(:+) / length.to_f; end Main advantage of this is that it's even more concise/readable and it handles the empty? case.

I've been using (and recently, contributing slightly to) Git for well over a decade. I don't have any single thing I'd specifically recommend at this point, but if you're looking for a decent book on Git, the Pro Git book has a bunch of plus-es: it's on line and kept up to date, it's free, and it's correct (unlike far too many online tutorials). There is also Think Like (a) Git, which covers most of what's missing from Pro Git.

These example are for Rails applications, but there is no dependency on Rails for using this gem. Most of the examples are applicable to any Ruby application.

The use of U+212B 'Angstrom sign', which was encoded due to round-trip mapping compatibility with an East-Asian character encoding, is discouraged, and the preferred representation is U+00C5 'capital letter A with ring above', which has the same glyph.

Mir wurde das Spiel glücklicherweise empfohlen und möchte es weiterempfehlen :)

Your validation functions should also treat undefined and '' as the same. This is not too difficult since both undefined and '' are falsy in javascript. So a "required" validation rule would just be error = value ? undefined : 'Required'.

This isn't really a downside to React; one of React's strengths is that it lets you control so much and slot React into your environment

Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.

I’d say if the form is short and an obvious pattern (like sign up or log in), you could use the placeholder visual pattern, but use real labels instead.

It can also be included as individual modules, i.e. Hashie::Extensions::MethodReader, Hashie::Extensions::MethodWriter and Hashie::Extensions::MethodQuery.

Feel free to pick and choose what you need for your applications.

The bare bones operation without any Trailblazery is implemented in the trailblazer-operation gem and can be used without our stack.

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

Only use what you like.

you can pick which layers you want. Trailblazer doesn't impose technical implementations

@adisos if reform-rails will not match, I suggest to use: https://github.com/orgsync/active_interaction I've switched to it after reform-rails as it was not fully detached from the activerecord, code is a bit hacky and complex to modify, and in overall reform not so flexible as active_interaction. It has multiple params as well: https://github.com/orgsync/active_interaction/blob/master/spec/active_interaction/modules/input_processor_spec.rb#L41

References Garrison, D. Randy, Terry Anderson, and Walter Archer. “Critical inquiry in a text-based environment: Computer conferencing in higher education.” The internet and higher education 2, no. 2-3 (1999): 87-105. Orlov, George, Douglas McKee, James Berry, Austin Boyle, Thomas DiCiccio, Tyler Ransom, Alex Rees-Jones, and Jörg Stoye. “Learning During the COVID-19 Pandemic: It Is Not Who You Teach, but How You Teach.” NBER Working Paper 28022 (2020). Rienties, Bart, and Bethany Alden Rivers. “Measuring and understanding learner emotions: Evidence and prospects.” Learning Analytics Review 1, no. 1 (2014): 1-27.

But in most cases, I strongly recommend you use padding inside a box, rather than margins, to ensure you don’t have this problem.

It is pretty much what Ubuntu 20.04 could have been, but isn't.

Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.

There are actually 3 other libraries that implements material in svelte, i hope this to become the community favorite because using MDC underneath it implements correctly Material guidelines.

If you have a better/simpler/"more official" solution, I'd still love to see it!

Start by reading this post (Final Form + Fonk)

Concepts in Thermal Physics 2nd Edition by Stephen J. Blundell (Author), Katherine M. Blundell (Author)

Mathematical Methods for Physics and Engineering: A Comprehensive Guide 3rd Edition by K. F. Riley (Author), M. P. Hobson (Author), S. J. Bence (Author)

I recommend folks use https://github.com/shama/bel instead of this package; we've been working hard on it for the past two years to make sure it has all the features you could want to write inline HTML. Hope it's good; closing for now!

Moreover, React team even removed the “highlight updates” feature from dev tools because people used to obsessively haunt wasted renders with no reasoning behind it

mdsvex is a Svelte preprocessor and is the preferred way to use this library.

Disclaimer: I’m new to Svelte so this isn’t so much a recommendation as it is a “I guess this is a way to do it 🤷‍♂️”

People assume any advocacy for things they're not personally stoked about is "shilling".

For the past couple of years in particular however, I’ve stopped using Webpack to develop them, opting instead to use Rollup as my primary bundler for apps.

In these cases, a recursive setTimeout() pattern is preferred:

Although specifying the ⚡ is the recommended approach

you will find better treatise for all individual topics covered; for example:- What we understand about the brain is essentially covered by Tim Urban in his article "Neuralink and the Brain's Magical Future" in, I might add, more entertaining manner. Alternatively, for a much more in-depth look, look at the book "Principles of Neural Design"- The short time Oliveira spends on superintelligence is better covered by Bostrom in his book "Superintelligence", which Oliveira references- What an algorithm is and what can be computed is better covered by "What algorithms want"- The "common sense" aspect of AI is better covered by "Common Sense, the Turing Test and the Quest for Real AI"- On the title promise, how science is "redefining humanity", the Digital Mind is relatively light on, aside from broadly listing topics that we need to think about like ownership and rights. For a (much) further-taken discussion on this, look at Yuval Noah Harari's Homo Deus, for example.

If you need a tool to backup your documents and files please take a look at the excellent BackInTime application which is more configurable and provides options for saving user files.

Here are my tools of choice for testing React apps:react-test-renderer for snapshot unit testingAct API for unit testing React componentsJest for unit and integration testing of JavaScript codeCypress for end to end / ui testing