A day in my life. This morning Dell was doing it's update on my laptop before I left for work, so later when I knew my wife was up I asked her via text to shut my laptop off.

W: "You left your laptop on this morning."
Me: "I know, it was still doing an update this morning. I sent you a text."
W: "Leaving your computer on all day is going to burn it up."
Me: "Its 8:30, been maybe a half hour isn't a day."
W: "Still wasting electricity. How do I turn this thing off?"
Me: "It's just like yours."
W: "No, your computer is way different than mine. Just tell me how to turn it off"
Me: "My computer is running Windows 11, yours is Windows 10, shutting down is exactly the same"
W: "I don't understand, yours looks completely different. Stop being an ass and just tell me"
Me: "Select Start, then shut down"
W: "Select what? There isn't anything that says Start"
Me: "Sorry, click the little icon in the bottom left. Looks like four little blue squares. That's the Windows Start menu button, just like yours."
W: "OK, now what?"
Me: "Shut down"
W: "Shut down what? I don't see anything"
Me: "The icon that looks like power button next to my name"
W: "There is nothing next to your name except your picture"
Me: "It'll be on the right hand side"
W: "Where the clock is?"
Me: "No, on the Start menu, where you see my picture, there should be a button to turn it off."
W: "No, it went away"
Me: "What do you mean went away?"
W: "All that disappeared when you told me to click over by the clock."
Me: "I didn't say to click on the clock, anyway, doesn't matter. Start over, select the icon in the bottom left"
W: "You're not listening. There is nothing there when I click that. You're such as ass. You cannot even tell me how to turn off this stupid computer. I'm busy, you can turn this thing off when you get home."
<a few minutes later I text my daughter>
Me: "Baby girl, can you turn off my computer?"
<10 seconds later>
H: "Done. Anything else?"
Me: "Nope. Thank you."

Overnight, our networking dept patched some systems, which unexpectedly caused a connecting system unable to work. That system was our alerting layer, which didn't/couldn't send out the alerts (phone calls, Teams messages, emails, etc) that alerting wasn't working.

This morning when networking came in, they saw the issue (our backup alerting system was sending emails all night long).

Instead of "Oh no, maybe we should have a process in place to verify patching X systems doesn't degrade Y systems", the various teams are dog-piling on alerting (my responsibility). VPs are now getting involved. They are saying things like "There should have been a monitoring system to monitor the alerting!!!". Which there is, the email back up alerting. Must be a dozens of messages in the team chat all pointing the finger that 'alerting should have worked', even though *those server clusters were all down*. My boss tried to chime in with common sense saying "If our infrastructure team can't guarantee 100% uptime on the clusters, then this will happen again. The issue happened once in the 5+ years we've been using this framework. We can spend time and money creating yet another monitoring system, which could fail too, or accept the reality that sometimes things break. We fix it and do what is reasonable so the issue doesn't happen again. In my opinion, paying for another solution isn't feasible in this situation."

Team chat is silent right now, but my spidey sense is tingling.

