When designing and building a web application, ensuring that it is responsive is paramount. A responsive application looks good and functions well on all screen sizes and devices. LINCS applications are being designed to be viewed in a wide range of ways: from tablets to laptops to whiteboard-sized interactive screens. It can be quite hard to achieve this level of responsiveness, but with the help of CSS tools, techniques, and frameworks, the task becomes a lot easier...

In my first meeting this summer as a data science research assistant, we each followed our personal introductions with declarations of our favourite ice cream flavours. Mine was and continues to be Häagen Dazs’ Strawberry Cheesecake ice cream, and I was pleasantly surprised to learn someone else on the team felt the same. However, the biggest surprise was learning that someone enjoyed microwaving their ice cream to change its texture. At that point is it still ice cream? Is it soup? Or a milkshake? What even counts as ice cream? ...

I’ve always found that context changes everything when learning something new, especially when it comes to understanding why that something matters. The first example I can think of is how, for all the general chemistry courses I’ve taken, the concepts never really clicked, nor did I see why I had to learn them. Four of these courses later, I wasn’t very excited to take biochemistry, but when I did, I couldn’t believe how much of a difference it made to have a real context: the human body, where chemical reactions happen for a reason. Suddenly, the abstract became pretty important—I could see how it all fit together, and in turn, my understanding of general chem probably increased threefold. Rest assured, this blog post is not going to be about chemistry. Rather, it’s about how the same phenomenon occurred this summer, when working on the Orlando Project changed the way I think about data...

LINCS is using ResearchSpace as a platform for exploring relationships in interlinked cultural datasets. With ResearchSpace, researchers can browse, search, and visualize data in the LINCS datastore. In summer 2022, I was part of a team that was developing new features for LINCS’s version of ResearchSpace.

Our team was a collaboration between contributors with a background in user experience (UX) and contributors with a background in software development. We worked in tandem: the UX group recommended features to improve the experience of using the web application. These recommendations were turned into tickets in GitLab. The tickets described what the desired end product would be, and it was up to the developers to determine how to achieve this goal. The development lead shared tickets out among the software developers, dividing them up based on what would be required to build the suggested features...

The UX team has been conducting user research on LINCS tools to get them ready to move from development to production. So far, we have completed card sorts, usability tests, surveys, and interviews. This research has provided us with a wealth of information. However, if we want to translate what we’ve learned into meaningful, productive changes to the tools’ designs, we must keep actionability at the centre of our research practice...

When I began my first co-op placement, I had no idea how software development worked in a professional environment. Previously, my experience had only been in the classroom, where  my classmates and I developed software for assignments. When I moved into a professional context, I was exposed to new ways of collaborating, among them stand-up meetings, or stand-ups...

As an English student, I was always told to keep my writing concise. Doing so was often easy because I could assume that the person reading my work would be an English scholar, so their expectations of my writing and the knowledge they brought to it would sit within a very specific range. In this way, I trained myself to default to an academic tone and level of complexity and to produce writing that was comparative and analytical.

This summer, however, as a member of the LINCS documentation team, I worked on an entirely different kind of writing: user guides and instruction manuals for the many software tools developed or employed by the project. To begin writing documentation, I first had to relearn how to write...

If you’ve ever listened in on a technical conversation between computer scientists, you might’ve heard them refer to something called an Application Programming Interface (API). What exactly is an API? Let’s break it down...

Pendant mon séjour chez LINCS, l'équipe UX a jeté les bases de la mise en œuvre d'un flux utilisateur intuitif et sans effort pour ResearchSpace. Pour ce faire, nous avons mené de nombreux tests d'utilisation et d'utilisabilité, des entretiens et des tris de cartes.

Travailler sur ResearchSpace a été ma première véritable expérience dans le monde de l'UI/UX. C'était aussi la première fois que je travaillais dans une équipe de conception, et j'ai été époustouflé par le talent de mes pairs...

Au cours des deux dernières années, j'ai eu l'occasion de travailler sur de nombreux aspects du projet Orlando, mais le travail que j'ai toujours trouvé le plus intéressant a été la recherche et auteur de l'écriture profils. Les profils d'Orlando sont des histoires savantes rédigées en collaboration, qui sont structurées par un XML, et qui permettent aux chercheurs d'explorer les intersections entre la vie des femmes et leur production créative. Au cours de mon premier été en tant que Digital Humanities (DH) Assistante de recherche, j'ai commencé à travailler sur le profil de Lili Elbe ; l'année dernière, j'ai commencé à écrire un profil sur Gurpreet Kaur Bhatti. En mettant la touche finale à ces profils, j'ai remarqué que les histoires de vie des deux femmes mettent en évidence le chevauchement entre le personnel et le politique, et entre l'identité individuelle et les limites imposées au travail créatif...