Search for a command to run...
A DevOps/Cloud Architect experienced with building and automating DevOps processes and tools for engineering teams encompassing cloud-native applications. Extensive background experience working with AWS and Microsoft Azure cloud services building hands-on robust and scalable solutions and services.
No comments yet. Be the first to comment.
The Evolution of DevOps - The Golden Age Let's wind the clock back a couple of decades to the late 90s and early 2000s, a time when most organisations had a single gatekeeper: the system or IT administrator. If engineering teams needed to run their a...
Organisations today are increasingly adopting cloud services from different providers to meet their business needs. However, managing multi-cloud infrastructure can be challenging, especially when it comes to infrastructure management, which is where...
What is AWS CloudFront? AWS CloudFront is a content delivery network (CDN). It securely delivers data, videos, applications, and APIs to customers globally with low latency and high transfer speeds. It offers a simple and cost-effective way to distri...
DevOps is more than just a software development methodology – it's a culture. The DevOps culture emphasizes 3 main pillars: collaboration, communication, and shared responsibility between development and operations teams. In this post, we will discus...
On this page
This guide presents a comprehensive set of rules for software engineering inspired by the movie Zombieland. The rules are not simply a list of arbitrary guidelines, but rather a carefully crafted set of principles that are designed to promote efficiency and effectiveness in software development. By drawing inspiration from the movie, these principles are not only practical but also engaging and memorable.
Rule #1: Cardio - Keep your code lean and agile to ensure quick and efficient processing.
Rule #2: Double Tap - Test your code thoroughly to ensure it's not just "undead" but truly dead before moving on.
Rule #3: Beware of Bathrooms - Be cautious when accessing sensitive parts of the codebase, such as login or payment processing modules.
Rule #4: Seat belts - Always use version control and back up your codebase regularly to safeguard against crashes and data loss.
Rule #7: Travel light - Avoid bloated software by minimising dependencies and optimising code for performance.
Rule #8: Kill Efficiently - Identify and fix bugs quickly and efficiently to prevent them from spreading and causing more harm.
Rule 9: A club does not have to be reloaded - Automate repetitive tasks to increase productivity and reduce errors.
Rule 10: Don't make any noise - Keep your code clean and organised to make it easier to understand and maintain.
Rule 15: Keep an exit free - Plan for scalability and flexibility in your code to allow for future changes and updates.
Rule #17: Don't be a Hero - Don't try to reinvent the wheel. Use proven software engineering patterns and best practices to avoid common pitfalls.
Rule #18: Limber up - Stay up-to-date with the latest technologies and tools to remain competitive in the industry.
Rule #22: When in Doubt, Know Your Way Out - Have a plan in place for handling unexpected errors and failures.
Rule #23: Ziploc™ Bags - Protect sensitive data and prevent breaches by implementing robust security measures.
Rule #31: Check the Back Seat - Don't forget to review and test all aspects of your code, including less frequently used features.
Rule #32: Enjoy the little things - Take time to celebrate small successes and accomplishments throughout the software development process.
Rule #36: Sunscreen - Protect your eyes and health by taking breaks and practising good ergonomics while coding.
Rule #42: Keep your hands to yourself - Follow coding standards and respect the work of your colleagues to maintain a positive and efficient work environment.
Rule #52: Don't be afraid to ask for help - Seek advice and guidance from more experienced developers to learn and grow in your career.
Rule #53: Wet naps - Clean up messy code and fix technical debt regularly to maintain a healthy and sustainable codebase.
This guide presents a unique and engaging set of principles for software engineering inspired by the movie Zombieland. By following these rules, software developers can improve the efficiency, effectiveness, and quality of their work. The rules cover a wide range of topics, from testing and security to teamwork and innovation. Whether you're a seasoned developer or just starting out, the principles presented in this guide can help you succeed in the challenging and dynamic world of software engineering.
