For Robotaxis, Safety Must Be Built In, Not Bolted On

I’m not a believer in languages designed by a committee and I have faith in Matz making reasonable decisions at the end of the day.

The beauty of runit is its brevity and simplicity

Reliability of the init system is paramount so simplicity is a key attribute.

You cannot. And you're not supposed to. When an account is deleted, it is disassociated from all existing posts by design.

Most browsers do give focus to a button being clicked, but Safari does not, by design.

Anything that isn't explicitly enforced by contract is vulnerable to misunderstandings. It's doing your teammates a great service, and reducing everyone's effort, by eliminating ambiguity and enforcing information flow by design.

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

In particular, with AC connected, a battery with a charge level higher than the stop charge threshold will not be discharged to the stop charge threshold, nor will there be a (cyclic) discharge down to the start charge threshold

Diet YAML is a light weight version of YAML that removes much of the complex aspects of the mainline YAML specification.

I would like to understand this design then. In my experience it has only served to limit what I can achieve, and gained me no additional benefit.

As has been stated elsewhere, in a Capybara test you typically want to do POSTs by submitting a form just like the user would.

The Capybara Ruby gem doesn’t support POST requests, the built-in visit method always uses GET. This is by design and with good reason: Capybara is built for acceptance testing and a user would never ask to ‘post’ parameter X and Y to the application. There will always be some kind of interface, a form for example. It makes more sense to simulate what the visitor would really do

This is ugly by design, as an inducement to test properties instead of specifics.

La confidentialité par défaut : La clause de "confidentialité par défaut" du projet de loi 64 a une portée beaucoup plus vaste et est beaucoup plus stricte que le concept de "confidentialité par conception" prévu par le RGPD. Le CCPA adopte plutôt une approche corrective "après coup".

The hyperthreat can be outmaneuvered by humans reconfiguring their activities in two ways: security by design and security by dispersal. National security in the Anthropocene is increasingly achieved by designing systems and settlements so that enhanced security is incorporated from the start. For example, it can be imagined that each time a person refuels a car with petrol, this action empowers the hyperthreat. This leads to global warming, which creates ocean acidification and in turn reduced fish stocks, while also creating pressures for resource wars, thereby influencing whether a soldier or civilian dies and how much taxpayer resources are required for material security missions. In contrast, zero-emission transportation technologies can “design out” the slow violence and threats associated with a fossil-fuel-intensive lifestyle. This is similar for plastic use, in which case the “threat” is embodied in the high polluting design of consumable products and lifestyle activities. Likewise, other health threats and longer-term costs are embodied in hidden toxins or sugars in food products. Accordingly, peace, health, and a different form of national prosperity can be created through design, which requires a longer-term and mesh-intervention viewpoint. OP VAK has a role to play in achieving security and safety by design by linking apparently benign activities with their devastating impacts.    

Drum or bag – a mechanism that requires replacement of the drum or bag that collects the matter.

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.

We don't need the threat of repo men to keep you paying your car note – miss a Tesla payment and your car will phone home and lock its doors. When the tow arrives, it will flash its lights, honk its horn and back out of its parking space for repossession.

Platforms of the Facebook walled-factory type are unsuited to thework of building community, whether globally or locally, becausesuch platforms are unresponsive to their users, and unresponsive bydesign (design that is driven by a desire to be universal in scope). Itis virtually impossible to contact anyone at Google, Facebook,Twitter, or Instagram, and that is so that those platforms can trainus to do what they want us to do, rather than be accountable to ourdesires and needs

I'm not sure if there's any cost in terms of contributing either, especially when by design git can have any branch as default, and will not hinder your experience when you use something other than master.

The primary branch in git can have any name by design.

For me the diagrams make it easier to talk about what the tests do without getting bogged down by how they do it.

Prettier intentionally doesn’t support any kind of global configuration. This is to make sure that when a project is copied to another computer, Prettier’s behavior stays the same. Otherwise, Prettier wouldn’t be able to guarantee that everybody in a team gets the same consistent results.

Incredible Mandy is a great example of design by subtraction, focusing on puzzle-solving and atmosphere and eschewing mechanics which do not contribute to the developer’s singular vision.

There is no request.env in functional tests because the functional tests are supposed to remain at the controller level.

A simple, yet surprisingly mind-boggling puzzle game. Simplicity may be perceived as a negative connotation when it comes to games for many people, but Neon Warp's simplicity actually works in it's favor in the best way possible and becomes one of it's strength.

There are myriads of platformers around, it's an oversaturated market, and just like industrial designer Karim Rashid said about there being no excuse by this point to make an uncomfortable chair, there's no excuse by this point to make a boring patformer.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

but if you were previously using regexp or proc values, they won't work at all with Sprockets 4, and if you try you'll get an exception raised that looks like NoMethodError: undefined method 'start_with?'

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.

The reason Reform does updating attributes and validation in the same step is because I wanna reduce public methods. This is to save users from having to remember state.

that's by design:

By design, snap apps have no access to /etc. They live in their own little world, but instead of a normal chroot, they are splatted all over the standard Linux filesystem layout. With other bits mounted hither and thither. Its a mess, and subject to change with each release.

