Cake
  • Log In
  • Sign Up
    • • Please share a link to one of your personal stories on Cake.

      This post was quite easy for me to choose since I don't often share personal stories on Cake. Most of the conversations I start are more informative and are meant to generate discussions, and I think this post on my trip to Penang is probably the most personal post I've written on Cake.

      • What made this story a good one to share publicly on Cake?

      Even though this is a slightly more personal story than I usually write, it's still quite informative, which is why I decided to write it. If I didn't have any insightful information to share from this trip I probably wouldn't have written it.

      Also, there aren't many Malaysians on here, and I think many people have never even been to Malaysia, so I thought it would be quite interesting to share this story with people from others countries.

      • How long did it take to create this?

      It usually takes me a few days to prepare a long-form post as I write in my free time when I'm not playing games, watching YouTube/Netflix, or reading, and though I can't remember exactly how long it took me to write this particular post, I think it was definitely a few days, probably a few hours of work in total.

      • What’s your typical writing process? (Outlines? Stream of consciousness first draft followed by proofread and editing?)

      Once I get an interesting idea in my head, I tend to ask myself if I have enough information to grow this idea into a full post on Cake. There have been times when I had ideas for conversations on Cake but decided against writing a post because I didn't think I had enough to generate an interesting discussion.

      Once I decide I do have enough to start a conversation then I just start writing. I don't really bother with drafts, I just write from my head. Once I start writing then I just see where my ideas take me and let the words flow naturally. I find this works best for me. If I have a draft or a skeleton to follow then I might end up forcing my writing into a certain direction, which could lead to a more disjointed flow of information and ideas, which I don't like. For me, any form of writing must be smooth and ideas must flow naturally from one point to another.

      I take this same approach to my academic writing. I'm currently writing a review paper for publication in an academic journal, and when I started I had no idea what I would be writing about. I mean, I had a title, but that was it. Then I just started writing, and as I was writing (also reading other scientific publications for reference) I got more and more ideas on how to grow the paper into what it is now - about 7500 words.

      • What specific advice do you have for prospective creators? (How to craft a title? How do you decide on a story? Is a photo or image required?)

      As Nike says, "Just do it". The best way to learn is to do. I've been writing for years, possibly more than 10 as I started blogging in my early 20s, and I feel like I'm much better now than I was 10 years ago. Everyone has their own creative process, and so the best way to figure it out is to create, and create often. Eventually you'll figure out what works best for you.

      As for the prompted questions, titles should be perfectly balanced between clickbait and informative. They should be "clickbait" in a sense that you want people to be curious as to what you wrote about, but should also be informative enough so people can know from the title if the content would interest them or not. Lean too much either way and you could lose engagement.

      Deciding a story, I think I've explained earlier how I decide what to write and what not to write. And as for photos, I've also shared my thoughts in this older post from over a year ago.

      Hope my insights were helpful to everyone here.

    • I tend to contribute two types of stories:

      (1) personal experiences often related to my work as an entrepreneur and angel investor, and

      (2) comments on important news that isn’t widely covered or appreciated.

      The contribution I'm highlighting is of the first type, based on advice I have been giving informally to entrepreneurs raising their first round of angel capital.

      What made this story a good one to share publicly on Cake?

      As an angel investor, I review anywhere from 25 to 50 pitch decks per month and most of them suck.  So, I wanted to post in a public forum what I think are the elements of a great
      pitch deck so that I can share that link with entrepreneurs who approach me for investment or advice.

      I posted a link to this post on LinkedIn and it has received quite a lot of likes and comments by entrepreneurs, which was nice since I rarely post on LinkedIn.

      How long did it take to create this?

      This post took some hours to compose, spread out over several weeks.  Once I decided to share my thoughts on pitch decks, it took a bit of writing and editing to distill it down into something cogent and quickly digestible by entrepreneurs.

      What’s your typical writing process?

      I typically conceive of a topic and jot a few notes in a Word file and then expand upon that over a few days as thoughts begin to gel.  “Land and expand” as they say in venture capital circles.

      For longer posts, I am a big fan of writing a draft, setting it aside for a day or two, and then subsequently editing it once or twice before I post.  When editing, I try to make my point as simply and quickly as possible.

      Finally, I try to keep paragraphs short so readers can quickly scan and absorb my posts, newspaper-style as it were.

      What specific advice do you have for prospective creators?

      Post what you know about.  I think your personal experiences are more interesting than opinion.

      Add a little humor whenever possible.  While humor does not always translate well on
      the Internet, it can keep posts from sounding too pedantic.

      Include pictures and article links if possible. A picture is worth a thousand words even on a text-oriented site like Cake!