Jacob Bednarz

After spending a lot of time with OpenAPI schemas and trying to answer the question of “are my HTTP requests and responses actually conforming to what my users are sending and receiving?”

In today’s tech-driven job market, Restricted Stock Units (RSUs) are marketed like pots of gold that companies are willing to hand over to the right candidates.

In every generation, a new gold rush emerges.

In the frozen wilderness of Antarctica, emperor penguins do something extraordinary.

At NASA’s Jet Propulsion Laboratory (JPL), there is a tradition for “lucky” peanuts to be present at every launch.

For much of my career, I’ve been in positions where I was sought out to provide guidance for larger or more complex tasks.

I regularly need a way of running a container (mitmproxy or tcpdump) against another running container.

Today while performing some basic networking connectivity tests between Kubernetes namespaces, I found myself without redis-cli which is what I’d usually reach for to test connectivity to a Redis instance.

For the longest time, Terraform Registry documentation has been manually updated as the resource is created or modified.

Since we purchased our new house in 2015, I’ve slowly been building up the home network and the components in it.

If you’re working on a Terraform provider, chances are at some point you want to run in against your configuration before pushing the changes publicly.

Like most of you reading this, I have important personal data scattered around on various devices (external hard drives, iOS devices, The Cloud™) and until recently, this had not bothered me too much.

For the majority of my engineering career, I’ve been on-call in some capacity.

In 2014, I was being bewildered and overwhelmed with the amount of options for a simple to-do list style application.

Being a combination of remote worker and having a partner who loves travel has forced me to continuously evaluate my travel gear and setup to get the most out of the trip.

Just on 10 months ago I joined Envato as a Site Reliability Engineer and took the plunge into full time remote work.

When you run a large application (or many large applications), it is important that you can effectively track down and investigate slow SQL queries when they arise.

Whether you run a service or provide a product to customers, there will be times when your service (or part of it) is unexpectantly unavailable.

When you are working on a large project sometimes you need the ability to gradually roll out a new feature to public facing users.

Building RESTful services within Drupal isn’t a new concept and there are already a lot of existing projects out there that will allow you to build a simple REST service.

Something that all API’s need to consider (no matter how simple they are!)

Monit (as the name suggests) is a tool designed for monitoring systems, processes and filesystems.

Bootstrapping a project is a concept that I first seen derived from Ruby on Rails script/server and I was instantly hooked.

As all Ruby developers will know, dependency management and isolation in projects is paramount.

I recently started building a new service in Ruby on Rails and had the need to build an API that users can interact with for their own applications or tools.

Within my daily workflow I can work on 5-6 projects over the course of the week and the likelihood of anyone remembering the exact dependencies and requirements for each environment is close to impossible.

One thing that is overlooked and under rated in team projects and especially open source collaboration is a good commit message and the benefits that come from that good commit message.