u/Wise-wordly0423

I have read Backman's two books so far. A Man called Ove and Anxious People. And I love his eccentric style and his ability to touch emotions. You become a part of his characters.

So, I am willing to read more of his work. Which one should I read next - "And Every Morning the Way Home Gets Longer and Longer", or "My Grandmother Sends Her Regards And Apologies"?

I have read reviews of his other books as well. But I want to know from you. Which other books should I go for?

Hi,

To understand your views as developers, I need some help.

I am not a developer, but I am working on a project that deals with API and SDK. The product offers API and SDK along with a webapp version.

We did not have a separate developer's portal earlier. Just the API doc.

But now, we want to address and focus on developers' pain points separately. And hence, we will have a developer portal. On the main page, I am thinking to add Doc, tutorials/examples, API dashboard, etc. in the navigation bar.

There will be code samples to show some of our usecases and features as well. Stats, data-security etc, too.

But what would you expect from this portal as a developer? Do you want it to be interactive (where you can upload demo files and see API working? We have a playground too). Would you like to see before-after results with our API or product? That you can hear or feel.

Would you like to explicitly see who this API is for? Or not?

Would you like to know a little about features or not?

Would you care about some ready-to-use and minimal-effort templates to try for your usecase? And integrations?

What would you hate on the page? How do you want to see and know things about an API? What else would you love to try and see?

It would be so amazing if I could get your help. It will help me provide the right details to developers, removing the fluff.

Thanks.

Hi,

To understand your views as developers, I need some help.

I am not a developer but I am working on a project which deals with API and SDK. The product offers API and SDK along with a webapp version.

We did not have a seperate developer's portal earlier. Just the API doc.

But, now, we want to address and focus on developers' pain points seperately. And hence, we will have a developer portal. Where on the main page, I am thinking to add Doc, tutorials/examples, API dashboard etc. in the navigation bar.

There will be code samples to show some of our usecases and features as well. Stats, data-security etc, too.

But what would you expect from this portal as a developer? Do you want it to be interactive (where you can upload demo files and see API working? We have a playground too). Would you like to see before-after results with our API or product? That you can hear or feel.

Would you like to explicitly see who this API is for? Or not?

Would you like to know a little about features or not?

Would you care about some ready-to-use and minimal-efforts templates to try for your usecase? And integrations?

What would you hate on the page? How do you want to see and know things about an API? What else would you love to try and see?

It would be so amazing if I could get your help. It will help me provide with the right details to devlopers, removing the fluff.

Thanks.

Hi,

To understand your views as developers, I need some help.

I am not a developer but I am working on a project which deals with API and SDK. The product offers API and SDK along with a webapp version.

We did not have a seperate developer's portal earlier. Just the API doc.

But, now, we want to address and focus on developers' pain points seperately. And hence, we will have a developer portal. Where on the main page, I am thinking to add Doc, tutorials/examples, API dashboard etc. in the navigation bar.

There will be code samples to show some of our usecases and features as well. Stats, data-security etc, too.

But what would you expect from this portal as a developer? Do you want it to be interactive (where you can upload demo files and see API working? We have a playground too). Would you like to see before-after results with our API or product? That you can hear or feel.

Would you like to explicitly see who this API is for? Or not?

Would you like to know a little about features or not?

Would you care about some ready-to-use and minimal-efforts templates to try for your usecase? And integrations?

What would you hate on the page? How do you want to see and know things about an API? What else would you love to try and see?

It would be so amazing if I could get your help. It will help me provide with the right details to devlopers, removing the fluff.

Thanks.

I recently finished Anxious People. And I loved it. It was heart-wrenching, funny, yet comforting. Right now, I am reading another book which feels slightly heavy. Also, my schedule is such tight right now, that I want to read a book which maybe lighter in its tone. Which may reflect on emotions so well, but may also make me feel good, may give me comfort.

I just want happy emotions in my already overwhelming times.

Which books will you suggest?