(Not gp) I read this book more than a decade ago, when I was very inexperienced. The thing I remember the most, and I think the most valuable to me, is the idea of defining a shared domain language with the business domain experts, with a clearly defined meaning for each concept identified. For instance, what a "frozen" account exactly means, what's the difference with a "blocked" account. These are arbitrary, but must be shared among all the participants. This enables very precise and clear communication.
I just bought a nice Asus Zenbook and first I did as soon as I received it was installing pop os. I keep my old windows notebook near by in case I need something I can't do in the Linux machine, but its use is more and more infrequent.
I've been wondering for a while whether it's possible/practical to create a solo company (maybe Delaware LLC) in the US just to be able to offer and invoice my services as a software developer to US companies that look for US candidates.
I assume (please correct me if you think I'm wrong) that sometimes this requirement is because of taxes and bureaucracy, and my be could be overcome by hiring a US company services (owned and operated by a non US citizen/resident).
I run my own email using mail-in-a-box running on a 5 dollar Linode, works like a charm with almost no maintenance (the little maintenance I do is always requested automatically by the system itself, and I'm notified by email)
This is what makes me really undecided about switching jobs. I've been working in the same domain for almost 20 years. I think I'm a very competent SWE, but I also think my domain knowledge is what really impress my customers.
This will probably settle with many new small companies succeeding at software products. The interests align beatifully when the SWE are de owners of the business.