Came across a bug in our code today where we were trying to store to large of a value in a database field. Turns out we intentionally set the value to a huge number just so that we could tell another process farther down the line that the object containing it needed to be deleted...Really??? Lol

!rant
So on the last day before launch our latest feature I'm informed that a requirement was missed and it had to be implemented before go live otherwise the business didn't want the feature. The feature in question was pretty drastic and basically required a scheme rewrite, new tables, etc. So I spent the entire day making the change.

Thankfully I pushed the whole project for good code coverage. Therefore, all I had to do when I was done was run all of our tests and make sure they passed. *warm fuzzy feelings*

Worst experience: Learning how data is stored in segments in a middleware application called PMS on mainframe and how to manipulate that data.

Best Experience: Building a app that lets you pull down any set of segment data from mainframe and figuring out a way to automatically annotate the data so you could just hover over it and you know what the data is exactly. This way I didn't have to constantly refer back to a reference manual to see what a field name is in a segment, or having to go talk to a mainframe developer to go look at their code. Btw, did I mention I made it searchable by field name??

Need to find the visual studio process to kill it because the app is frozen. Pen task manager > processes> sort by memory usage. right there at the top...always at the top...2gb+ usage.

Wrote JavaScript today and it didn't work in chrome and Firefox but it worked fine in IE...I instantly knew I did something wrong.

Started adding new MVC project to main solution at work. Started getting assembly reference errors across the projects during testing. Figured I might as while update the few assemblies that are complaining instead of trying to downgrade to maintain the current state of things. Shouldn't take too long right?....8 hours of staring at configs and running and rerunning nuget commands to get all the versions lined up across 120 projects....thank God we have extensive unit and integration tests...

I wish windows would release a personal version of Windows micro server so that I could only install exactly what I want for my dev workstation through budget packages...*sigh*

Had a 2 hour meeting where I was told to use Specflow for all of our unit and integration testing. It'll be easier for the business to read.

Spent 3 hours setting up the tests for the scenarios for the next story.

Had another 2 hour meeting where they decided it was a bad idea to wrap all unit and integration tests in gherkin...because the business users don't want to read gherkin...

Tried to pull a Java solution, originally developed on linux, into my windows environment to test a Jenkins job. The build job wouldn't run on my box due to reaching the arbitrary max windows path limit in command prompt..why??