Uncategorized

Test Blog Post with Blocks

This is a test blog post. Here is some sample content: When it comes to DeviceOps, there are two core responsibilities that need to be considered. The first responsibility is the device configuration owner. This is the person or team who is responsible for telling the Mason system how to set up the device. In our system, this person owns projects. A project has configurations, which are the details for how a Mason device is set up at the OS and applications that will be installed on the device. We maintain a history of configurations within a project, and projects can span multiple devices. With these tools, we create a development loop to allow teams to deploy and test their Mason projects on their test devices.

“This is exactly what you want as a developer for this kind of use case. It’s set up like modern build tools are.”

Patrick O’Donnell – GGV Capital Incorporated

Director of Software Development

This is a test blog post. Here is some sample content: When it comes to DeviceOps, there are two core responsibilities that need to be considered. The first responsibility is the device configuration owner. This is the person or team who is responsible for telling the Mason system how to set up the device. In our system, this person owns projects. A project has configurations, which are the details for how a Mason device is set up at the OS and applications that will be installed on the device. We maintain a history of configurations within a project, and projects can span multiple devices. With these tools, we create a development loop to allow teams to deploy and test their Mason projects on their test devices.

Relevant blog stats and numbers for Mason

54%

Growth in sales

13

New partnerships

1m

Quarterly goal hit

99%

Sure I made this up

This is a test blog post. Here is some sample content: When it comes to DeviceOps, there are two core responsibilities that need to be considered. The first responsibility is the device configuration owner. This is the person or team who is responsible for telling the Mason system how to set up the device. In our system, this person owns projects. A project has configurations, which are the details for how a Mason device is set up at the OS and applications that will be installed on the device. We maintain a history of configurations within a project, and projects can span multiple devices. With these tools, we create a development loop to allow teams to deploy and test their Mason projects on their test devices.