Some of these are absent-by-design

For a long time, the blue flame coming out of a gas burner has evoked cleanliness. That was no accident, but the result of a concerted advertising campaign.

Or even keep as is, the simplicity of this feels right in line with svelte's simplicity :)

Deku is a library for rendering interfaces using pure functions and virtual DOM.

Most of the tech news we get barraged with is about algorithms, AI, robots, and self-driving cars, all of which fit this pattern. I am not saying that such developments are not efficient and convenient; this is not a judgment. I am simply noticing a pattern and wondering if, in recognizing that pattern, we might realize that it is only one trajectory of many. There are other possible roads we could be going down, and the one we’re on is not inevitable or the only one; it has been (possibly unconsciously) chosen.

duty of care

But Vue’s simplicity runs more deeply in its design.

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.

The $ contract for auto-sub­scrib­ing is lovely in its sim­plic­ity and flex­i­bil­ity. You can adapt your own preferred state-man­age­ment pattern or library, with or without Svelte stores as helpers. Svelte does not fuss about how you want to manage your state.

“Simplicity in all we do” is one of the core values at DigitalOcean. This includes all aspects of our product portfolio: UX, API, CLI, docs, billing, and pricing.

Because Svelte is a compiler, we're not bound to the peculiarities of JavaScript: we can design a component authoring experience, rather than having to fit it around the semantics of the language.

Rollup also does something very different compared to the other bundlers. It only tries to achieve one simple goal: Bundle ES modules together and optimise the bundle.

Did you know that you can create a Svelte component and with almost no extra steps distribute- and use it like any classic old Javascript library through a global constructor (let myComponent = new MyComponent())?

By enforcing this practice, Svelte can make some assumptions that simplify your code.

This is what I love about React, it's JavaScript basically, not a DSL

At the same time, we need to ensure that no information about other unsafe usernames or passwords leaks in the process, and that brute force guessing is not an option. Password Checkup addresses all of these requirements by using multiple rounds of hashing, k-anonymity, and private set intersection with blinding.

Privacy is at the heart of our design: Your usernames and passwords are incredibly sensitive. We designed Password Checkup with privacy-preserving technologies to never reveal this personal information to Google. We also designed Password Checkup to prevent an attacker from abusing Password Checkup to reveal unsafe usernames and passwords. Finally, all statistics reported by the extension are anonymous. These metrics include the number of lookups that surface an unsafe credential, whether an alert leads to a password change, and the web domain involved for improving site compatibility.

For several reasons the Simple backend shipped with Active Support only does the "simplest thing that could possibly work" for Ruby on Rails3 ... which means that it is only guaranteed to work for English and, as a side effect, languages that are very similar to English. Also, the simple backend is only capable of reading translations but cannot dynamically store them to any format.That does not mean you're stuck with these limitations, though. The Ruby I18n gem makes it very easy to exchange the Simple backend implementation with something else that fits better for your needs, by passing a backend instance to the I18n.backend= setter.

There are thousands of to-do list apps out there, in part because no system works perfectly for everyone. I’m not going to say todo.txt is the exception, and that it will work for everyone, because that would be crazy. But todo.txt is the most flexible tool I’ve come across. In part, this is because of the sheer number of clients available, but also because the simplicity lends itself to improvisation.

You're not going to find many checkboxes, drop-downs, reminders, or date pickers here.

Simplicity is todo.txt's core value

In a nutshell, the King's Keys deck started as an experiment to see what card games would be like if you rebuilt playing cards from the ground up. Instead of using ranks and suits, each card has a number (from one to four), one of four items, and one of four colors. The result is what I call a 4x4x4 deck where 64 playing cards each have a unique combination of these three parts.

Arguably, the rails-team's choice of raising ArgumentError instead of validation error is correct in the sense that we have full control over what options a user can select from a radio buttons group, or can select over a select field, so if a programmer happens to add a new radio button that has a typo for its value, then it is good to raise an error as it is an application error, and not a user error. However, for APIs, this will not work because we do not have any control anymore on what values get sent to the server.

When the controller creates the user, instead of adding a validation error to the record, it raises an exception. How to avoid this?

But now the first line throws an exception ArgumentError: '0' is not a valid audience

Unfortunately, it also gets the other properties, including bringing down the whole system when it crashes. This matters because systemd is complex

“Code without tests is broken by design”

The selection committee declares that whatever LMS the university chooses next must work exactly like Blackboard and exactly like Moodle while having all the features of Canvas. Oh, and it must be "innovative" and "next-generation" too, because we're sick of LMSs that all look and work the same.

I use backwards de-sign to develop our lesson plans: What do we want our students to write, and why? What skills are required, and how do students acquire those skills (Wiggins and McTighe 34)?

The central idea of DbC is a metaphor on how elements of a software system collaborate with each other on the basis of mutual obligations and benefits.

project-based learning (PBL), game-based learning (GBL), Understanding by Design (UbD), or authentic literacy, find an effective model to institute in your classroom