Alfonso Alvarez

Thanks for your post! There are a couple of tools for this, right? I found this one recently that apparently it's been used by some people to automate onboarding... https://withpact.com/ .. as well as other platforms :) Hope it helps!

✋

AWS and GCP mostly for infra / code / services. G Suite. It makes a lot of things easier. It depends on the service and solution I'm trying to create and, of course, how expensive could it get. (I try to architect my solutions to be either free or incredibly cheap)

I see mixed responses. What are you referring to? Editing video? Or just storing the result? (Like youtube)? CHeers! For edition: - Canva - Descript - Veed.io To store and share them: - Youtube. - Youtube Shorts Cheers

Hey @profy17 , Could you share some of your experience to build a Slack community? How do you build it? That's the part I'm starting with my product and I feel totally connected with your concern about Generated content. I was planning to build a small tool to do so. If you discover something we could use please let me know :) Cheers and thanks!

Prioritize priorities 😅

Congratulations! Wish you all the best. I'm building something similar and I'd like your opinion: What is the reaction you're getting from employees using this? And from the rest of positions in a company? :) Cheers

1. Interviews 2. Research. (Competitors, Science behind to have strong fundamentals) 3. Launching and testing constantly.

Generate valuable content. Something that is interesting/useful

With my first startup: The hype. My mentors. Wanting to learn a lot of techs. (That's how I entered DevOps) Now: I want to create something that will help others. Current startup: I lived burnout. It was awful. I want to help people prevent burnout and live better.

1. Co-Founders help a lot. Select them carefully and be clear on the details of the deal. 2. Validate a lot first. Interview a lot of people. 3. Launch super fast. Multiple iterations per month. 4. Hang in there as much as possible. 5. Talk to possible users a lot a lot a lot. 6. Build when you're sure. 7. Make room for planning, thinking and clarifying the mind. Avoid work without...

"Why are you doing what you are doing?"

Got someone technical and up to date with latest industries practices for speed on teams and product and either have him/her as constant advisor or join your team if possible. At least a Tech Lead. (This because it sounds like you will have a bunch of developers).

Go to uncle Rocky, same as launching -> Get over it as fast as you can and move on. https://www.youtube.com/watch?v=uyTAfX7cniI&t=1s

And I thought I couldn't trust humans.... ... wait a second...

Validate with as many close people as you can before launch to avoid the "most common things that people will notice" .. That will at least make some progress no matter what the outcome is. Set goals and all those things in the PH launch guide. Try to be as clear as possible. Have fun! All the best on your launch

This one is a tricky one. What do you mean with "Productivity" exactly? .. Same for "Efficiency"? After consulting a bunch of IT companies that's the discovery. "Productivity" means something different for multiple audiences. :) What are your main metrics and what units are you using? (The question of the Tools can be solved after knowing this)

I think the key point would be to avoid reaching that point. Drive the conversation in a way that you won't misread anything. You ask questions and complete all the gaps possible before jumping into any conclusions. And boom. Civilized conversations appear. Listen first.