News for hackers. Stuff that matters.
Re:Why ‘your’ programmers just want to code by scarface74 on Saturday March 10, 2018 @12:15PM (#16559265)
So, my job is officially "dev lead" but I'm really just a glorified senior developer who the company (use to) listen to more than other people until they brought in a "scrum master" and started going "agile".

I had one process that I designed that wasn't reliable. I didn't realize it until the volume started going up. The people in the field were complaining about the process not working reliably, somehow that got translated to senior management as "performance issues", by the time it got back to the "scrum master" and my immediate managers, I was being criticized about working on "the wrong thing" because I was focusing on health checks, auto recovery, scalabiliy, high availability, and most importantly improved logging to determine what the issues were instead of making it faster - ie improving the speed (performance).

After much arguing, I was able to prioritize one improvement that would improve reliability when processing large data sets and I was able to prioritize logging of both successes, failures and time it took to run queries.

I was not able to prioritize connection resiilliancy even though I knew that was part of the issue.

So we had a big outage while we were working on the "performance issues" caused by spotty network connections that could be improved if we implemented retry logic (that got deprioritized). But we couldn't add the resiliency because it wasn't going to make things faster and it wasn't part of the sprint. What was even worse was that part of the exception message from Entity Framework said that the error was "transient" and that we need to Implement a resiliency policy.

Another part of the issue was based on an unoptimuzed set of queries that were causing reliability issues and that was prioritized. But while implementing that, I realized that there were other performance bottlenecks caused by API calls of semi static data that could be cached. I did a simple in memory cache and was lambasted about that since it "wasn't part of the story".

At that point, when you can't change your environment is time to change your environment. But in the meantime, it's a matter of communicating to senior management the decisions that were made by the scrum master and my manager.

On the other hand, I always keep my resume updated, my network fresh, and my skill set in line with the market....

There are no comments on this comment yet.