Bringing technical clarity to the unknown

About The Site

💬 EN

Input” often leads my StrengthsFinder test results.

CliftonStrengths warns people like me, “your input needs useful and regular outputs,” lest I unexpectedly overflow at inopportune moments and info-dump about neural networks at Christmas parties.

I’m a technology renaissance woman, and this blog is my safety overflow.

To borrow a phrase from Al Sweigart’s excellently titled book, I “automate the boring stuff.”

It’s an exhilarating feeling, and I love to share what I know so that others can enjoy the experience, too.

  • I kicked off the blog teaching non-programmers and non-data-analysts to edit spreadsheets with Python, so that they could complete their work faster and enjoy more rest.
  • My opportunities to do serious web application and database integration development accompanied my journey from Salesforce administrator to Salesforce developer to Oracle PL/SQL developer, so there’s a lot of Salesforce and SQL content in the early posts.
  • Then I got to lift-and-shift a major enterprise system (one in which I was doing database programming) from one cloud infrastructure provider to another, which gave me the opportunity to journey into “DevOps” work and become a definitive voice as I consult on CI/CD pipelines, infrastructure as code, software package libraries and registries, test automation, security, identity and access control, and all the other things that come up in enterprise operations and software development lifecycles – particularly around client-server applications, but often around endpoints, since staff productivity, identity, and security often bridge those two domains together.

Credits

Despite accelerating them for a living these days, I am still very much not a front-end web developer.

I had no idea how to put a top nav on a page (it only took … 10 hours?)

I knew what blogs I liked the font size and whitespace proportions from … I had no idea how to make them happen from scratch.

  • I’ll drive as much traffic there as possible, but I can never fully express my eternal gratitude to Real Python for showing me what a code blog done right looks like. (Ahem … imitation is … the sincerest form of flattery? Sorry about ripping off, like … all your text sizing and whitespace and border-rounded-corner-sizes. I literally don’t know how to front-end dev.)
  • Much as I’d love to have eye-catching pictures like Real Python and Women Code Heroes, this site is probably destined to be unadorned … thanks to Practical Business Python for being the role model that consoles me, reassuring me that quality writing wins the day.
  • Thanks, also, to davidensinger.github.io, michaeltroger.github.io, walshbr.github.io, mjclemente.github.io, and Jekyll Architect for your open GitHub repos that let me figure out how to stitch together a Jekyll site. I couldn’t have done this without you.

Thanks to my friends for naming my blog. (Always have friends who are cleverer than you.)

Most of all, thanks to everyone who’s come before me, teaching me tech, writing, speaking, and teaching, and who walks alongside me, continuing to do so. I most certainly can’t do this without you.