That's not true. There have been lots of companies that couldn't raise money at one point but ultimately succeeded.
— Paul Graham (@paulg) July 20, 2023
In effect you're saying "investors have good judgement," and any founder knows how laughably false that is.
This article was insightful in regards to job hunting and all. Its a long read, but if you have the time, read it: https://t.co/y9Ap55EPgm
— Obiagu (@iamCynthiaPeter) July 17, 2023
Instead of MVP, start with Minimum Viable Tests to increase chances of succeeding with your startup idea. https://t.co/5VVpJxoIFQ by @gaganbiyani
— Volodymyr Melnyk ЁЯЗ║ЁЯЗж (@vamelnyk) July 15, 2023
How Instagram Co-founder Mike Krieger Took Its Engineering Org from 0 to 300 People At the time of the acquisition, he had just six generalist developers. ......... In just seven years, Krieger himself went from first-time manager to leading a multi-layered organization of specialized engineers, many of whom are the best in their fields. ........ how to gracefully transition from an early to a more mature technical team, how to introduce new tiers of management, and how to build an engine for unrelenting improvement and innovation. .......... “Have you heard that expression, ‘shaving the yak’?” Krieger says. “Sometimes programming means solving super complex technical problems. But a lot of times, you end up with a long string of tasks that are necessary to get where you’re going, i.e. ‘I need to get this iPhone app running on my device, which means I need to generate this provisioning profile, which means I need to set up for this account, and on and on.’ In the end, you’re shaving a yak to accomplish that original action — you’re so detached from it.” ............ An effective engineering generalist knows when to move on............ Put pride aside and keep your eye on your real goal. “The goal is not to set up Nagios or Munin. The goal is to ship software so that you can get people using it.” ......... In the early days of Instagram, Krieger and and his team recorded their action items in a rolling Google Doc, organized by themes. ........... “One of our themes was being the fastest photo-sharing app in the world. What are we working toward within that theme? Next, we wanted to make the photos look incredible, way beyond what you'd expect from a cell phone. What are we doing on that? Anything that didn't fit into those things went by the wayside. And you want engineers who are okay with that.” ............. The Google Doc was the perfect minimally viable product for tracking all tasks as a team — and making sure that every single one of them rolled up to one of the organization’s most important goals or priorities. It was broken up into days, and under days into themes. Uncompleted tasks under each theme were migrated to the next day. Highest priority tasks were labeled as such. That way, nothing got lost in the mix, it was easy for people to comment and ask questions, and their eyes were always fixed on what was next for the goals they needed to achieve.