Suggest modification to this talk

Title

Description

RubyConf AU 2014: http://www.rubyconf.org.au

Not too long ago, a small group of developers inside Envato embarked on a mission: take an idea, and turn it into something real. To accomplish this goal, they didn't just have to build the product, but change the way they were writing and shipping code as well. In the end, the way they were delivering was radically different to anything they'd ever done before. The result? Mission accomplished.
This talk explores the core tenets of the team's delivery process, and explores the reasons behind the decisions that were made. It mixes anecdotes with practical examples, showing how changing the way you think can really help get things done.
Some of the tenets in the talk include:
Level up your CI to continuous deployment Time is valued above all Staying lean with YAGNI Pay the refactor cost upfront Testing is best done in production Do things that don't scale Living on the bleeding edge The only way to move is forward After listening to this talk, you will know how easy it is to introduce these principles into your Rails app. You'll be armed with ideas of what you can take home to your team, in order to deliver better and faster than before.

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 his talk "Real Developers Ship" at RubyConf AU 2014, Sebastian von Conrad shares the journey of a development team at Envato as they built and shipped a new product, Microlancer. Focusing on fundamental principles for effective software delivery, Von Conrad discusses actionable tenets that transformed their workflow and led to improved results in shipping products.

The key points of the talk include:

- **Fake it until you make it**: The team quickly launched a low-fidelity version of the product to gather real user data and validate their assumptions.  
- **Cut the crap**: They simplified their task management by focusing on essential actions instead of adhering strictly to methodologies like Agile or Scrum.  
- **Elevate your CI to Continuous Deployment**: By leveraging Continuous Integration that automatically pushed successful builds to production, the team minimized risks and increased the frequency of updates.  
- **Test in production**: Utilizing feature flags permitted the team to test new features in a live setting while maintaining control over when they were activated.  
- **The only way to move is forward**: Instead of rolling back code, the team focused on fixing issues directly, ensuring continual progress.  
- **Live on the bleeding edge**: Keeping dependencies up-to-date through daily bundle updates helped the product remain optimized and functional.  
- **Pay the refactor cost upfront**: They emphasized writing code with the expectation of future changes and cleaning as they went, rather than scheduling dedicated time for refactoring.  
- **Stay lean with YAGNI**: The principle of "You Ain't Gonna Need It" encouraged the team to prioritize essential features and avoid premature implementation of unnecessary functions.  
- **Do things that don’t scale**: The team began with manual processes to understand workflows fully before automating, ensuring effective solutions.  
- **Time is value**: Finally, they highlighted the importance of optimizing time spent on coding, testing, and deployment to continually provide users with added value.

In conclusion, the talk presents a comprehensive approach to software delivery that prioritizes speed, efficiency, and customer value. By adopting these principles, developers can significantly enhance their workflows and product outcomes.

Cancel