4
9 Comments

Need advise with SW product positioning!

Fellow hackers who write code and tech founders. We are working on a product that makes code comprehension easier but struggling to position our product.

As an engineer, which problem do you see more pressing? What resonates with you more?

  1. automatically create visual documentation for any project
    or
  2. visualize complicated code to understand how it works
    or
  3. answer questions about complicated code

Thank you hackers. You guys are the best.

on January 13, 2020
  1. 2

    If I was you, I would have just said

    Visual Code Flow for your complicated project

    This will clear 3 things

    • What Problem : Code flow / how different modules tie together

    • For whom : Big and complex projects

    • Unique selling preposition : Visualisation

    1. 1

      Great thank you. In other words you see more value in understanding specifics of complex code as oppose to just "having visual documentation", am I right? Thanks again.

      1. 1

        Correct. Please I believe this has to give holistic view for the new developer in the team.

        Do you have any prototype how this looks like ? I am just wondering...

        1. 1

          Sachin, the early prototype is at https://sourcespy.com. Our decission is around where to focus the development - overall picture or detailed flow analysis akin to this.

  2. 1

    I think we should apply ICE framework here. E-mail me about that if you want.

    1. 1

      This is a great reference. Never heard about ICE but it is very close to what I need. Thanks and I'll get in touch.

  3. 1

    In my opinion this is a very useful thing. Beginners will be able to quickly understand the essence of a large project. Even experienced programmers will help to save a lot of time. Cool idea, and most importantly useful !!!

  4. 1

    I'd say 2 and 3 kinda the same thing. You don't need to visualize the code unless you have a specific question in mind. If you can combine them both, I would say 2/3. Good luck!

  5. 1

    Documentation is dead. I vote for #2 and #3 close behind but I'm not sure how it might work.