-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
On a normal day, I've usually got tasks from our sprint. For example, recently we got a New Relic plugin deprecation notice, so I spent the last couple days porting our build infrastructure metrics from the old plugin stuff to use the more modern AWS Cloudwatch -> New Relic integration, plus did some related misc alert cleanup. The rest of the week I'm probably going to help with some bugfixes on our custom Git GUI. Then next sprint I'm setting up some tooling to help us clean up some problematic terminology in our code to be more inclusive, using stuff like https://github.com/get-woke/woke plus https://pre-commit.com/ probably. And then after that is my turn (I think?) to be "Dev on Duty", just handling whatever emergent issues come up, like build nodes dying or support requests from our team when they ask for help debugging weird build failures or whatever. And then after that we're doing some groovy cleanup and refactoring to help keep our pipeline maintainable. So pretty much it varies wildly.
On a normal day, I've usually got tasks from our sprint. For example, recently we got a New Relic plugin deprecation notice, so I spent the last couple days porting our build infrastructure metrics from the old plugin stuff to use the more modern AWS Cloudwatch -> New Relic integration, plus did some related misc alert cleanup. The rest of the week I'm probably going to help with some bugfixes on our custom Git GUI. Then next sprint I'm setting up some tooling to help us clean up some problematic terminology in our code to be more inclusive, using stuff like https://github.com/get-woke/woke plus https://pre-commit.com/ probably. And then after that is my turn (I think?) to be "Dev on Duty", just handling whatever emergent issues come up, like build nodes dying or support requests from our team when they ask for help debugging weird build failures or whatever. And then after that we're doing some groovy cleanup and refactoring to help keep our pipeline maintainable. So pretty much it varies wildly.
Related posts
-
Implementing Quality Checks In Your Git Workflow With Hooks and pre-commit
-
[Tool Anouncement] github-distributed-owners - A tool for managing GitHub CODEOWNERS using OWNERS files distributed throughout your code base. Especially helpful for monorepos / multi-team repos
-
How to Write Impeccably Clean Code That Will Save Your Sanity
-
I’m a hack and a fraud - what are some dead giveaways that someone is self taught?
-
Regarding securing confidential data without enabling secrets scanning