Diego Alonso Álvarez tries to help developers lose their fear - or reluctance - to invest time creating a GUI for their research software, and help them to take those first steps in the development of graphical user interfaces.
Diego Alonso Álvarez tries to help developers lose their fear - or reluctance - to invest time creating a GUI for their research software, and help them to take those first steps in the development of graphical user interfaces.
This is the second part of two blog posts discussing the advantages of adopting FAIR for research software, the current adoption practices of software across organizations, the attitudes towards adoption, and the motivations and barriers for adoption.
This is part one of two blog posts discussing the advantages of adopting FAIR for research software, the current adoption practices of software across organizations, the attitudes towards adoption, and the motivations and barriers for adoption.
Registration is open for a Workshop on Graphical User Interfaces (GUI) for Research Software, running from 27 - 29 April. The workshop aims to help developers lose their reluctance to invest time creating a GUI for their research software.
By Patrick McCann, Rachel Ainsworth, Jason M. Gates, Jakob S. Jørgensen, Diego Alonso-Álvarez, and Cerys Lewis. This post is part of the CW19 speed blog posts series. What are the challenges? For many researchers, the development of software is a means to an end—a chore that is necessary to allow them to get on with the real work of conducting research and publishing papers. They may not see themselves as programmers or recognise the code that they write as being software. Their supervisors or senior colleagues may not see the value of devoting perceived extra effort to following good…