6
11 Comments

What exactly would you do? Even outrageous opinions are welcomed!

Ladies and Gents,

I'm at a crossroads and I need some fresh perspective.

Recently, I started falling down the rabbit hole of becoming a coder. Ruby/Rails to be exact. Now, I'm enough of a realist to realize that with due diligence I might feel confident in the burgeoning skill set in a year or so.

With that being said, here's my dilemma:

-Do I wait until my coding skills are 100% up to snuff and realize my own ideas by wearing every hat? Or,

-Do I try like mad to partner up with a highly technical co-founder, potentially revenue-split and share the hats?

I've ran a business by myself before, so I understand 80+ hours weeks on end.

What would you do and why?

Thanks!

on February 3, 2020
  1. 2

    What do you want? Like what do you actually want? Do you want to just start a business? Do you want to learn to code? Do you want to just make money?

    Without knowing your goals, most advice is not going to hit home.

    I think you will never regret getting more technical skills. But you need to figure out what you actually want.

    1. 1

      @joshdance I'm 100% on the fence with it. I'm very cool with waiting to flesh out some ideas until I can code them myself. That being said, I also realize that (a) small groups of smart people is what takes development to highest possible level and (b) there very well might be a development 'soulmate' if you will, whose skill set is complimentary to the one I currently have. In that case, I'd be completely cool with working with a technical partner.

      It takes so many hats to run a business, that I'm fine with not wearing all of them (been there and done that, twice!). It isn't about the money. Sure, if I can live off of what I'm passionate about, why not? It's more for the sense of accomplishment: working on something that I've got a passion for and bringing it all the way to fruition + hopefully helping some people in the process. That will add a lot of meaning to my life and meaning is truly what I'm after, at the end of the day.

  2. 1

    i read your question and i impressed with your thoughts this is very goor question you can see its answer here on my personal website https://hidethatfat.com/product-category/slimming-underwear/

  3. 1

    work on your own project and improve your coding skills if you partner up and
    you are not it won't help the joint venture

  4. 1

    If you're feeling patient and able to make money in another way, I think it's worthwhile pursuing something on your own. Even if your product sucks at first (except to a small population), that just means there's space to grow yourself as you grow the product.

    Even if you fail after a few months or a year, you'll get a lot out of the experience and it'll be much easier to find a partner for the next thing.

    If time is a concern and you want to be profitable in a year or two... maybe consider bringing on a partner. There are a lot of exceptions to this, of course!

    1. 1

      @mattkandler Thank you for the generous advice! I will indeed take it to heart.

  5. 1

    Partner. One of the sometimes overlooked validation of an idea is that you can convince someone to join you to realize it or not.

    1. 1

      Thank you🙏

  6. 1

    Something to consider, work for another company to learn more, acquire knowledge basically and get paid, that will really help you in your journey.

    1. 1

      Thank you. Yep, I did that with  and came out the other end a relational database developer, so I can attest to the fact that this works.

  7. 2

    This comment was deleted 3 years ago

    1. 1

      @Reboot2dot0 Many thanks, Aaron! 🙏