Was working on a high priority security feature. We had an unreasonable timeline to get all of the work done. If we didn’t get the changes onto production before our deadline we faced the possibility of our entire suit being taken offline. Other parts of the company had already been shut down until the remediations could be made -so we knew the company execs weren’t bluffing.

I was the sole developer on the project. I designed it, implemented it, and organized the efforts to get it through the rest of the dev cycle. After about 3 month of work it was all up and bug free (after a few bugs had been found and squashed). I was exhausted, and ended up taking about a week and a half off to recharge.

The project consisted of restructuring our customized frontend control binding (asp.net -custom content controls), integrations with several services to replace portions of our data consumption and storage logic, and an enormous lift and shift that touched over 6k files.

When you touch this much code in such a short period of time it’s difficult to code review, to not introduce bugs, and _to not stop thinking about what potential problems your changes may be causing in the background_.

!rant

I just got the best pe of my carrier.. Got some extra cash, and new future career path goals..

sometimes it’s hard being in this industry, but when you find a great team, you’ll know by the support

🍻 happy Friday!

Was asked today what type of service ticket was needed for a domain level whitelist request.. gave them the answer, and they tell me, “oh I don’t think I want to do that, I’ll just create a generic ticket and go from there.”

Why ask if you are going to do it your own way anyways..

This happens to often in all parts of IT. Someone consults you, tells you your suggestion sounds difficult, then try’s to take a short cut..

Good luck to them.. so glad it’s Friday! ✌️

Posted in DevOps discussion board (teams channel):

“Program x isn’t behaving the same way that it does on production. Can you please take a look?”

..a little background: we have a deployment scheduled for today and this issue was found during regression testing.

The issue found is that when a file is clicked on it disappears from the screen, and then isn’t opened…

The file is not on prem, and doesn’t get uploaded to a server that our DevOps team owns…

So why on earth would this development team be asking DevOps to look into a bug that is most likely a code related issue? 😆

Is this a common occurrence for anyone else?
A Bug is found, and the first thought is that the code isn’t the issue?

Got an email from a recruiter.. he went on to outline how great I’d be for the job he had in mind…

Then ended the email with: Let me know if you are interested, OR if you have a referral for this position.

WHAT?! I thought I was perfect for this position.. why are you asking me to refer someone else? Ug.

Ability to ask the right question the first time.

Sometimes the hardest part of development work is first understanding the question that’s needed.. the answer isn’t typically hard to formulate from there.

Code is not self documenting..

reading 10k+ lines of business logic does not take the place of well defined documentation.

Mic drop.