# data[].attributes.headline
Rollbacks because of to many cooks in the kitchen

# data[].attributes.subject
Rollbacks because of to many cooks in the kitchen

# data[].attributes.body
THank you for always being willing to tackle tickets together. I feel like our ability to solve them as a team is far greater than solving them as individuals.

# data[].attributes.body
Its tough out here with this thang.

# data[].attributes.body
Chris did an absolute killer job testing for our successful Max Price Adjustment Bug. He had tons of test cases and was extremely thorough. He is one i would follow into the pit of Edge Cases

# data[].attributes.body
self explanatory

# data[].attributes.body
Joey and I ironing out the minor issues we come across in our microservice with relative ease so far, and got our call to match the results from the current job precisely. Matt Lynn taking time to help me debug vendor integration, George putting up with my "do you happen to know" jargon. Sean and Sharon with working with me on the create a loan page. y'all are great

# data[].attributes.body
Working with devops and others to see what we need to do to authenticate the call into our microservice has been quite frustrating. Being told repetitively that we won't have to implement any kind of authentication, and me knowing that can't be true because then our endpoint isn't private.

# data[].attributes.body
Not sure if anyone has felt this way, but it seems like I've had a lot more meetings than usual on my calendar. I know we have to work around the 4x10 schedules, but I feel like my Thursdays in particular are always jam packed full of meetings. Could we possibly explore spreading some of these out a bit?

# data[].attributes.body
Among researching an issue and trying to gain a better understanding of things, meeting with other parts of the business to collaborate on thought processes and brainstorming has helped provide a huge insight that should help guide the project team in the right direction to continue moving forward.

# data[].attributes.body
Between multiple high priority items, there is some intensive research being done to get gears going. However, having a breakthrough on research has been a somewhat slow process. For one item, there is quite a bit of insight on the issue and a really good idea of what could be causing it, but currently finding where this is happening is the big challenge. Shoutout to Joe Sillman however, for jumping into this and taking a look to help dig deeper into research.

# data[].attributes.body
Working with Joey has helped me make much more progress on my High Priority bug than I would have made on my own!

# data[].attributes.body
I want to try at a bit longer then maybe talk to Steven or Shruti (MISMO team) about the code changes I would 'like' to include.

# data[].attributes.body
Even with 3 days off each weekend I can never get enough things done.

# data[].attributes.headline
Getting the 'OK' and gathering feedback from other teams

# data[].attributes.subject
Getting the 'OK' and gathering feedback from other teams

# data[].attributes.body
For my duplicating property taxes bug we have had to run out solution past so many people from the business and BPTs, it's difficult to choose where to focus when we are waiting to hear back from so many voices

# data[].attributes.headline
I Won't Ever Be the Developer I Would Like to Be

# data[].attributes.subject
I Won't Ever Be the Developer I Would Like to Be

# data[].attributes.body
I don't have the time or energy after work to practice nor do I get enough code writing experience on the floor so I feel like I have only regressed in my ability to write code since I graduated Dev-I/X a long time ago. I know a lot of other things which helps carry the workload, but I would like to be capable of writing better code.

# data[].attributes.body
Being the last to know something is always frustrating but increasingly so when the parties you talk to are also in the dark. I was thrown back and forth between Dev ops and the release team when seeking clarity on how to deploy code to the dev branch of uwm.com and it didn't help that it seemed that both groups were unclear on whose responsibility it was to manage the environment

# data[].attributes.body
I fight for my friends.

# data[].attributes.body
EDGE issues locally with my connection strangs (thx Charlie)
-Joey B

# data[].attributes.body
The amount of fast changes (and changes to changes) that are not documented anywhere, is making it difficult to understand elements of our roles. I'm worried to miss a day and be completely out of the loop when I return.
Even when changes might be noted in a teams chat, it's overwhelming to read back through a discombobulated discussion log.

# data[].attributes.body
I have had a temp fix in place for a bug all week, but I have struggled to refactor it into proper prod code because I barely ever get to write code so I am super out of practice.

# data[].attributes.body
Deployed DTI fix for one of the issues this is Joey

# data[].attributes.body
Some bugs are very difficult or almost impossible to replicate. This is very frustrating, especially when it is a high priority bug :(

# data[].attributes.headline
Guidelines for bothering the release team

# data[].attributes.subject
Guidelines for bothering the release team

# data[].attributes.body
Specifically with all of the new red tape around on-demand deploys, it is getting very hard to get the timing right in terms of our code moving through the deploy board in line with when we want to test. I don't want to overburden the Release team with requests, but I need better than a 24-hour window's worth of predictability for when my code will move through the pipeline

# data[].attributes.body
This caused the issue of the trial of error of deployment and then going for one day with no documentation or communication the process has changed.

# data[].attributes.body
Very frustrated at the lack of any documentation on how we're supposed to move our self-deploys through the pipeline.

# data[].attributes.body
There was no communication about changes to the deployment process for self-deploys - I think I spent at least half a week trying to babysit deploys into production

# data[].attributes.body
Gone Friday, now the deployment process has changed another time. It is already hard to get PRs in on time now. We keep getting bombarded with new processes or changed processes to deploy.

# data[].attributes.body
for best quality use on small screen and zoom as-needed. color-code according to color at bottom of section

# data[].attributes.body
Nuff said.

# data[].attributes.headline
BUG will most likely turn into multiple BUGs

# data[].attributes.subject
BUG will most likely turn into multiple BUGs

# data[].attributes.body
My bug that I have is a pretty broad issue, and when we get down to really researching it, it will more than likely be vertically sliced into TWO or more bugs.

# data[].attributes.body
Knowing who to reach out to for specific questions is an underrated ability, and it has truly helped me gain more knowledge of specific issues and where in the code to narrow down and look into.

# data[].attributes.body
These tickets that come in lately have been more involved, more difficult, and less clear than usual. Ready to get off this rotation.