Mother-in-law was visiting this morning (love her, lovely woman) and being a good son-in-law, I set out/up the coffee maker before leaving for work (I knew she'll want coffee).

About an hour I get a text message from my wife.

W: "Mom is here and wants some coffee. How do I make coffee in that thing on the countertop?"
<It's a Keurig>
Me: "First, press the power button to get the water up to the brewing temperature."
W: "I know that, I'm not stupid. Where is the power button?"
Me: "The top row of buttons, the first button, it looks just like the power button on the remote control."
W: "Got it. Now what? Its not working"
Me: "You need to wait until it's done warming up. Takes about 30 seconds."
W: "Is it supposed to make that sound? Something is wrong."
Me: "No, its normal. Be patient."
W: "No, something is wrong. Its not supposed to be that loud."
Me: "Sounds like a jet engine taking off, yes, been using it for almost 10 years, this isn't new."
W: "Stop being mean. Never mind. It stopped. What now?"
Me: "Put the pod in the little basket, pull down the handle, and press the second button from the top."
W: "Not working"
Me: "Did you pull the handle all the way down, so it locks?"
W: "Still not working. Now what?"
Me: "Weird. Send me a picture, I can't see what you see."
W: "Never mind, its working now. This would have gone a lot faster if you told me what to do from the start."

My prayer today is thanking Jesus for patience. Amen.

In my EOY performance review/summary, I told I would only receive (along with everyone else) the standard cost-of-living increase of 3%. I'm OK with that, with my tenure/seniority, 3% is a good bump, but I had to make a comment.
Me: "With Biden's inflation between 7% and 10%, its actually a pay cut, right?"
Boss: "Yea, I know."
Me: "Our insurance went up around 5% and they cut some of the benefits, so that's a little more of a pay cut, right?"
Boss: "I know that too. With the economy and cuts to margins, there won't be any profit sharing this year. We have a hiring freeze for the foreseeable future."
Me: "Recruiters have been offering sweet work-from-home compensation packages, what's the likelihood that these young guys will move to greener pastures?"
Boss: "Hard to say. I think the ones that wanted to quit already have. Company already gave a generous industry level-up pay adjustment back in November. Those guys are all single and the 3% is icing on the cake. I don't think 3% will look very good next year."
Me: "Agreed. Looking forward to a wonderful year"
Boss: "Yea, sure.. smart ass."

Any ranters at VS Live360 Orlando? Trying to figure out the point of .Net Aspire. I don't get it.

Researching a new communication platform (Twilio, Vonage, etc), I started with Plivo. Created an account, they offer from free credits to try out the platform, so I set up a phone number and attempt to use their API, didn't quite work. I contact their support through their online portal (being very detailed about what I'm trying to do and the issue I'm having)
A day later they reply asking "Could you tell us how you are using Plivo and the issue you are having?"
That would be OK, but my question from the online portal was in the body of the email message. My first reply started with "You not reading the <bleep>ing message is my issue right now.", but I copied and pasted the same message. I even included a screenshot of the API I was having a problem with (so they could see what I see).
Next day I'm trying out a different area of their API and there is a banner "Incoming and Outgoing phone calls are disabled on this account. Contact Support blah blah blah"
I thought, OK, its a trial account, they probably want some additional validation before allowing anyone to make phone calls. I jump thru the hoops, next day I receive an email "Thanks for sharing the details with us. I have reached out to the Product Team to assist us with this and I'll share more details with you as soon as they revert."
Revert what? The block? Waited until next day, banner still there, so I replied again. Not another reply until the next day.
"Our internal team analyzed the account details and unfortunately, we would not be able to remove the restrictions from your account."
WTF!? Plivo, we are going to give you *money* and you can't answer my question! I'm not asking for free stuff, not asking for help finding the 'any key', your API is supposed to support XYZ feature and it's not working...OK. We're done.
I try to close the account (has too much of my personal info I don't want these clowns to have) and I get an error 'Unable to close the account'. WTF!

This is going to be fun. We are switching our phone system to use Zoom and the turn on date is sometime in October (couple of weeks away). I have a feature I'm working on (automated phone calls) that the salesman said was fully functional (jump through a hoop, stand on your head, turn around three times, type of functional). Tried the steps they gave me, got to #3 and there is no virtual agent API call I can find to hand off/transfer the call. Send our contact at Zoom some questions, responds "That is a feature we might put in a future product. Can't do that right now." WTF?!
Other developers are running into similar "How do we get there from here?" issues that features promised, either don't exist or don't work.

One feature in particular I'm receiving a 403 permission denied error.
K: "Feature X needs to be enabled."
Me: "It is."
<send a screenshot showing the feature enabled>
K: "Your account doesn't have permissions. Have the sysadmin elevate you authentication level."
Me: "I'm an admin"
<send a screenshot showing my admin status>
K: "I'll have to get back with you."

Its been 3 days and no update on my ticket. *sigh*

It's been a while since I've heard a consensus of a moronic idea from the corner offices. I was invited to a department planning meeting (just to listen, not necessarily engage or add value) and discussion went to the development of a mobile app.

Mgr1: "The CEO has the net present value of the mobile project as $20 million. Where did he get that number?"
VP: "No idea."
Mgr2: "How will it be any different than our web site that is already mobile compliant?"
VP: "It is to gain market share"
Mgr3: "Market share from who? A mobile app is not going to increase our customer base. At best, it will only move some of our existing customers to mobile. No way it would scale to those numbers."
VP: "The primary benefit is so customers can browse offline."
Mgr2: "Offline browsing isn't listed in the milestones."
Mgr1: "We're not going to push and keep gigs of data up-to-date on someone's phone just for random times they don't have internet access."
VP: "I guess that's right. We can push our pdf catalog. That's only a few hundred meg."
Mgr2: "Pushing the catalog? That's not on the listed milestones"
VP: "Its all assumed."
Mgr3: "Who owns this project? Web team is already maxed to capacity."
Mgr2: "Marketing team only has 3 developers, we can't take on anything as complex as a mobile app and support the existing processes."
Mgr1: "What about the network infrastructure and PCI compliance? We're talking about a system for the web site and another for mobile, right?"
Mgr2: "Who is going to manage all the versions in the app stores and future changes to the mobile platform?"
Mgr4: "Not us"
Mgr2: "Nope"
Mgr1: "OK, good. Its very likely this project will be dead on arrival at the next company strategic meeting."
VP: "Mobile the only project on the strategic meeting agenda. Sorry guys, it's happening. We're not going to leave $20 million sitting on the table.
<awkward silence>
VP: "Next item of business ..."

Last week a user couldn't find a document in sharepoint. Typed (what he thought) was the exact file name in the search -> no results.

I know how to get 'under the hood', so I looked where I thought the file was, found it, and it was exactly as he searched for it. What the hell? Wasn't a new file, it wasn't moved/renamed, no reason why it couldn't be found.
I 'touched' the file. Waited 5 minutes and searched again, found it. What the frack Microsoft!

A service had/has been logging hundreds of errors in the development environment and I reached out to the owning process mgr that the error was occurring and perhaps a good opportunity to log additional data to help troubleshoot the issue if the problem ever made its way to production. He responded saying the error was related to a new feature they weren't going to implement in the backing dev database (TL;DR), and they know it works in production (my spidey sense goes off).
They deployed the changes to production this morning and immediately starting throwing errors (same error I sent)
Mgr messaged me a little while ago "Did you make any changes to the documentation service? We're getting this error .."

50% sure someone misspelled something in a config, but only thing they are logging is 'Unable to parse document'. Nothing that indicates an issue with the service they're using.

Spent the last half hour helping my wife over text trying to "fix" FireFox. She said any site she tries to go to just "spins and spins". Chrome, Edge, all work fine. Tried the trusty 'ipconfig /flushdns'.

Me: "Open the command line, by selecting Start and start typing cmd. You'll see the Command Prompt application. Right click and run it as an administrator"
<15 seconds later>
Her: "Do I left click or right click to run as adminstrator?"
Me: "Left click. You'll get a pop message, just click yes"
<about 10 seconds later>
Her: "This thing popped up, what do I do?"
Me: "Click yes"
<more waiting>
Her: "Says something about making changes to my computer, what do I do?"
Me: "Click yes"
Her: "Is it going to make changes? Are you sure I should click yes?"
Me: "YES!!"
Her: "Don't yell at me. You're supposed to know how to do this, not me. What do I do now?"
Me: "Type ipconfig /flushdns"
Her: "OK, is this right.."
<sends a screenshot of 'Type ipconfig/flushdns'>
Me: "No, just ipconfig /flushdns"
Her: "OK, is this right.."
<sends a screenshot of 'ipconfig/flushdns'>
Me: "Yep, just put a space between ipconfig /flushdns and press enter"
Her: "Is this right.."
<sends a screenshot of ' ipconfig/flushdns'>
Me: "No, the space goes between ipconfig /flushdns, not before."
Her: "You're not making yourself clear. OK, now what?"
Me: "Press enter"
Her: "It didn't do anything."
Me: "Did you press enter?"
<more waiting>
Her: "OK, it's done. Now what?"
Me: "Restart FireFox"
Her: "Still not working. Just spins and spins."
<not 100% sure restarted FireFox>
Me: "I'll look at it when I get home."

Trying to use authenticate a JWT token from an Azure service, which apparently needs to use Azure AD Identity services (Microsoft Entra ID, Azure AD B2C, pick your poison). I sent a request to our Azure admin. Two days later, I follow up, "Sorry, I forgot...here you go..."
Sends me a (small) screenshot of the some of the properties+GUIDs I need, hoping I don't mess up, still missing a few values.
Me: "I need the instance url, domain, and client secret."
<hour later>
T: "Sorry, I don't understand what those are."
Me: "The login URL. I assume it's the default, but I can't see what you see. Any shot you can give me at least read permissions so I can see the various properties without having to bother you?"
T: "I don't see any URLs, I'll send you the config json, the values you need should be in there."
<10 minutes later, I get a json file, nothing I needed>
<find screenshots of what I'm looking for, send em to T>
Me: "The Endpoints, what URLs do you see when you click Endpoints?"
<20 minutes later, sends me the list of endpoints, exactly what I'm looking for, but still not authenticating the JWT>
Me: "Still not working. Not getting an error, just that the authentication is failing. Don't know if it's the JWT, am I missing a slash, or what. Any way I can get at least read permissions so I don't have to keep bugging you to see certain values?"
T: "What do you need, exactly?"
Me: "I don't know. I don't know if I'm using the right secret key, I can't verify if I'm using the right client id. I feel like I'm guessing trying to make this work."
T: "What exactly are you trying to get working?"
<explain, again, what I'm trying to do>
T: "That's probably not going to work. We don't allow AD authentication from the outside world."
Me: "Yes we do. Microsoft Teams, Outlook, the remote access services. I can log into those services from home using my AD credentials."
T: "Oh yea, I guess we do. I meant what you are trying to do. Azure doesn't allow outside services to authenticate using a JWT. Sorry."

FRACK FRACK FRACK!!

Whew! Putting the flamethrower away.

Thanks devrant for letting me rant.

My favorite famous dev/tech person + why?

Scott Hanselman.

He always takes the human approach to technology. Its easy to forget we're supposed to write software for people.

My wife is a pretty decent artist and we were talking about AI and what affect it can have on folks in the graphic artists industry.
I fire up Microsoft's Designer, enter a prompt and this is what it generated.
She said "Oh good. We're gonna be OK."

Worst coding procrastination story?

Not necessarily coding, but anything that has to do with writing support reports for an application/feature. Good news is we have a dedicated dept for maintaining reports now, but there was a time developers were required to write and maintain reports (Crystal Reports). Starts out as data in grid, but de-evolves into ..
U: "This value here...can you make that red if its a Thursday before a promotion release on Friday and I forget to update the promotional percent?"
<month later>
U: "Why is this value red?"
<explain why it's red>
U: "That is so stupid, I wouldn't ask for such as feature. I never forget."
<month later>
U: "OMG! I FORGOT TO UPDATE THE PERCENT AND WE LOST OVER $100,000!! THE REPORT WAS SUPPOSED TO FLAG THOSE VALUES IN RED!!! I HAVE THE REQUIREMENT DOCUMENT!! ITS ALL YOUR FAULT!!!"

Not to mention the hours...HOURS worth of meetings filled with "Can you move the value a little to the left, a little more..NO! Too far! Now, make it bold...bolder..uggh...I said bolder, I thought you guys knew a lot about computers."

I eventually ignored the report feature with "I'll work on it later". 'Later' never showed up. Users eventually exported the data to Excel to write their own reports and now exporting data to Excel is a standard feature of our apps.

I'll monitor our helpdesk ticket system from time-to-time and HR will send their employee termination request so the accounts are deactivated. I notice an odd name I hadn't seen in a long while (names have been changed)

<thought bubble> "Ketsup? Hmmm...wonder if they're related to ol' Brad Ketsup?"

Brad was a bully who would shove me in the bathroom when I would pee so I would tip over and hit the urinal. He was part of pack of older bullies who enjoyed torturing people in the stalls by throwing wet paper towels over the wall or one time in my case, busted the door open (Brad: "Look everybody! PaperTrail is pooping! Look at his little pee-pee...ha ha ha..") Incidentally, the school didn't fix the door, they removed all the doors so the problem wouldn't happen again, but I digress.

I look at the individual's pic, and it was like going back in time. There he was, the near perfect round face, pinned back ears...not Brad, but I'd bet my paycheck at Vegas it was his son. All the vent up frustrations started to bubble up...then...sadness.

Brad moved away in high school and unless the good Lord moved mountains in Brad's life, this poor kid likely lived the same abusive life as Brad. Brad's dad was a drunk and known to be abusive. Statistically speaking, no reason to believe the the apple wouldn't fall far from the tree.

Makes me wonder what happened to all those guys from back then. I know two of em' ended up in prison, but I wonder what I would say if I came across any of them in the wild?

I'm sure most of you had perfect lives growing up and no feelings of mass carnage when you think of the bullies in your early life.

Most awkward video meeting?

Can a conference call count? This happened several years ago.

Diving into international markets that could potentially make us millions of $$ (no pressure), while the phone was ringing the CEO's number (in Norway), my manager leans over and whispers
DevMgr: "This project will be managed using *proper* software development methodologies, none of this agile shit you want to use."
<CEO picks up>

I had already been in talks with their dev team to get a feel for their tech stack and we had discussed project milestones, potential release cycles (laying the ground work for using agile methodologies) before getting upper mgmt involved.

The partner dev team was listening and kept throwing out agile buzzwords and I could tell my manager was getting pissed. He would blurt out "Those specifications will need to be fully documented before PaperTrail writes one line of code!". No one said anything, but I could tell the other mgrs/VPs in the room were uncomfortable with the hostility towards discussing features.

Playing around with Bard:
Me:Who called me from ...?
Bard: <blah blah blah> Would you like me to run a reverse phone lookup on that number for you?
Me: Yes
Bard: I'm just a language model, so I can't help you with that.
Me: Then why did you ask?
Bard: "I understand that you don't need me to run a reverse phone lookup, and that's perfectly fine. I just wanted to offer the service in case you were interested."

I tweaked the question and Bard responded with a Python script and a phone number regular expression.

Our jobs are safe for now.

#1 life lesson I learned from coding?

Maybe not coding specifically, but I learned the difference between problem solving and solution finding.
Its helped me in a lot of areas of my life. Made friends and made enemies.

Best code performance incr. I made?

Many, many years ago our scaling strategy was to throw hardware at performance problems. Hardware consisted of dedicated web server and backing SQL server box, so each site instance had two servers (and data replication processes in place)

Two servers turned into 4, 4 to 8, 8 to around 16 (don't remember exactly what we ended up with). With Window's server and SQL Server licenses getting into the hundreds of thousands of dollars, the 'powers-that-be' were becoming very concerned with our IT budget. With our IT-VP and other web mgrs being hardware-centric, they simply shrugged and told the company that's just the way it is.

Taking it upon myself, started looking into utilizing web services, caching data (Microsoft's Velocity at the time), and a service that returned product data, the bottleneck for most of the performance issues. Description, price, simple stuff. Testing the scaling with our dev environment, single web server and single backing sql server, the service was able to handle 10x the traffic with much better performance.

Since the majority of the IT mgmt were hardware centric, they blew off the results saying my tests were contrived and my solution wouldn't work in 'the real world'. Not 100% wrong, I had no idea what would happen when real traffic would hit the site.

With our other hardware guys concerned the web hardware budget was tearing into everything else, they helped convince the 'powers-that-be' to give my idea a shot.

Fast forward a couple of months (lots of web code changes), early one morning we started slowly turning on the new framework (3 load balanced web service servers, 3 web servers, one sql server). 5 minutes...no issues, 10 minutes...no issues,an hour...everything is looking great. Then (A is a network admin)...
A: "Umm...guys...hardly any of the other web servers are being hit. The new servers are handling almost 100% of the traffic."
VP: "That can't be right. Something must be wrong with the load balancers. Rollback!"
A:"No, everything is fine. Load balancer is working and the performance spikes are coming from the old servers, not the new ones. Wow!, this is awesome!"
<Web manager 'Stacey'>
Stacey: "We probably still need to rollback. We'll need to do a full analysis to why the performance improved and apply it the current hardware setup."
A: "Page load times are now under 100 milliseconds from almost 3 seconds. Lets not rollback and see what happens."
Stacey:"I don't know, customers aren't used to such fast load times. They'll think something is wrong and go to a competitor. Rollback."
VP: "Agreed. We don't why this so fast. We'll need to replicate what is going on to the current architecture. Good try guys."
<later that day>
VP: "We've received hundreds of emails complementing us on the web site performance this morning and upset that the site suddenly slowed down again. CEO got wind of these emails and instructed us to move forward with the new framework."

After full implementation, we were able to scale back to only a few web servers and a single sql server, saving an initial $300,000 and a potential future savings of over $500,000. Budget analysis considering other factors, over the next 7 years, this would save the company over a million dollars.

At the semi-annual company wide meeting, our VP made a speech.

VP: "I'd like to thank everyone for this hard fought journey to get our web site up to industry standards for the benefit of our customers and stakeholders. Most of all, I'd like to thank Stacey for all her effort in designing and implementation of the scaling solution. Great job Stacy!"
<hands her a blank white envelope, hmmm...wonder what was in it?>

A few devs who sat in front of me turn around, network guys to the right, all look at me with puzzled looks with one mouth-ing "WTF?"

Most awkward work event/parts story?

There was a girl who worked in customer service, very goth. Un-kept hair, baggy cloths, dark lipstick, etc..etc. At a company holiday party there were several+many people (mostly dudes) asking "Who is that! ... She's HOT!!" etc (you could hear it from various tables), and someone said "That's Stefanie.", then the "Noooo...OMG..."
Apparently she cleaned up nicely (dressed like she was going to a movie premier, very classy). She and a female friend (also attractive, dressed like a million bucks) were sitting close to each together and you could hear more (inappropriate) comments "OMG, are they together!?...that's fucking hot!....".
Mind you, this wasn't a very big venue (and before all of today's woke-ness), I could hear it a few tables away (again, all dudes, customer service and warehouse worker folks), I *know* they could hear it from their table.
It was so bad Stefanie's CS manager talked about in the break room the next day. She wasn't at the holiday party, but the rumors were going wild that day.
<she's in her 60's and I wouldn't want to be on her bad side>
D: "I can't believe they made such a scene. I would have smacked those young men in the face! Stefanie has a boyfriend and Laura is married. They have been best friends since kindergarten, its disgusting what went on. And another thing..."

It was talked about for many years afterward.

I need some time off. Just had this convo with a dev-manager about an 'issue' with our system change mgmt calendar (Blazor) app.

K: "In the system drop-down, it's not filtering when I type."
Me: "Let me check <I attempt to reproduce>, yep, not working. Do you get the same error? Looks like duplicate data from the database is causing a problem."
<this is over MS Teams, about 5 minutes go by with no response, then>
K: "No error, its not working."
<I find the bad data, delete it, TADA, the filtering is working again>
Me: "The filtering is working again, at least for me. You sure you didn't see an error?"
<wait 5 minutes again>
K: "No, no error."
Me: "You didn't see a little red banner at the bottom and in all caps..ERROR"
<send him a screen-shot of the error I still had in another tab>
K: "Yes, I saw that one, but no other errors. Filtering is working again. Thanks"

My dad got a new phone over the weekend and asked me to help him set it up (TL;DR his IPhone broke, he likely cussed out someone on the phone and now he's on android).

Setting up his bank app, I asked for his password (I somehow knew asking a 80+ year old man password questions wouldn't end well)

<pulls a card out of his wallet>
Dad: "Here you go."
Me: "This is your business card?"
Dad: "Yep. Password is at the bottom. That way I never forget it."
Me: "Jeez dad, you shouldn't have your bank's password on a business card. You don't give these out to people, do you?"
Dad: "Sometimes. Hell, they won't know what that is. Its just a bunch of nonsense."

Luckily the password didn't work. He had to reset it when his IPhone messed up and didn't remember what he changed the password to.

Fav. thing I've worked on recently?

Blazor and creating our framework around authentication/authorization.

We have an internal nuget package that wraps up the IConfiguration+ConfigurationBuilder for various .net core console/service apps (TL;DR, because people got creative), and it has a dictionary property for the common sections we use. AppSettings (for backward compatibility), ConnectionStrings, and ServiceEndpoints. If the need arises, I can add methods to return any type of object (no one has requested yet, we try to keep configs dead simple)

ex. var myDatabaseConnectionString = ConfigurationManager.ConnectionStrings["MyDatabase"];

Code review for someone who updated a .net framework app to .net core and they wrote their own IConfiguration wrapper for accessing the appsettings.json file, so I pointed out that we already had a library for that.
In the reply, he said he couldn't use our library because it had an 'AppSettings' property and since his appsettings.json file didn't have that section, he didn't want to cause a runtime exception.

OK, WTF...I even sent him a link to the documentation (includes explaining the backward compatibility part)...why the frack would you think because a property exists and you don't use it, that would cause some kind of runtime exception?
We have dozens of .net framework apps migrated to .net core with zero code changes and no one ever brought this up as a concern (because, why would they?)

Deep breath...ahhh...I respond that not having an AppSettings section in the appsettings.json file won't cause an exception, if you don't have one, don't need it, you don't have to use it.

He went ahead merged+committed his code anyway with his own IConfiguration+ConfigurationBuilder plumbing.

Code addiction is real kids...it's real.

Goal for my dev career future?

I'll soon be 53, my career goal is to make it to retirement without fired for some random biz-talk excuse for being too old.

Inappropriate experience at work? Here is another one:

After 10 years of service the company gives the employee an anniversary party, complete with cake, drinks, etc.

Preparing for a party, HR set the cake in the break-room and left to get the other supplies, in the mean time the IS department manager 'John' walks in, sees the cake and decides to take a slice.
Not a small corner piece you may not notice by smearing the frosting around, but a big piece from the * middle of the cake *.

'Mary' walks in and catches him.

M: "JOHN! The cake is for Eddie's party! Everyone will be here any minute!"
John: "Oh shit!..sorry, let me put it back..."
M: "NO!, you've already eaten some...the cake is ruined!"
<he had icing all over his hands, so he used the cake knife to cut, but used his hands to dig out the slice, so the cake looked pretty tore up>
J:"How was I supposed to know? All I saw was free cake!"
M: "You are on the invite list for Eddie's party! You have 'Happy Anniversary Eddie' on your plate!"
J: "Party isn't until 2:00...<looks at the breakroom clock> oh shit...it's 2"

About that time, several VPs walk in, notice Mary is upset and after finding out, our IS-VP said "John, I'm not happy about this. I want you in my office after the party. You can leave ...now!"

Our IS-VP is almost always emotionless (mostly just happy and in a good mood), it was the first time anyone had seen him this physically angry in years. We don't know how John kept his job.

Inappropriate experience at work? Here is another one:

The IS department manager 'John' loved shelled peanuts, but hated cleaning them up. By the end of the day his desk and surrounding area were covered in peanut shells (he never bothered trying to put the shells in the trash can). He didn't seem to care because the maintenance crew would clean up the office every night and he would come in to a clean area every day.

That was until the company owner's wife was making the rounds one day and saw his mess. The shells hit the fan. The 'beat down' occurred at EOD, so most didn't witness it, but she lit him up. Almost screaming that he's a grown man and the maintenance crew have enough to do without cleaning up after him...etc..etc.
John never ate peanuts at his desk again.

Inappropriate experience at work? Here is another one:

The IS department manager 'John' bought a drone (when they first started getting popular, paid over $400 for it), flew it around the office, which was kinda fun, then he took it outside and started peeking in (and recording video) various VPs offices.

Needless to say, that behavior wasn't popular because several/most have their back to the window and never saw the drone and the drone was close enough to see/record their monitors (which John did). No one was doing anything wrong (no porn, no secret company plans, etc), but they were rightfully upset.

Later that day he decided to find out how high he could go and because of the technology at the time, it lost signal or battery power, fell from the sky, and before he could gain control, it crashed (styrofoam wings shattered). Can't say I felt sorry for him.

Inappropriate experience at work? Here is another one:

The IS department manager 'John' bought a blowgun and was shooting at a box down the cubical farm hallway. Only a little annoying to hear him puff on the tube, but then someone walked out their cube and almost got hit.
Dev: "Dammit John! What the hell are you doing?!"
John: "Maybe you should pay the hell attention to where you're going. You heard what I was doing. Don't be a baby, those darts wouldn't have hurt you anyway."

I've attached a pic of what the darts looked like.