Welcome Micah Silverman
My name is Micah Silverman and I just joined the Developer Advocacy team at Okta. TL;DR - There are some easter eggs in this post. If you want to know what they’re all about - jump to the bottom.
Funny thing is, I’ve been working for Okta for 2 years now, just on different teams.
It was in the Sales Engineering and Education Services teams that I learned all the ins and outs of the Okta Developer API, including our support for standards like SAML, OpenID Connect and OAuth 2.0. And, I went on to teach our developer courses. Check out our course catalog when you’re ready to dig deep into all that Okta has to offer.
I’ve also been a casual contributor to the Developer Blog as a guest poster. I am very excited now to be an official member of the team. I’ll be primarily leading workshops around the country (and the world) to talk about OAuth and OpenID Connect. I will also be contributing more code and posts.
About Me
I developed an interest in computers right at the beginning of the personal computer revolution when I was in 6th grade. I first played with CBM PETs in school. My first home computer was a Commodore Vic-20. Then a Commodore 64 and even the rare SX-64 (LOAD "*",8,1
– anyone?).
After learning of what I was doing with my 300 baud modem and phreaking tools, my parents sought a more wholesome outlet for my interests (one that would keep me out of jail, preferably). My father, a dentist, purchased an Osbourne 1 (CP/M for the win!) and had me help him automate his office.
Since then, my love affair with technology has continued to develop and evolve.
I’ve had a wide-ranging career working at the Syfy Channel for its first online presence, large banks and insurance companies including JP Morgan Chase and Metlife, and startups.
The primary themes have been my love of APIs, information security and teaching others all about them.
I’m a maker at heart, whether it’s refurbishing a Dark Tower game or building out a MAME arcade cabinet.
The Love of All Things API
I love connecting systems and functionality via APIs. Especially, things that were not necessarily intended to ever go together.
I wrote a blog post on efficiently working with the Twilio and Slack APIs to accomplish the same thing: showing a random Magic the Gathering game card.
Maybe not very practical, but it demonstrated some key software development patterns (SOLID) using very different APIs.
Gamification
I also love gamifying everything! It’s one of the reasons an early blog post of mine include playing the text based adventure Zork as a way to learn some of how OAuth 2.0 works.
I’ll even make impractical devices or API mashups just to better understand concepts and standards and make it fun along the way.
In fact, this post is an example of that (and the sort of thing you can expect from me).
You see, there are easter eggs embedded right in this post! Here’s the game:
- Text any message to 702-766-4224 (only US and Canada)
- As a bonus, format your message like:
-<icon id> <msg>
where icon ids can be found at: https://developer.lametric.com/icons
- As a bonus, format your message like:
- You’ll get a response referencing an easter egg in this post
- Text the proper reply to the same number, and your message will be sent to my LaMetric Digital message board.
- You can tune into this twitch stream to see your message display as well as that of other people
My dear friends in Education Services gave me the LaMetric as a parting gift. I wanted to discover how it worked, so I made a mashup of the Twilio and LaMetric APIs.
My focus on the DevRel team at Okta will be OAuth and OIDC and you can count on me to bring the fun with the learning.
Happy Hunting!
Spring Boot + Twilio + LaMetric FTW
The app that drives this ridiculous mashup is written in Spring Boot. It uses the Apache Fluent HTTP library to interact with the LaMetric API. It also uses the Twilio API to handle the interaction via SMS.
The source code for this app can be found on GitHub.
Okta Developer Blog Comment Policy
We welcome relevant and respectful comments. Off-topic comments may be removed.