Recently, I've been seeing other people's e-books because of my own background in releasing -ebooks.

"So many books that hit exactly the right spot regarding what I'm having trouble with"

I'm impressed.

It is natural to think about it, but a general book cannot be published unless a certain number of publications can be expected.

There is no way that content in a niche technical field can be sold in a normal way.

However, in the case of e-books, there are basically no intermediate costs (editing, binding, shipping, bookstore shelves, returns).

The cost for this is also low.

-----

For an engineer like me, the contents of general books are often not enough.

For example, the GTFS data format and how to retrieve the data, or how to set up AWS IAM, are out of scope even for data engineers and cloud engineers.

My writings on Bayolinks, PostGIS, etc., are probably a mystery to many engineers.

If your goal is to make money in the first place, this kind of publication is completely absurd.

-----

I don't know about other fields of e-books, but when it comes to the technology field, it seems to be driven by different theories than the normal market principles for books.

(1) Write down my findings when I forget them, regardless of profit, and

(2) By being aware of the fact that "others will read it," I will be able to structure my sentences properly, and

(3) It's good if I can recoup some of the cost of the time I spent writing.

like the above.

-----

Well, sometimes I think the books are a bit difficult to read because they don't have a professional editor in them.

However, as an engineer, I believe that they can read between the lines, even if it is difficult to read.