rongenre

I'm an experienced individual contributor who's done a lot of work building and scaling distributed backend systems in a bunch of different industries. I've worked for both startups and large enterprises.

  @book{Kuhn1962,
    author    = {Kuhn, Thomas S.},
    title     = {The Structure of Scientific Revolutions},
    publisher = {University of Chicago Press},
    year      = {1962},
    address   = {Chicago},
    note      = {Often cited with various editions, e.g., 50th ed. 2012},
    keywords  = {paradigm shift, normal science, scientific revolutions}
  }

1. Brainstorming building something. Tell it what you're working on, add a paragraph or two of how you might build it, and ask it to give you pros and cons and ways to improve. Especially if it's mostly a well-trod design it can be helpful.

2. Treating it like a coach - tell it what you've done and need to get done, include any feedback you've had, and ask it for suggestions. This particularly helps when you're some kind of neurospicy and "regular human" responses sort of escape you.

I miss that girl.

I mostly do commuting, grocery runs, etc. EVs are great for that. But then I do road trips about once a year, and an EV just adds to the complexity of planning currently.