stevenjackson

https://gist.github.com/alisdair/ffc7c884ee36ac132131f37e3803a1fe

stevenjackson

https://dev.to/wes/how2-using-gpg-on-macos-without-gpgtools-428f

stevenjackson

namespace(:db) do
  def query(sql)
    ActiveRecord::Base.connection.query(sql)
  end

  Rake::Task['db:create'].enhance do
    config = Rails.application.config.database_configuration[Rails.env]
    puts "Config #{config}"
    conn = ActiveRecord::Base.establish_connection(config)

stevenjackson

ApplicationRecord.descendants.each do |model| 
  model.reflect_on_all_associations.each do |relation| 
    model.first&.send(relation.name) 
  end
end

stevenjackson

  def record_error(error)
    error.set_backtrace(Thread.current.backtrace)
    if Rails.env.development?
      raise error
    elsif Rails.env.test?
      RSpec.current_example.set_exception(error)
    else
      Bugsnag.notify(error) do |report|
        report.severity = 'info'
      end

stevenjackson

Keybase proof

I hereby claim:

• I am stevenjackson on github.
• I am stevejxsn (https://keybase.io/stevejxsn) on keybase.
• I have a public key ASCgh8r-PSU-gCxmdICr5NKspZ7y3B-YI1c7BcUFq35vNQo

To claim this, I am signing this object:

stevenjackson

    - Giving it to the best player doesn't make the team better
    - Positive reinforcement
    - You can't play for them
    - You're going to be ignored / Shared understanding takes forever
    - The game is not the most important thing

  I coached a rec team that had a huge range of talent.  One young man was very talented and could have gone on to play junior college basketball.  I had a couple that were a level below him and then varying levels all the way down to the kid who was surprised when the basketball was in his hands.  I did focus on leveling up everyone in practice, but our in-game style quickly devolved to give it to the best kid and move around him.  This was moderately successful, everyone got to contribute, and the games were competitive.  Then that kid got sick.  Then baseball season started and he wanted to focus on that.  All of a sudden my team had no identity and no idea how to win.  We couldn't just lean on the next best player, the talent gap was too wide.  Before the team could re

stevenjackson

DevOps for the Perplexed

Containers, Swarms, Infrastructure as Code - it all sounds neat, but maybe a bit overwhelming? We just chef-ized our configs, but we can't deploy until we terraform something? There's a new tool every month, how do you keep up? You try to read the docs, but it sounds like they all do the same thing - why do we need to add another tool? Let's start with an example web app and try to get it running on someone else's machine. As I run through a number of deployment problems, I'll pull a tool off the shelf and show how it addresses that problem, and probably create a few more.

You'll walk away with an understanding of each class of tool and the one-thing it's best at. With that knowledge you can determine which tools can benefit your current projects and which are solving problems you just don't have yet.

stevenjackson

Empathy, Boldness and Boundaries:

@marcpeabody

Crucial Conversations

1. How to avoid crucial conversations?
2. What leads to them in the first place?

If you're like this when you're ok, you're going to be kinda like this when you're stressed

stevenjackson

Abstract

Do you avoid failure? Learn to succeed by embracing failure!

Discover how you can use failure to learn faster, build resilient software, and enable innovative teams. Learn how cognitive biases make failure seem unattractive. Explore experimenting with failure to overcome this stigma and supercharge learning. Investigate the skills to reframe failure and enable a mindset and culture suitable for success in a world full of random events.

Summary

Failure provides critical feedback, but we're conditioned to avoid it at all costs and forget it quickly when it happens. How can we challenge this natural human bias? I've spent the last couple years digging into "pop" psychology and thinking about how books like "Thinking Fast and Slow", "Antifragile", "Drive", "Blink", and "Outliers" apply in a software development environment. I'm most excited about the idea that if we can make failure "safe" then we can use it to learn things that we would otherwise be tempted to avoid and ignore because it mi