Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
If you have ever built a web application, chances are that you have also had to deal with "the back office" - the chores and one-off tasks required to operate your software in production. Workflows that aren't user-facing, like creating promo codes, moderating content, or running reports, are often a janky combination of admin scripts and spreadsheets. Retool helps developers quickly and easily solve these problems with software instead. In this session, we'll show how to build a back office interface for a Ruby on Rails application using Postgres and several common API services, so you can keep your focus on the business in the front, and let Retool help throw the party in the back (office).
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 the presentation titled "Business in the Front, Party in the Back (Office)" delivered by Kevin Whinnery at RubyConf 2022, the primary focus is on the significance and development of back office applications in software environments. The talk begins by differentiating between two types of applications: customer-facing applications and back office applications. The former typically receive greater attention and resources due to their direct impact on revenue, while the latter, which are crucial for internal processes, often suffer from underinvestment. Key points discussed include: - **Dual Nature of Applications:** The distinction between customer-facing and back office applications is crucial. Customer-facing apps prioritize user experience and UI polish due to their external impact, whereas back office applications focus on utilitarian functionality for internal users. - **Investment Challenges:** Back office tools are often underfunded, primarily because they do not directly drive revenue despite their essential role in efficiency and operational success. This often leads to reliance on inefficient workarounds, like scripts and spreadsheets. - **Long-term Considerations:** Developers are encouraged to think beyond the immediate needs of internal tools and consider long-term scalability, maintenance, and integration complexities. - **Retool as a Solution:** The presentation highlights Retool as an effective platform for constructing internal applications swiftly and intuitively. Whinnery provides a demonstration of building a back office interface for a Ruby on Rails application using Postgres and API services. - **Demo Segment:** In the live demonstration, he creates an administrative interface for managing blog posts and comments, implementing CRUD operations. He emphasizes the integration of rich functionalities using Retool, demonstrating how to link frontend UI components effectively with backend data sources. - **Final Thoughts:** Whinnery concludes by reiterating the value of investing in internal tools and highlights the capabilities of Retool in bridging the gap between ease of use and powerful functionality, reinforcing operational efficiencies within organizations. Overall, the session conveys the message that while customer-facing applications may capture the limelight, fostering robust internal applications is integral to organizational success and efficiency.
Suggest modifications
Cancel
