jewel beetle
for - example - jewel beetle - simple hacks over seeing the truth - jewel beetle tries to mate with dimple on glass beer bottle - it doesn't use any other signals to help it distinguish between - the beer bottle dimple and - a real female jewel beetle
This typewriter was quite grimy, so I removed the shell (fairly challenging) and gave it a bath in an ultrasonic cleaning tank. Mitch Hamm alerted me that such tanks, big enough to dip a portable while keeping its keys out of the water, are now available for a mere $150 or so. Here’s the Royal undergoing what sounds like electroshock therapy, but is really just a micro-agitated bath. Concentrated Simple Green Industrial Cleaner & Degreaser was added to hot water in a 1:20 ratio.
https://typewriterrevolution.com/a-green-machine/
Richard Polt's experience in cleaning a Royal Portable with an ultrasonic cleaning tank with Simple Green in a 1:20 ratio.
Royal Futura 800 Typewriter Plastic Key Top White Crud Removal Cleaning Servicing by [[Phoenix Typewriter]]
For the white, crusty out gassing (or off gassing) on plastic typewriter keys, Duane recommends a round or two of Simple Green with a stiff bristle brush. Follow this up with a scrub down using WD-40 to displace the water from the Simple Green and then follow up with denatured alcohol, which is safe on plastics, and a wipe down with a rag to dry.
I think the fact that it's so simple to add, makes the case to just keep it in userland.
The goal of Lucia v3 was to be the easiest and cleanest way to implement database-backed sessions in your projects. It didn't have to be a library. I just assumed that a library will be the answer. But I ultimately came to conclusion that my assumption was wrong. I don't see this change as me abandoning the project. In fact, I think it's a step forward. If implementing sessions wasn't easy, I wouldn't be deprecating the package. But why wouldn't a library be the answer? It seems like a such an obvious answer. One word - database. I talked about how database adapters were a significant complexity tax to the library. I think a lot of people interpreted that as maintenance burden on myself. That's not wrong, but the bigger issue is how the adapters limit the API. Adapters always felt like a black box to me as both an end user and a maintainer. It's very hard to design something clean around it and makes everything clunky and fragile, especially when you need to deal with TypeScript shenanigans.
Old school repair guys used a lot of different stuff that's no longer available due to being... Not good. Ha. But naphta was one that's still widely available as white gas aka "coleman/camping fuel" Essentially naphtha with stabilizers to keep it from going bad. Mineral spirits works as well, but naphtha leaves less residue in my experience. Lacquer thinner is good for especially stubborn crap and cleaning slugs, but evaporates really fast and the fumes are no bueno. Alternatively; non toxic degreasing cleaners like simple green are usually my preferred method of cleaning up especially gross machines. Typically very safe on paint finishes and internals, just make sure to keep it off the decals. (It can and WILL erase them if it sits for more than 10 secs) Really though, nothing beats air and a long handled "paint" brush. My air compressor and blow out tube are some of my most cherished tools.
quote from Nashville Typewriter
One of our favorite sayings is: opt in to complexity. We designed Astro to remove as much “required complexity” as possible from the developer experience, especially as you onboard for the first time. You can build a “Hello World” example website in Astro with just HTML and CSS. Then, when you need to build something more powerful, you can incrementally reach for new features and APIs as you go.
Astro was designed to be less complex than other UI frameworks and languages. One big reason for this is that Astro was designed to render on the server, not in the browser. That means that you don’t need to worry about: hooks (React), stale closures (also React), refs (Vue), observables (Svelte), atoms, selectors, reactions, or derivations. There is no reactivity on the server, so all of that complexity melts away.
Reflexivity has been explored on a collective societal level, for example through Ulrich Beck's work on reflexive modernization wherein the unintended consequences of simple modernity motivate a reflexive turn across society, including to science itself: ‘science itself is deconstructed by means of science’
for - further research - Ulrich Beck's research on unintended consequences of simple modernity - SOURCE - paper - Reflexivity as a transformative capacity for sustainability science: introducing a critical systems approach - Lazurko et al. - 2025, Jan 10
the real problem is what we're layering the web on we shouldn't be doing the web over this kind of just simple file distribution system that works over TCP and you have to work really hard to put over anything else we should be putting the web over a distribution system that can deal with the distributed case that is offline first and uh this is are kind of like stats showing the usage of mobile apps versus uh the web and so on so this is a very real real thing
for - quote / insight - We shouldn't be doing the web over this simple file distribution system that works over TCP - Juan Benet - IPFS
Reliability of the init system is paramount so simplicity is a key attribute.
Log to stdout. Shut down on TERM/INT. Reload config on HUP. Provide the necessary config file for your favorite init system to control your daemon.
Let your operating system handle daemons, respawning and logging while you focus on your application features and users.
This makes developing a modern daemon much easier. The init config file is what you use to configure logging, run as a user, and many other things you previous did in code. You tweak a few init config settings; your code focuses less on housekeeping and more on functionality.
Revisiting my first typewriter restoration... by [[Just My Typewriter]]
Interesting to see someone with some broader experience looking back at what they'd done before and describing how they'd do it now.
Olympia SM Typewriter Wash, Scrub Clean Lid Cover, Restore Paint by [[Phoenix Typewriter]]
Simple Green gets off most dirt and nicotine as well as some White Out. Duane uses Nu-Trol Control Cleaner (for electronics) as a mild specialty cleaner for tougher White Out cleaning.
to your point for 00:13:46 every problem there's going to be a solution and AI is going to have it and then for every solution for that there's going to be a new problem
for - AI - progress trap - nice simple explanation of how progress traps propagate
What are some top UX design principles when designing for kids?Some important UX design principles when designing for kids are as follows. Simplicity and clarity Interactive and engaging elements Age-appropriate content Safety and privacy Consistent feedback and rewards
There's 5 in this list and there was 4 in the other - I think Safety and Privacy is the one additional but it's also in my proposal because I am concerned about it too.
Engaging Visuals: Bright, colorful, and appealing visuals are essential to capture a child’s attention and stimulate their creativity.
This is especially important for me, the Applications that have been offered so far by no fee schools locally are not engaging, the visuals looks very outdated, the colours are very dull.
Abstract
结论：预测结果，好于MOST（MO估计系统地低估了湍流通量的大小，改善了与观测值和减小与观测通量偏离的总幅度。）,不同地点的泛化能力 不足：不含物质通量，预测结果待提升，结果因稳定性而异常，不同季节的泛化能力，运用了不易获得的变量（找到最小观测集）
Instance methods Instances of Models are documents. Documents have many of their own built-in instance methods. We may also define our own custom document instance methods. // define a schema const animalSchema = new Schema({ name: String, type: String }, { // Assign a function to the "methods" object of our animalSchema through schema options. // By following this approach, there is no need to create a separate TS type to define the type of the instance functions. methods: { findSimilarTypes(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); } } }); // Or, assign a function to the "methods" object of our animalSchema animalSchema.methods.findSimilarTypes = function(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); }; Now all of our animal instances have a findSimilarTypes method available to them. const Animal = mongoose.model('Animal', animalSchema); const dog = new Animal({ type: 'dog' }); dog.findSimilarTypes((err, dogs) => { console.log(dogs); // woof }); Overwriting a default mongoose document method may lead to unpredictable results. See this for more details. The example above uses the Schema.methods object directly to save an instance method. You can also use the Schema.method() helper as described here. Do not declare methods using ES6 arrow functions (=>). Arrow functions explicitly prevent binding this, so your method will not have access to the document and the above examples will not work.
Certainly! Let's break down the provided code snippets:
In Mongoose, a schema is a blueprint for defining the structure of documents within a collection. When you define a schema, you can also attach methods to it. These methods become instance methods, meaning they are available on the individual documents (instances) created from that schema.
Instance methods are useful for encapsulating functionality related to a specific document or model instance. They allow you to define custom behavior that can be executed on a specific document. In the given example, the findSimilarTypes method is added to instances of the Animal model, making it easy to find other animals of the same type.
methods object directly in the schema options:javascript
const animalSchema = new Schema(
{ name: String, type: String },
{
methods: {
findSimilarTypes(cb) {
return mongoose.model('Animal').find({ type: this.type }, cb);
}
}
}
);
methods object directly in the schema:javascript
animalSchema.methods.findSimilarTypes = function(cb) {
return mongoose.model('Animal').find({ type: this.type }, cb);
};
Schema.method() helper:javascript
animalSchema.method('findSimilarTypes', function(cb) {
return mongoose.model('Animal').find({ type: this.type }, cb);
});
Imagine you have a collection of animals in your database, and you want to find other animals of the same type. Instead of writing the same logic repeatedly, you can define a method that can be called on each animal instance to find similar types. This helps in keeping your code DRY (Don't Repeat Yourself) and makes it easier to maintain.
```javascript const mongoose = require('mongoose'); const { Schema } = mongoose;
// Define a schema with a custom instance method const animalSchema = new Schema({ name: String, type: String });
// Add a custom instance method to find similar types animalSchema.methods.findSimilarTypes = function(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); };
// Create the Animal model using the schema const Animal = mongoose.model('Animal', animalSchema);
// Create an instance of Animal const dog = new Animal({ type: 'dog', name: 'Buddy' });
// Use the custom method to find similar types dog.findSimilarTypes((err, similarAnimals) => { console.log(similarAnimals); }); ```
In this example, findSimilarTypes is a custom instance method added to the Animal schema. When you create an instance of the Animal model (e.g., a dog), you can then call findSimilarTypes on that instance to find other animals with the same type. The method uses the this.type property, which refers to the type of the current animal instance. This allows you to easily reuse the logic for finding similar types across different instances of the Animal model.
I thing you are doing a very subtle mistake which will become fatal in long-term. Your strategy to take small steps that cover as much functionality as possible is reasonable, but it is necessary to be careful, as it leads to a critical state when there is too much little stuff built up without proper structure to support it.
When the relations are implemented in the right way, they will simplify Gitlab, not make it more complex.
Another example are issue boards. They represent elegant use of a good infrastructure — it is all just a smart use of labels. It would be very complex feature without the use of labels.
Issue relations are meant to be the basic infrastructure to build on (at least that is how I meant it when I posted the original feature request). Just like the labels are just a binary relation between a issue and a "label", the relations should be just a ternary relation between two issues and a "label". Then you can build issue task lists on top of the relations like you've built issue boards on top of the labels.
That helps us keep GitLab simple as long as we can.
We already have a very nice example of such tool and its great use: the Board, where labels are used to store metadata and the Board is built above this storage. Do the same with the relations -- simple metadata storage to build on.
One way is to have a very simple model of the same thing like Github and let users decide on the hierarchy of things. If Gitlab really want to go one step further and give users more then its really important simplicity is not killed in the process.
its easy to get lost in complexity here, but i prefer to keep it simple: our *only* problem is overpopulation, which is caused by pacifism = civilization. *all* other problems are only symptoms of overpopulation. these "financial weapons of mass destruction" (warren buffett) have the only purpose of mass murder = to kill the 95% useless eaters. so yes, this is a "controlled demolition" aka "global suicide cult". most of us will die, but we are happy...
financial weapons of mass destruction: the useful idiots believe that they can defeat risk (or generally, defeat death) by centralization on a global scale. they want to build a system that is "too big to fail" and which will "live forever". they use all kinds of tricks to make their slaves "feel safe" and "feel happy", while subconsciously, everything is going to hell in the long run. so this is just another version of "stupid and evil people trying to rule the world". hubris comes before the fall, nothing new. their system will never work, but idiots must try... because "fake it till you make it" = constructivism, mind over matter, fantasy defeats reality, ...
the video and soundtrack are annoying, they add zero value to the monolog.
Recent work has revealed several new and significant aspects of the dynamics of theory change. First, statistical information, information about the probabilistic contingencies between events, plays a particularly important role in theory-formation both in science and in childhood. In the last fifteen years we’ve discovered the power of early statistical learning.
The data of the past is congruent with the current psychological trends that face the education system of today. Developmentalists have charted how children construct and revise intuitive theories. In turn, a variety of theories have developed because of the greater use of statistical information that supports probabilistic contingencies that help to better inform us of causal models and their distinctive cognitive functions. These studies investigate the physical, psychological, and social domains. In the case of intuitive psychology, or "theory of mind," developmentalism has traced a progression from an early understanding of emotion and action to an understanding of intentions and simple aspects of perception, to an understanding of knowledge vs. ignorance, and finally to a representational and then an interpretive theory of mind.
The mechanisms by which life evolved—from chemical beginnings to cognizing human beings—are central to understanding the psychological basis of learning. We are the product of an evolutionary process and it is the mechanisms inherent in this process that offer the most probable explanations to how we think and learn.
Bada, & Olusegun, S. (2015). Constructivism Learning Theory : A Paradigm for Teaching and Learning.
The question is also not about error handling and if the file write fails, exiting with a stack trace is reasonable default behavior because there's not much you can do to recover from that.
Making a property writable adds an order of magnitude in complexity. In the real world it's definitely not realistic for every class to be immutable, but if most of your classes are, it's remarkably easier to write bug-free code. I had that revelation once and I hope to help others have it.
In recent git versions, git restore is supposed to be a "better" way to revert undesired local changes than the overloaded checkout. Great, that sounds reasonable - a nice simple purpose-built tool for a common operation.
https://david.shanske.com/venue/santa-fe-depot/
GWG has now got locations built into the Simple Location Plugin!
This occurs for the child processes, where the entry is still needed to allow the parent process to read its child's exit status: once the exit status is read via the wait system call, the zombie's entry is removed from the process table and it is said to be "reaped".
If you want a queueing system that uses X, use a queuing system that uses X! Sidekiq's mantra is simple and efficient. Redis is both. Abstracting data storage is neither.
This means that when considering the "unevaluatedProperties": false in the root schema, "wheels" has not been evaluated, so unevaluatedProperties applies to it, and therefore validation fails because the false subschema fails by definition against any instance.
a benchmark tells you how slow your code is ("it took 20 seconds to do X Y Z") and a profiler tells you why it's slow ("35% of that time was spent doing compression").
appropriate Key Management
Di Angelo and Salzer (2020) divided wallets into six types.
The main problem here is that the problem itself is a little bit poorly defined.
A key aspect of this library is its simplicity
Think the mere existence of a file is effectively like writing a require call for them, which is executed on demand (autoload) or upfront (eager load).
the C standard — because that would be tremendously complicated, and tremendously hard to use
"the C standard [... is] tremendously complicated, and tremendously hard to use [...] full of wrinkles and [...] complex rules"
This gem is just one concern with one scope. If you want to customize it later you can simply copy the code directly into your project.
FORBIDDEN: Status code (403) indicating the server understood the request but refused to fulfill it. User/agent known by the server but has insufficient credentials. Repeating request will not work, unless credentials changed, which is very unlikely in a short time span.
There's a problem with 401 Unauthorized, the HTTP status code for authentication errors. And that’s just it: it’s for authentication, not authorization. Receiving a 401 response is the server telling you, “you aren’t authenticated–either not authenticated at all or authenticated incorrectly–but please reauthenticate and try again.” To help you out, it will always include a WWW-Authenticate header that describes how to authenticate.
So, for authorization I use the 403 Forbidden response. It’s permanent, it’s tied to my application logic, and it’s a more concrete response than a 401. Receiving a 403 response is the server telling you, “I’m sorry. I know who you are–I believe who you say you are–but you just don’t have permission to access this resource. Maybe if you ask the system administrator nicely, you’ll get permission. But please don’t bother me again until your predicament changes.”
UNAUTHORIZED: Status code (401) indicating that the request requires authentication, usually this means user needs to be logged-in (session). User/agent unknown by the server. Can repeat with other credentials. NOTE: This is confusing as this should have been named 'unauthenticated' instead of 'unauthorized'.
+----------------------- | RESOURCE EXISTS ? (if private it is often checked AFTER auth check) +----------------------- | | NO | v YES v +----------------------- 404 | IS LOGGED-IN ? (authenticated, aka user session) or +----------------------- 401 | | 403 NO | | YES 3xx v v 401 +----------------------- (404 no reveal) | CAN ACCESS RESOURCE ? (permission, authorized, ...) or +----------------------- redirect | | to login NO | | YES | | v v 403 OK 200, redirect, ... (or 404: no reveal) (or 404: resource does not exist if private) (or 3xx: redirection)
When you initially logon with OAuth2, you will be redirect to Google’s sign-in page,. Once you have signed in, Google issues you a special OAuth2 token which is saved in Thunderbird and can be seen in the same place as passwords. So when you next logon to gmail, it is using that unique OAuth ID instead of password.
Actions are deceptively simple yet incredibly powerful.
In your Svelte component, you can then use your store with the special $ prefix syntax, to access the value of the store ('cause the temperature variable is a reference to the store itself, it's just a mean to our end, the result we need is the value):
Stores are essentially some kind of simplified streams (or Observable as they're called in ES), that is they represent a value over time.
Stores are the idiomatic Svelte way when you need to import "reactivity" from your normal JS sources.
export function autofocus(node) { node.focus(); } That's it. This is a legitimate Svelte Action!
Airtable evolves with you and your team, so you can build a solution with increasing sophistication and capability.
function strictIsDog<T extends Dog extends T ? unknown : never>( // like <T super Dog> candidate: Dog | T // if Dog extends T then Dog | T is T ): candidate is Dog { // compiler recognizes that Dog | T can narrow to T return "bark" in candidate; } if (strictIsDog(animal)) {} // okay if (strictIsDog(dog)) {} // okay if (strictIsDog(mixed)) {} // okay if (strictIsDog(cat)) {} // error! // ~~~ <-- Cat is not assignable to Dog
Adding to the accepted answer, if you happen to need to use a type guard against a mixin, you'll get this error too, since the is operator doesn't behave as an implements would.
const isValidMethodForHandler = <T extends { [i: string]: any }>(handler: T) => ( method: string ): method is Extract<keyof T, string> => Object.keys(handler).indexOf(method) !== -1;
Every time filter-repo is run, files are created in the .git/filter-repo/ directory. These files overwritten unconditionally on every run.
Please
The song's title was mentioned in Sly and the Family Stone's hit song "Thank You (Falettinme Be Mice Elf Again)” (1969).
https://genius.com/Sly-and-the-family-stone-sing-a-simple-song-lyrics
That image only contains 200 pixels horizontally, but the browser stretches it to 400px wide or even farther!Luckily, you’ll see there’s an easy “fix” there at the end: our old good friend the width attribute!<img src="example.gif", srcset="example.gif 200w" sizes="(min-width: 400px) 400px, 100vw" width="200" /* <=== TA-DA! */ class="logo">As long as you can specify the width attribute so it reflects the true maximum size of your largest image, you won’t run into this problem of having sizes make your image wider than it naturally should go.
Keep it simple.
It's simple really ... put tests into a shared example that you want multiple things to conform to. Put code into a shared context that you need to include in multiple tests.
Everything about this game is as simple as possible, down to the three main leads, their conversations, and even the plot—it may sound super exciting to go on an expedition under the ruins of a temple to find some ancient advanced machinery; but in reality, the whole thing is like a longer Saturday morning cartoon episode.
# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end
find_field finds by id, name or placeholder text - so find_field('Prefix') should find the element with matching placeholder text rather than needing xpath.
I think the issues/problems specified in the comments are not present with a Hash-only implementation. :) I would be supportive of re-considering this feature just for use with a Hash, where I believe 80% of the real-life use cases would (and do) exist. I have encountered this need before in the wild, but not with Arrays.
Intuitively, a subcategory of C is a category obtained from C by "removing" some of its objects and arrows.
Write modules that do one thing well. Write a new module rather than complicate an old one.
.
Maybe it would be simple to always add that line, and always shift the source maps by 1.
Semantically correct usage of elements means that you use them for what they are meant to be used for.
It means that you're calling something what it actually is.
Output() in combination with Path() allow very simple modelling for alternive routes.
A Monad wraps a value or a computation with a particular context. A monad must define both a means of wrapping normal values in the context, and a way of combining computations within the context.
It’s so simple that I sometimes wonder why it took years to develop it!
The shell process itself is in yet another process group all of its own and so doesn't receive the signal when one of those process groups is in the foreground. It's that simple.
Writing the uniqueness validations yourself is easy so I felt it was better to leave this up to the developer
I've been over the use case for form objects in this post on moving away from fat models but wanted to go into more detail on how and why I use them here. I really believe in the utility of these objects; their ability to abstract and isolate logic in a simple and effective manner is unmatched, IMO.
That's covered by "they must differ only by #where"
All those names of things - topology, complex analysis, and differential geometry - might not sound like much to you now, but you'll soon learn that they're really just describing the shapes of things in our Universe, and the way those shapes change in time and space are explained by things like calculus and chaos theory.
Simple answer: If you need the interface in in another module.
Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.
page is a { host, path, params, query } object where host is the URL's host, path is its pathname, params is derived from path and the route filename, and query is an object of values in the query string.
I like that we don't have to manually parse params/query out of the full request URI. It provides the data that you are most likely to need, in an readily/easily-usable form.
I think the main difference between the two are the way API are served. Some smelte components need you to input big chunk of json as props, while i prefer keep props as primitive types and in the other hand give you different components tags to compose.
My focus is on make the API as simpler as possible to allows easy integration without even reading the docs but keeping and expand current features.
For example, your application should work offline, but it doesn’t mean that you must set-up a background queue or store your data in a persistent storage – a offline message (e.g. “You’re offline, check your network status.”) is enough.
So let's say we pull down evil/foo which is FROM ubuntu followed by RUN apt-get update except with a small surprise included in the image. Subsequent builds using those same commands will be compromised.
However, this coalescing was very complicated, both in the specification and implementations, due to the dynamism of computed property names for accessors. Coalescing was a big source of overhead (e.g., in terms of code size) in polyfill implementations of "Stage 2" decorators.
This is Sass based, and therefore doesn't require Svelte components
Just because we could make Svelte wrapper components for each Material typography [thing], doesn't mean we should.
Compare:
material-ui [react] did make wrapper components for typography.
svelte-material-ui did not.
I don't think the heading/bearing split is as clear-cut as that.
for (var member in myObject) delete myObject[member]; ...would seem to be pretty effective in cleaning the object in one line of code
But checking hasOwnProperty is probably better/safer idea:
for (var prop in obj) { if (obj.hasOwnProperty(prop)) { delete obj[prop]; } }
And I'm all for not adding a gazillion flags to to an elegant library.
But it sounds like the library could use some way to setTouched()
I don't want Svelte to go out of its way to try to catch all these edge cases. It would require lots of fragile heuristics in the compiler. I want a solid compiler I can trust, not something magic but often out of service. I want it the simplest possible.
Wondering how to get field state from multiple fields at once? People coming from Redux-Form might be wondering where the equivalent of Redux Form's Fields component is, as a way to get state from several fields at once. The answer is that it's not included in the library because it's so easy to write one recursively composing Field components together.
but the design pattern is so simple that it takes hardly any effort to implement it on any existing reducer, so I rejected abstraction for abstraction's sake.
Not all application state belongs inside your application's component hierarchy. Sometimes, you'll have values that need to be accessed by multiple unrelated components, or by a regular JavaScript module.
A store is simply an object with a subscribe method that allows interested parties to be notified whenever the store value changes. In App.svelte, count is a store, and we're setting count_value in the count.subscribe callback.
Just like elements can have children... <div> <p>I'm a child of the div</p> </div>...so can components. Before a component can accept children, though, it needs to know where to put them. We do this with the <slot> element.
Good risk management is inherently simple; adding too many complexities increases the likelihood of overlooking the obvious.
Escaping is a subset of encoding, where not all characters need to be encoded. Only some characters are encoded (by using an escape character).
A programming language is Turing complete if you can implement any possible algorithm with it.
Snarkdown exports a single function, which parses a string of Markdown and returns a String of HTML. Couldn't be simpler.
We are very close to full inline components (with css, js logic, and templates).
We get a boilerplate-free API where shared state has the same simple get/set interface as React local state (yet can be encapsulated with reducers etc. if needed).
Solid keeps it simple
Like they tried so hard to make things easy they didn't care that they weren't elegant or simple.
Any variable referenced on the lines marked with $: is marked as a dependency of the derived variable.
However, if you want to create a backend API that is meant to be consumed only by your frontend, then you don't need REST nor GraphQL — RPC, such as Wildcard, is enough.
setContext must be called synchronously during component initialization. That is, from the root of the <script> tag
To make this “if you install me, you better also install X, Y, and Z!” problem easier, peerDependencies was introduced.
Lets not extend the framework with yet another syntax
I'm more likely to use it than alternatives in future projects - it's simple and clean
"AOO is not, and isn't designed to be, the 'super coolest open source office suite with all the latest bells and whistles,'" Jagielski continued. "Our research shows that a 'basic,' functional office suite, which is streamlined with a 'simple' and uncluttered, uncomplicated UI, serves an incredible under-represented community.
A simplified pricing and packaging (PnP) strategy serves customers in the optimal way per the industry best practice. More SKUs lead to a more complex PnP model as a company scales, which eventually causes huge confusion to customers.
Why save sessions as bookmarks? - all the data saved will be there no matter what addon you may use in the feature
And you see the problem, concerns are so simple that they do not deserve a full guide. Concerns are mixins, if you are a Ruby programmer, you already know what a mixin is and their use case to modularize APIs.
From: https://www.kickstarter.com/projects/admagic/rise-of-tribes-beasts-and-bronze
[saved a copy]
Regardless of what or how much you order, this is your flat shipping cost.
I think this goes against the Keep It Simple mentality and the Low Level Of Shame that we should have when we contribute.
whose personal data you collect and process as “controller” (that is the word that GDPR uses for whoever determines the purposes and means of the processing of personal data).
The extra “space” from vertical navigation might encourage some designers to go overboard and clutter the navigation menu; as with top, horizontal navigation, stick to only the top four or five links within the site.
I don't think this is a common enough use case to warrant this change (which would need documentation and tests if it were to be accepted). Overall, the goal has been to simplify the validators, and prune out edge cases. This use case can be easily accomplished by just using a method instead.
Markdown provides shorthand for the most common features of HTML. One of its best features is that you can always fallback to the full syntax for HTML. This includes doing things that aren't included in markdown. Personally, I like that markdown is concise and includes very little fluff. It makes it easier to learn the whole set of shorthand. This is particularly important if you expect someone else to read your code later.
One of its best features is that you can always [fall back[ to the full syntax for HTML.
See rebuttal below.
Invert the exit code of a process. Make 0 into 1 and everything else into a 0. An alternative to ! some-command syntax present in some shells.
minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply.
Don't use it! Writing simple assertions (and Minitest way of transforming them to expectations) is almost always a better idea anyway. Work with your favourite library authors to start with assertions and add matchers for convenience and not the other way around. Keep it simple.
First-party cookies are the lifeblood of every website, enabling businesses to remember key pieces of information about users and to collect analytics data. Third-party cookies are the bread and butter of AdTech, allowing publishers to monetize their websites, and brands to run advertising and marketing campaigns.
I discuss the flaws of this in regards to spreadsheets in Spreadsheets Are Sabotaging Your Business. In brief, when people inevitably started using the more complex formulas available, they unknowingly broke the fundamental design concept of paper spreadsheets: that humans can understand what’s happening between the cells.
In this system, plaintext files are used for most of the backbone of your organizational system.
You're not going to find many checkboxes, drop-downs, reminders, or date pickers here.
Thankfully, some clients like https://github.com/QTodoTxt/QTodoTxt2 do have nice features like autocomplete, and date pickers.
Most to-do lists give you no control over your data. Your tasks live inside the app, not in a document you can edit, and syncing is handled by whichever company made the app. If you don't like this, todo.txt is a great alternative.
Fetch() provides similar functionality through the AbortController interface. It’s not as simple as the Axios version, though:
Fig. 4
Graph is extremely unclear. Bad usage of point shapes
Local- using social media, technology, keeping it horizontal, keeping it simple and humble, celebration is important.
quickly realized something counterintuitive: Often, it’s the simplest uses of technology that get students to talk, write and create
This is really interesting. I think this is an important finding because as teachers begin to blend and personalize instruction, keeping it simple will allow for more teachers to engage because it doesn't appear to be daunting and super-sophisticated (and scary).