The first time we do anything, we're terrified. Asking out that first date, submitting that first patch, reviewing someone else's code for the first time. Surprisingly, how we feel about it (e.g. "OH MY GOD I DON'T KNOW WHAT I'M DOING") has very little to do with how well
I've always been fascinated by the idea of getting up in front of hundreds of strangers and being expected to present your ideas to them. It's simultaneously enticing and terrifying, and that's probably what draws me to it. In October of this year (2016), I attended the DevIntersection [https://devintersection.
I'm continuing my series of deep dives into ASP.NET Core [https://www.exceptionnotfound.net/tag/asp.net-core/], on my never-ending quest to keep my coding career from becoming obsolete [https://www.exceptionnotfound.net/learn-or-die-warding-off-my-coding-careers-eventual-obsolescence/] . In this part of the series, let's discuss a new feature in ASP.NET Core
I had a meeting with a customer (let's call her Kate) last week, and she wanted some changes to a web-based messaging application that my group owns and manages. That meeting didn't exactly go as planned. Blame Tennis Here's how the conversation between myself and Kate went: > Matthew: OK, so
I've been writing this blog for about a year and a half now, and I firmly believe that every software professional should write a blog. It's an invaluable tool for connecting with other professionals, for getting your ideas out there, for making bad jokes making good jokes. I've told this