I realized what I was trying to say:
a good authorization service makes for good software development.
- [all this random stuff about why authorization is hard]
- Authorization stuff is complicated, but when it works well, it's really nice.
Tutorial:
I realized what I was trying to say:
a good authorization service makes for good software development.
Tutorial:
I often write detailed walk-throughs of difficult learning projects I take on.
This document serves as the same, a bit of an active scratch pad, and a way to quickly ask detailed questions of my team, and perhaps provide detailed answers for my team.
currently trying: USB-C->DisplayPort cord with SwitchResX to "force" the display up to a reasonable level
My home office setup has suffered some problems of late that are driving me insane.
The most annoying is my wired mouse. I use a wired Redragon Mammoth hooked up to my USB-C hub, and it started giving me problems when dragging anything. Like... a file, a screenshot, a window, it would rapidly (dozens of times a second) "drop" what I was dragging and then pick it up again.
This had extremely unpredictable effects, and was highly disruptive to my workflow.
I don't think my mouse is failing (my bluetooth mouse works fine, and for a variety of reasons I think the problem is my monitor is running at 30hz, not 60. more on that later.)
Having a good process is how you go about doing anything that takes a long time and is hard. A good process can be a faithful tool to help you learn dozens of things, now, and five years from now. It's flexible and it's powerful.
One of the biggest pieces of "having a good process" is "taking plentiful notes, easily and quickly"
I won't try to convince you. Here's Arique, currently in Mod 1, on how she's made use of this general process:
class Object | |
def exceptional? | |
false | |
end | |
end | |
Course = Struct.new(:name, :duration) do | |
def duration=(new_duration) | |
self[:duration] = Duration(new_duration) | |
end |
i want to know how long it takes to do some stuff. I've got some code like this:
def count_stuff(list)
list.inject([]) do |results, item|
results << get_results_from_something_else(values)
end.flatten.uniq
I needed a URL validator - it needed to check that URL's had HTTP or HTTPS at the beginning. I initially wrote a "before save" action, but didn't like it cluttering up my model. I found a reference to basically "monkey patching" Rail's default Validator class, so that's what I did!
# concerns/url_validator.rb
require 'uri'
class UrlValidator < ActiveModel::Validator
def validate(record)
if record.url?
topics: {
DEEP WORK:
protect and cultivate (limited) attention,
ear plugs,
skeptical of music,
examine your own process,
downtime,
We'll cover two things:
From Regis, who will cover the "workflow" portion of the spike
A few days ago, I worked on a project that was mostly about serving up basic store data (modeled after Etsy) to an API.
We had a few dozen end-points, and all responses were in JSON.
Most of the action happened inside of our controllers, and as you might imagine, our routes.rb
file was bananas.
One of the instructors made an exceptionally simple suggestion, I was embarrassed to not have seen it.