Dave Nugent and I sat down together and Dave asked me the following questions about Developer Relations:
How do you prove the value of DevRel inside a large company?
How valuable is consistent messaging for DevRel?
How does leading DevRel differ between a startup and enterprise?
How does your team interface inside IBM?
How has your mission changed since you started at IBM?
Who in DevRel would you like to call out?
Q: How do you prove the value of DevRel inside a large company?
Probably one of the best ways and my favorite is to explain that developers today have a lot of influence. In other words, developers make decisions what software to use and buy. Many years ago software was purchased by executives and pushed down to developers (top-down approach). In most companies today it’s the complete opposite. Developers try software and if they like it they go to their managers/executives (who has the budget) and ask them to buy the software. Instead of top-down it’s now bottom-up approach. In some companies developers not only influence what software to buy but they also have the buying power.
This 12-minute video shows how I built a no-code application that sends an email and a text message when a new user registers. I used the following no-code tools: Airtable, Parabola and Twilio. The video is based on this blog post.
I live in Contra Costa County in the San Francisco Bay Area. The county has setup a web site with Covid-19 information for its residents. The main page shows key Covid-19 data updated daily. I have been visiting this page almost daily. This is how it looks for Friday, June 19, 2020:
I wanted to build an application that would email me this data every day. To continue my no-code journey I built a no-code application that sends me a daily email with the latest data. I didn’t need to write a single line of code!
These are the tools I used to build the application:
Simplescraper – to scrap data from the county web site and turn it into an API
Parabola – build a flow to invoke the API and send the email
This is how the application flow looks in Parabola:
In this blog post I will give you an overview of how I built a no-code application that sends an email and a text message when a new users registers. This is part of me taking an application built with code and building it with no-code tools.
I like breaking a topic into series as it allows to focus on a particular technology in more detail. You also don’t need to think about running out of time when you try to cover everything at once. Once you complete the series you can upload the videos to YouTube and publish a blog post with links and a short description of what developers will learn. You can also collect all the questions and answer them in a separate blog post. That’s part of content creates content approach.
Google Sheets is a well-known service and online spreadsheet. Google Sheets can be more than just a spreadsheet, it can be used as a back-end or a database for applications. For example, Glide uses Google Sheets as a database for its mobile applications. Glide allows to build a mobile application without any code connected to Google Sheets. It’s incredible how fast you can build a real app, .
I was building an app in Glide that displays the latest news using News API. I connected the app to a Google Sheets spreadsheet where I entered a number of news stories manually. The app looks like this:
This is how the Google Sheets spreadsheets looks:
If I need to update any news I can manually edit the Google Sheets spreadsheets and the Glide app will be updated.