Merge 460473a87f into 25b5677260

README.md

@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
 
 For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
 
-_1436 TILs and counting..._
+_1439 TILs and counting..._
 
 ---
 
@@ -392,6 +392,7 @@ _1436 TILs and counting..._
 
 - [Deploy A Review App To A Different Stack](heroku/deploy-a-review-app-to-a-different-stack.md)
 - [Diagnose Problems In A Heroku Postgres Database](heroku/diagnose-problems-in-a-heroku-postgres-database.md)
+- [Open Dashboard For Specific Add-On](heroku/open-dashboard-for-specific-add-on.md)
 - [Run SQL Against Remote Postgres Database](heroku/run-sql-against-remote-postgres-database.md)
 - [Set And Show Heroku Env Variables](heroku/set-and-show-heroku-env-variables.md)
 - [SSH Into Heroku Server Hosting App](heroku/ssh-into-heroku-server-hosting-app.md)
@@ -1101,6 +1102,7 @@ _1436 TILs and counting..._
 
 - [Avoid Accidentally Disabling Pry](rspec/avoid-accidentally-disabling-pry.md)
 - [Check Specific Arguments To Received Method](rspec/check-specific-arguments-to-received-method.md)
+- [Configure Tests To Run In Random Order](rspec/configure-tests-to-run-in-random-order.md)
 - [Find Minimal Set Of Tests Causing A Flicker](rspec/find-minimal-set-of-tests-causing-a-flicker.md)
 - [Format Test Results As A JSON File](rspec/format-test-results-as-a-json-file.md)
 - [Run Tests With Documentation Formatting](rspec/run-tests-with-documentation-formatting.md)
@@ -1180,6 +1182,7 @@ _1436 TILs and counting..._
 - [Map With Index Over An Array](ruby/map-with-index-over-an-array.md)
 - [Mock Method Chain Calls With RSpec](ruby/mock-method-chain-calls-with-rspec.md)
 - [Mocking Requests With Partial URIs Using Regex](ruby/mocking-requests-with-partial-uris-using-regex.md)
+- [Multi-Line Comments](ruby/multi-line-comments.md)
 - [Named Regex Captures Are Assigned To Variables](ruby/named-regex-captures-are-assigned-to-variables.md)
 - [Navigate Back In The Browser With Capybara](ruby/navigate-back-in-the-browser-with-capybara.md)
 - [Next And Previous Floats](ruby/next-and-previous-floats.md)

heroku/open-dashboard-for-specific-add-on.md

@@ -0,0 +1,17 @@
+# Open Dashboard For Specific Add-On
+
+The number of times I've needed to check the papertrail logs for my
+Heroku-hosted Rails app is a lot. I open a browser tab, go through several
+layers of navigation to get to my app's dashboard, and then click the
+papertrail link under _Add-ons_.
+
+There is a much quicker way using the Heroku CLI.
+
+```bash
+$ heroku addons:open papertrail -a my-app-name
+Opening https://addons-sso.heroku.com/apps/abc123/addons/efg456...
+```
+
+It sends you to an add-ons SSO link in the browser which authenticates you and
+drops you into the dashboard for that specific add-on. You just need to specify
+the add-on name and the app name.

javascript/immutable-remove-with-the-spread-operator.md

@@ -15,10 +15,8 @@ const remove = (items,index) => {
 };
 
 const list = [1,2,3,4,5];
-remove(list, 2);
-// [1,2,3,4]
-list
-// [1,2,3,4,5]
+remove(list, 2); // [1,2,4,5]
+// list still [1,2,3,4,5]
 ```
 
 It only took a couple lines of code and immutability is baked in.

rspec/configure-tests-to-run-in-random-order.md

@@ -0,0 +1,33 @@
+# Configure Tests To Run In Random Order
+
+By default, an RSpec test suite is going to run in a predictable, sequential
+order, every time.
+
+When testing the parts of a complex Rails app that have all kinds of test data
+that needs to be set up, I prefer to have my tests always run in a random
+(repeatable with a seed) order. This way I'm more likely to catch sooner,
+rather than later, bugs that are hidden by passing tests due to test data setup
+that happens to work in a specific order.
+
+RSpec can be configured to run tests in a random, seedable order in the
+`spec_helper.rb` file.
+
+```ruby
+RSpec.configure do |config|
+  config.order = :random
+end
+```
+
+Whenever you run your test suite, the first thing you'll see is a message like
+this:
+
+```
+Randomized with seed 7011
+```
+
+That seed number can be used to re-run the suite in a repeatable order when you
+need to do so to track down an order-dependent failing test.
+
+```bash
+$ be rspec --seed 7011
+```

ruby/multi-line-comments.md

@@ -0,0 +1,46 @@
+# Multi-Line Comments
+
+Ruby has an obscure syntax for creating multi-line comments.
+
+In many languages, there is a multi-line comment syntax that looks something
+like this:
+
+```javascript
+/*
+ * multi-line comment in javascript
+ */
+```
+
+This gets used often in those languages.
+
+In Ruby, the multi-line comment syntax is not something we see very often. It
+is a departure from the single-line comment syntax and it also requires no
+indentation.
+
+```ruby
+RSpec.configure do |config|
+  config.order = :random
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # These two settings work together to allow you to limit a spec run
+  # to individual examples or groups you care about by tagging them with
+  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  # get run.
+  config.filter_run :focus
+  config.run_all_when_everything_filtered = true
+
+  # ...
+
+=end
+end
+```
+
+Using the `=begin` and `=end` syntax (no indentation), we make everything
+inbetween into a comment.
+
+Though we don't see this too often, I did pull this example directly from the
+`spec_helper.rb` file that RSpec generates.
+
+[source](https://docs.ruby-lang.org/en/master/syntax/comments_rdoc.html)