Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Radoslav was the CTO of Product Hunt. He recently built Angry Buildings as the single technical person on the team. This talks is about how he did it all by himself.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In Radoslav Stankov's talk at the Balkan Ruby 2024, he discusses his journey of creating the facility management software, Angry Buildings, as the sole technical person on the team. The presentation covers the inception of the idea, the development process, and the challenges faced while building a successful product aimed at businesses. Stankov emphasizes the importance of context in engineering decisions and shares insights on achieving Product-Market Fit. Key points discussed include: - **Product Background**: Angry Buildings is a facility management software evolving from a side project into a scalable ERP system. - **Motivation**: Stankov’s focus shifted from his responsibilities as a CTO to a passion for working on Angry Buildings, leading him to pursue it full-time. - **Team Dynamics**: The team consists of primarily non-technical positions, with Stankov managing all technical aspects alone. - **Business Strategy**: The initial audience targeted were individuals, but a pivot to facility management companies was made based on market needs and available resources. - **Customer Acquisition**: Maintaining zero churn illustrated the product's reliability, with current users managing approximately 30,000 apartments. - **Mistakes and Learning**: Stankov openly discusses the challenges and mistakes made during development, such as misnamed database fields and premature expansions. - **Technical Stack**: The software utilizes Ruby on Rails as its primary technology, with React Native for mobile applications, emphasizing simplicity and functionality. - **Client-Centric Approach**: Success in serving clients was achieved through an import feature that streamlined data transition, emphasizing the importance of feedback and user needs. - **Development Practices**: The speaker describes effective coding practices, such as using specific gems for functionality, maintaining extensive test coverage, and ensuring organized project management. In conclusion, Stankov advises future developers to target businesses with non-existent systems to facilitate easier transitions and stresses the necessity of integrating sales and customer support roles within the developer framework to enhance product development. This talk serves as a guide for engineers looking to transition into product development and the importance of agile responses to customer feedback.
Suggest modifications
Cancel