Manual creation of GitLab projects has been okay, but consistency among projects for such as protected tags requires a procedure be followed, which tends to be a brittle solution. Using Terraform we can create projects configured as we like them, with the added bonus of easily disabling all the features we don't need.
We create issues for all implementation work and generally for analysis work as well. (Other work such as consultations, meetings, e-mails, professional discussions are not tracked, obviously, so it’s important to note that time spent on issues is not expected to add up to the seven-hour workday.) Issues help us track and prioritize work that needs to be done as well as features we may or may not tackle in the future.
Regardless of language or environment, there are core principles we follow in software development, to encourage readability, maintainability, and joy. Each member of the team is responsible for adhering to these principles and guidelines and to assist and encourage others in doing so.
We’ve been building REST APIs for some of our projects. One of the struggles that I’ve personally faced was deciding on the URL structure for the endpoints. After some trials and errors and learning from others, here is a set of conventions that I think we should follow.
It can take a while to learn a team’s culture, and there’s no quick solve for that: it’s the culmination not only of the group’s shared experience but the years of lived experience each individual brings in, and it evolves over time and is always unique. Expected practice, on the other hand, can and should be clarified–and if your team culture has “inclusion” as a core tenet, then setting clear expectations is essential to keeping everybody on the same page.
We found as development on ZooDB progressed and the amount of data involved increased, especially with intricate queries involved in each view, page loads became slower than we'd like. In this blog post we describe some of the strategies we used to improve performance.
OpenStack is open source software for running cloud services. Recently I worked on a Python program that would scan ARC cloud instances and determine which instances have been running longer than their allotted time. This mostly used the compute API which is a proxy for OpenStack’s Nova service.
Indentation is more than just a matter of aesthetics in coding; in some languages like Python, it holds a semantic value. It’s a fundamental part of how code is structured and readable. It helps to organize your code, making it easier to understand and maintain. In this blog post, we will explore the basic indentation rules for four popular programming languages: JavaScript, HTML, Django, and Python.