Chris Horne

Contribute as much as you can to open-source projects to keep building your resume. I actually open sourced my project to help some of my Laravel developer friends and myself build some public resume contributions. With the mass layoffs in tech overall, I think contributing to open source for resume additions is going to be crucial when your name is on a stack of resumes. Just my two cents....

What originally started as a billing platform for my own VOIP business, turned into a free open source project to help other service-based industries sell and manage their customers' contracts, services and more. I always believe in build something you would use yourself and you'll always have at least 1 customer! https://www.producthunt.com/prod...

You mean the frontend? Not sure I've ever seen a backend template.

I would suggest requiring feedback/review as a way to extend your trial vs a credit card. No credit card up front, but after a few days have something that's like "Want to extend your free trial? Answer these three questions" or something..

Generally.. I wake up. Grab a brush and put on a little makeup. Hide the scars to fade away the shake-up. Then sometimes I end up leaving the keys on the table, and then eventually create another fable. Why? Because I wanted to.

I love your intro video.. Very creative!

https://www.youtube.com/watch?v=fC6bQIlQrqw This was my go to this morning with my coffee.

I love the idea for an affiliate system. Gave me an idea to put it into my project as well. We have a sales agent commissioning system, but having a way to just throw a code around for commission tracking is a great idea.. Added to my milestone haha! https://github.com/Vocalogic/log... Going to check out your app today though.. sounds cool!

In regards to what? business? a product? life? financial success? mental success? Success is a loaded word that really needs more context. Happiness is success. Even if it comes in short waves.

I'd be interested. I'm currently working on some youtube videos doing an overview of how my software works to make it easier to understand and configure. In return I'd be happy to reciprocate and review something for you as well.

I've been toying with the idea of creating a project that all it does is allow you to get testers by testing and giving feedback on other projects.. Basically a credit system.. You review a product, get a credit, and then can use that credit to get reviews on your own product. Everytime I see a post like this it validates this idea more and more.. Although I do want to checkout polywork now.

Not really a failure, but my project started after paying around $500/mo for billing software that still didn't do everything I wanted it to, so I started my open source project and built the things I needed! And while the project not actively making me money, the success is that my business now runs more efficiently and less mistakes have been made during the quoting and invoicing process.....

Java probably. And pineapple on pizza.

I think it depends on the size and efficiency of your team. Some teams Agile would work well for and others would be a hindrance. For agile to work optimally you have to have a lot more than just a methodology in my opinion.

I'd say.. when to release to public.. then once done, how do you get traction.. but not too much traction that you're overwhelmed and can't support your customers - but just enough to keep moving forward unscathed by bug reports that undoubtedly will come your way!

You have to weigh the needs of the many vs the needs of the few. Not all feedback is equal, but it's important to get feedback from as many people as possible because you might get an idea you didn't have before.

I think we should just start a movement of no light mode.. ever!

Proper lighting, and music. Without those two I'd just stare at my screen thinking: "come on... do something"

Build something *you* would use and you'll always have at least one customer.