jbranchaud

This largely depends on the kind of software system you are working on. These sorts of DDL migrations are common on the kinds of Rails apps I’ve worked on over my career. Size of the table, traffic patterns, who uses associated features, tolerance for small downtime windows, or orchestrating a multi-phase zero-downtime migration are all ways to justify these migrations, and is preferable to alternatives that would be comparably over-engineered for that app’s business and technical context.

I don't remember my first steps with subversion, mercurial, or git too well, but I don't think any of them were any more intuitive. My understanding is that jj is supposed to be easier to use for day-to-day version control. I'm very comfortable with git, but that was hard earned and I don't see that level of confidence with most devs that I've worked with over the years. Hoping jj can be more accessible to the average working software engineer than git has been.

The core advice of the article seems relevant and useful to both of those types of design.

Great article -- I'm going set aside some time with a notebook and pencil today and give this a try.

I'm not sure I agree with the left brain/right brain, analytical and logical vs creative and emotional dichotomy. I think good design work can be just as analytical as it is creative. I think it has to be when it comes to UI and UX.

I outsource most of my esoteric `jq` syntax questions to ChatGPT. It does really well with them, usually turning up solutions that I'd struggle to munge together from several different google search results.

I wonder how ChatGPT would do with focussed pandoc requests.

Hey, I'm Josh, the creator of this TIL repo. I've started it back in 2015 and still contribute to it a couple times a week. I reference TILs all the time to remember how to do something. It has been a great practice and I'd recommend to anyone to maintain their own TIL repo.

AMA!