i wrote a lot about this on my blog but the gist of it is that i'm an engineer whose main stakeholder is the community of glitch.com users. we call glitch the friendly community where you can build the app of your dreams and i'm trying to keep it that way by building tools for users to remix, doing outreach and also listening to what the users needs are so we build the best product for everyone!
ooof I've done a lot! before i came to fog creek i was a consultant building javascript and php apps for all sorts of clients, and before that i was a senior front-end engineer at the NBA working mostly on stats.nba.com. before i entered the industry with that gig I was a department administrator in the computer science department at a state university. i advised students, taught java and web development and intro to technology, recruited, and did curriculum design.
Thanks, I wasn't sure if that was a common title or something you rolled yourself. It makes a lot of sense as a key responsibility at a place like Glitch.
i rolled it myself for my role, but there are others who have already been going by that title i've learned. there are also some who have changed their title to community engineer after they read my blog post. i'm sure it's not helping the confusion around what dev rel/evangelism/experience/advocacy is but it works for me :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
i wrote a lot about this on my blog but the gist of it is that i'm an engineer whose main stakeholder is the community of glitch.com users. we call glitch the friendly community where you can build the app of your dreams and i'm trying to keep it that way by building tools for users to remix, doing outreach and also listening to what the users needs are so we build the best product for everyone!
ooof I've done a lot! before i came to fog creek i was a consultant building javascript and php apps for all sorts of clients, and before that i was a senior front-end engineer at the NBA working mostly on stats.nba.com. before i entered the industry with that gig I was a department administrator in the computer science department at a state university. i advised students, taught java and web development and intro to technology, recruited, and did curriculum design.
Thanks, I wasn't sure if that was a common title or something you rolled yourself. It makes a lot of sense as a key responsibility at a place like Glitch.
i rolled it myself for my role, but there are others who have already been going by that title i've learned. there are also some who have changed their title to community engineer after they read my blog post. i'm sure it's not helping the confusion around what dev rel/evangelism/experience/advocacy is but it works for me :)