
Nikki Sutherland
Lead Software Engineer at Shop-Ware; software engineering leader specializing in Ruby on Rails since 2013.
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
SEP 28
OCT 5
OCT 12
OCT 19
OCT 26
NOV 2
NOV 9
NOV 16
Jun 30, 2026
Nikky Southerland: Lessons from 13 Years of Rails at the Auto Shop
50:55
51:00
51:15
51:24
51:35
51:39

Robby RussellHOST
With your infrastructure, does everything get kinda get deployed, or are you doing, like, uh, canary deploys or anything like that?

Nikki SutherlandGUEST
When I first joined, we were doing, in theory, biweekly deploys and releases, and that was a process that everyone hated, as far as I know, for a very long time.

Nikki SutherlandGUEST
And there was a huge QA regression test happened that lasted, like, a week, and sometimes they would find bugs, and sometimes features we'd need to go in that were promised.

Nikki SutherlandGUEST
And we'd have to, you know, shove them in the last minute and hope they don't break anything and delay the release candidates being cut until they were merged in.

Nikki SutherlandGUEST
And if you missed that, then you had to wait two weeks for the next release.

Nikki SutherlandGUEST
And bugs didn't get fixed for two weeks unless it was a really important bug, and you did a special release for it.
6 MINS LATER