DEV Community

Discussion on: I spent 3 years writing an Android Contacts API in Kotlin with Java interop. What I’ve learned…

Collapse
thumbone profile image
Bernd Wechner

Lovely, frank and open sharing. I didn't read it all, as per your closing prediction as it is a tad long and diverse in content from Java code to human interactions for example and I'd have considered splitting it into a series here on dev.to (I'm pushing one myself) only because I believe shorter is generally better on-line and the series structure here helps bind a larger story into its smaller components - which also help people searching in future surf into a bit that is their focal interest then, and exploring the backdrops tory (series) if they have interest and time.

Collapse
vestrel00 profile image
Vandolf Estrellado Author • Edited on

Thanks for reading @thumbone ! I knew that I would get suggestions about breaking this up into smaller articles. I 100% agree that it is too long. That goes the same for the Medium article I wrote haha!

I understand that I'm doing myself a disservice by not following standard rules for advertising, which are to keep it short, impactful, unique, and (most effectively) outrageous. As you said, I could have easily split this into a series. Any one of the sections in this article could have been a standalone article.

  1. I spent 3 years building a Contacts API in Android.
  2. Writing "open source" code, privately.
  3. Thinking that no one else in the world is building what I'm building.
  4. Hoping that people will magically discover what I've built without promoting it.
  5. Answering ancient questions in StackOverflow using the APIs that I've built.

I thought about it even before writing this article. The first one would have the hashtags android, java, kotlin, showdev and the rest would have opensource and other related hashtags.

The last topic about getting my posts taken down from StackOverflow would have made for a great promotional Big Bang as it checks all effective marketing rules of "keep it short, impactful, unique, and (most effectively) outrageous".

I decided against doing that because I feel that the code I wrote and my non-coding experiences I gained from it are one and the same. It can't be in the same series. They have to be in the same article. It is a perfect example of "emotions clouding judgement"! However, all of this is of my own volition. I am in control and fully aware.

If I am less emotionally attached to what I'm building, I would not listen to what I feel. I would market my socks off and split this article into bite-sized chunks, even pay money to get featured. I know that doing so will allow me to get the most attention, and stars in my repo.

TLDR; Perhaps I don't really want to succeed in promoting my work XD