FrancoisBosun

Trust (2011) is a movie that shows us how the pedophile works. Trust is a movie about a 14 year old girl that falls prey to a man, and the process by which he got what he wanted.

I highly recommend the movie.

https://www.imdb.com/title/tt1529572/

In Canada, it is not. If you don’t join the union, you may still benefit from the union’s bargaining power so you will pay some dues to the union. I would presume this varies per region.

This is called PostgREST: https://postgrest.org/. Never used it in production, but PostgREST leverages multiple PostgreSQL features: row-based security, schemas, authorizations, etc. I quite like PostgREST, and I'd use it for internal stuff.

The functional language does do away with loops, but when the rubber nets the road, you don’t have any choice: somewhere, something will execute the equivalent of “for(int i = 0; i <= 10; i++) {}”.

When I implemented Mindcode, I realized that “while” is the basic construct and that all enumerations and looping compiled down into goto.

Mindcode is a Ruby-like language for the Mindustry game. Mindustry has an assembly-like language with a visual editor in-game. Mindcode has a more traditional text-based flow.

If it isn’t syntax then it is a function/method call. By being a method call, one can define default options, allowing overridability.

For better or for worse, we have “agreed” to the teens and conditions …

Shift + /, when using fr-CA, does return É. Is that what you meant with "two keys". For œ or Œ, I use Option+Q or Option+Shift+Q (Mac Big Sur).

I set this up differently: my user gitconfig has my personal email. In my work monorepo, I have a local gitconfig where I set/override the email and GPG settings.

Still, this is a neat thing too.

From my understanding, this is total message size, but packet. If a receiver has two incoming messages, a batch upload and a query for a list, the batch upload may have 10MiB to transmit while the other message may only have 1KiB. This, to improve latency, the smaller message should be prioritized.

What about a key named “_comment”, or something similar? Of course, the underlying software must ignore unknown keys, so it’s not a full win anyway.

Jim Weirich wrote rspec-given. This gem allows one to write really nice assertions:

    Given { @stack = Stack.new }
    When { @stack.push(1) }
    Then { @stack.peek == 1 }
    And { @stack.size == 1 }

What you wish for is embedded in When and And. Check it out: https://github.com/jimweirich/rspec-given

Well explained article. Good job OP!

That is what OP was talking about: after you've done the change, make a commit with just that tiny refactoring. Once you're done and ready to review your work, you can cherry pick just that fix and move it to main / master / it's own PR. Since it is self-contained, it can be processed by itself only.

If you haven't, Sqitch[1] is a great tool.

[1] https://sqitch.org

The article is about reducing R and maintaining it at or lower than 1. Yes, the article does not have sliders for age, CFR and IFR and what not, but the fact remains that people reading this must understand how to reduce R. I found it very informative and entertaining.

Similar concept, in Ruby, acting as a filter in a pipeline, by me:

https://github.com/francois/surrender

Maybe because of the large increase in complexity?

In 5 years, I used !g maybe once. I use !pg, !wen and others very frequently.

The difference is my customer's don't have a first-party relationship with the data store that holds their password.

    browser -> www.example.com

    browser -> www.example.com -> Base

That's the biggest problem I see with this approach. The password will be seen by two parties instead of just one.

Looks nice. I’m uncomfortable pushing the password in plaintext to an unknown entity. I can always bcrypt the password locally before sending it through the API, but it would be great to see examples of this, to prevent deva from pushing secrets outside their zone of control.

Otherwise, I can see myself using this in some side-projects. Good work!

There is now a boot time for my kitchen mixer… about 2-3 seconds. It’s horrible and I always forget.

You know about such trick, others may not. I loved this article for the thought process, not for the nested loop error.

There is also Redo

https://redo.readthedocs.io/en/latest/

Very different, never used it, but very interesting nonetheless.

I thought nothing could move faster than light?

Messages, yes: "Hey siri, read my unread messages". Phone, I don't know.

Sqitch by David Wheeler is a great way to manage database schemas. I haven’t uses it in production, because I mostly use Rails and haven’t felt enough pain to justify the switch.

https://sqitch.org

The execs in question are most probably all male and have never thought about stillbirths.

10 years ago, on the exact same hardware, running a Rails application test suite in a Linux VM through VirtualBox was nearly 2x faster than running natively on the Windows side of things. This must be a combination of things, namely Ruby on Windows was super slow back then, but the filesystem impacted things as well.

In an app, I can import a picture either through attaching an image or pasting a URL in a field on the UI. That URL field does not exist in the DB, but in order to benefit from ActionView's helpers, I had to declare the field on my model, even though the value in that field never goes to the model. The controller takes the field's value and does the right thing with it.

This is a very simple example of a common task that the separation between UI and backend fails.

Ah, true. I use Encrypt.me on a public Wifi. Perfectly legitimate use, and I get blocked. Oh well.