> That may be good enough.

I would argue it is.

I have had discussions with peers recently around doing the big flash-y <insert revolutionary product>. An interesting analogy surfaced. The nuts in the studs of the infrastructure of the many structurally sound homes in existence are just as important (meaningful) as the doors, windows, and more flash-y features. They may be _more_ important in some cases. They all make up the home.

It made me realize it might not be all about maximizing ambitious pursuits. Maybe it is more about experiencing the joy of solving the next problem and the fulfillment that comes from simply being needed pretty regularly.

This is a good point. I thought about it, too.

I could see a frequent traveler using an AVP as a "full setup" on the go. In my experience, I can get away with most with a MacBook. Some projects really benefit from the extra screen real estate (and a mechanical keyboard.)

> work every day, ~8h/day

This is fascinating. What are your most used features?

> extended monitor

Do you also use a real monitor in the field of view?

I recently wrote my own invoicing application. I got wrapped up in the joy of adding the features I wanted. Many of these features come at a premium monthly fee for a big named product.

I needed to get an invoice out in a timely fashion. As much as I wanted to use my app, I found certain kinks I needed to work out (with styling, adding addresses, etc.) -- This was where I realized what you have articulated.

At some point, it becomes better to prioritize the "fun" in working on my bike, and the "usefulness" of the daily driver bike.

In doing so, perhaps the fun/usefulness of each converges over time.

I personally have found it effective to oscillate between having a goal and defining constraints in some _direction_. There are points on the journey where articulating a specific goal is helpful. At other times, I get more results with a few well-defined constraints. It can depend upon the season, but both have been solid tools for progress.