PMS - How much time do you spend reading technical docs or API documentation?

As the title says ☝️

I have 8 years of total work experience, graduated from a Tier I college. I still feel lost as to what future holds. Kickass & genuine advises on professional, personal fronts are most welcome. I am sure a lot of folks could relate.

It’s clear that companies won’t need engineers 10 years from now. They’ll just need people who know what to make. Who to sell to. How to sell to. At what price. This will be the great commoditization of Software development Take it or leave it.

I’ve worked at multiple orgs: 1. Sometimes prd are written for the sake of it. Contains no details. Usually engineers closely work with pm and implement stuff 2. In other scenario active discussion happen on prd and then stakeholders meet and take final call 3. In some orgs prds are just less of prds and more of timeline docs. What do you guys prefer?

I am 4 months into my first job as a product manager. I have never coded in my life except for a basic coding course in college. While I am always eager to understand technical concepts and tend to ask a lot of questions around the same I still feel there's a huge gap in communication. This leads to poorly estimated timelines, and often difficulty in assessing feasibility of ideas. I wish to learn more about software architecture, data management systems and the development processes in general. While I know I lack technical expertise, I don't want to discount the possibility of this just being a communication issue within the team. This is a series B startup just entering the growth phase, so no proper processes are set up as of now - again something I will have to streamline. My question is to all the product managers especially who don't come from a technical background - how did you bridge this gap?

Portfolio management services

Can someone share any real Prd because i am writing prd for a website and it is crossing 30 pages is that okay?