Maximize Your Hackday Success: Technical Considerations for Extra Marks
Enhance your chances of impressing judges with key technical considerations for hackdays like clarifying requirements, focusing on coding aspects, using version control, and showcasing future potential. Learn how to approach development, what to consider when coding, and the value of clear implementation and infrastructure. Follow best practices for sustained success post-hackday.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
www.software.ac.uk CW2016 Hackday Technical considerations or How to score extra marks with the judges CW2016 March 22nd, 2016 Steve Crouch, Research Software Group Lead, SSI s.crouch@software.ac.uk Software Sustainability Institute
Enjoy yourselves! www.software.ac.uk Formal vs Fun! (?) Software Sustainability Institute
Before you start www.software.ac.uk How to approach development? e.g. clarify requirements, planning, architectural design, implementation choices? Who will be responsible for what? Consider short development cycles Use of collaborative tools GoogleDocs Slack Software Sustainability Institute
What to consider when coding? www.software.ac.uk Which aspects to focus on? e.g. maintainability, readability, usability, reliability, reproducibility, performance? What s going to make it easier for you to continue after the hackday? Software Sustainability Institute
Implementation and Infrastructure / reproducibility www.software.ac.uk Thou should use version control! When to check stuff in, how open, what to put in it e.g. code, data, even unit tests? Short cycles - always have something to demo Documentation? Issue tracking? For reproducibility Ideally: a README, how to configure, build and run 1st Tag 2nd Tag 3rd Tag Software Sustainability Institute
Implementation and Infrastructure www.software.ac.uk Value of work should be clear or lose marks! Context - building on existing work, starting something new? What does your software/scripts do? How does it benefit others, and who? What s novel about your work? Have 100-150 word summary in README Software Sustainability Institute
Generally www.software.ac.uk Criteria: future potential What about after the Hackday? Mention some interesting ideas for future steps in your README (or a GitHub issue?)! Think about which license to use early e.g. Apache, BSD, GPL, LGPL, Start as you mean to go on! What practices? How open? Don t have too much, but how much is enough? Hackday as microcosm for long-term? Decide early, adhere early, revise later! Software Sustainability Institute
