For our second community meetup we focussed on using Civo for CI/CD through GitOps and Github actions for cloud native application development This installment featured talks from our CTO Andy, our Developer Advocate Kai, and guest talks from community members Sam Weston and Johannes Tegnér. The talks touched on a wide variety of topics within CI/CD, from automating builds to monitoring and observability. Here's what was on the agenda...

Interviewing for a new job and finding your right fit is tough enough, not to mention the added stress of interviewing during the COVID-19 pandemic. As stated on our Careers Page, our process is pretty consolidated and we move quickly (you have to when you’re a growing tech company).

CIOs see data costs as their greatest logging challenge to overcome, according to this survey we collaborated on with IDC. If you’re running significant production operations, you’re almost certainly generating 100’s of GB of log data every day. Naturally, you’re also monitoring those logs and querying for incident investigations. However, most log data is never queried or analyzed, yet makes up the majority of logging costs.

Military strategists will often tell you that the best way to win a conflict is to prevent it by projecting an unmistakable posture of strength, preparedness and resolve. As history has shown in the seven decades since the Second World War, deterrence doesn’t come cheap, certainly not in the era of modern, technology-enabled warfare. Yet it is still far less costly in lives, dollars, and equipment than letting a hostile situation escalate out of hand.

Agile is a popular buzzword in software development, with some organizations and teams masquerading as “agile” while they are actually doing something very different. I’ve seen it numerous times in my career as an Agile Coach: A leader claims to embrace agile values, but micromanages engineering teams and uses agility as a way to manipulate developers to work long hours. The result?

2020 keeps on proving the old adage, “It gets worse before it gets better.” We still seem to be in the “worse” stage. If you’ve been paying attention to the news—and I don’t blame you if you’ve been taking a break for sanity’s sake—you might have noticed (in addition to the reports about the pandemic and social issues) hacks and general security breaches have been ramping up.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.

If you know anything about WebAssembly (WASM), it’s probably that WASM lets you execute code compiled from languages such as C, C++, Rust, or others in the browser at almost native speeds. You might be less familiar with the fact that WASM is not only an interesting technology in the browser, but also in other environments that require fast sandboxing. As such, WASM has found some popularity with edge computing and as a lightweight docker replacement for certain situations.

Cloud computing can be more complex than anticipated, particularly as agencies continue to move applications and operations into a cloud environment. Does your federal IT team have the in-house skills to ensure cloud computing is helping your agency rather than draining its money and resources?

We just released Ruby Gem 2.11. We are always making things easier to use for you, so more things work out of the box and more instrumentation and dashboarding is built without you doing any heavy lifting. This release has a big overhaul of Active Job support. The cherry on the stroopwafel cake is the automatically generated dashboard with status per queue, queue throughput and queue times. 2.11 also polishes a lot of other integrations. Let’s dive in.