SendGrid is happy to announce its availability in Google Cloud Launcher, a marketplace that enables Google Cloud Platform users to explore, launch, and manage powerful solutions and services. Google Cloud Platform offers computing, storage, and application services for your web, mobile, and backend solutions. Google Cloud Platform and SendGrid have collaborated for a number of years, but this update provides customers with easier access to leverage SendGrid. Why Join Google Cloud Launcher Email continues to be one of the most effective ways for organizations to communicate with their users or customers. From an ROI perspective, each $1 invested in email returns an average of $38 in revenue. We’re happy to provide an easy email integration for Google Cloud Platform users.
Stamplay + SendGrid Stamplay is basically lego blocks for developers. Essentially, it allows developers to connect disparate API endpoints together to build a functioning backend, all through an easy-to-use and intuitive interface. I first came across the tool during my office hours at 500 Startups and I immediately saw a lot of value in it. In addition to connecting endpoints seamlessly, it also allows a developer to trigger workflows based on certain criteria. For example, you can send out automated Slack invites over email. Stamplay connects with several services (including SendGrid) to add a layer of abstraction, allowing developers, and even non-developers, to quickly put together a backend for their projects. Most recently, there were two major updates to the service
In mid-August, we hosted our second-annual Internal Hackathon and once again, it was a total success! Over 100 employees, ~30 hacks, and 24 hours of creative excellence! The whole idea of hackathons is to bring people together in a creative environment and give them the freedom to build something amazing. All too often now we see companies hosting internal hackathons where the event is either mandatory attendance, or a chance for the company to exploit their employees by having them work on only the business’s software, and without any kind of remuneration—in essence just a long, pressured sprint. This isn’t a good way to go, and certainly not something we agree with. Whilst we had “bounties” on SendGrid-related projects, the
I’ve now been a Developer Evangelist (or as I call it, a Devangelist) for 29 months. I’ve admittedly been close to burn out twice, but bounced back from both close-to-burnouts with the knowledge to keep myself from doing it again. I’ve been all over the world, spoken at some of the best conferences, attended some of the best hackathons, learned an unbelievable amount, mentored some of the finest minds I’ve ever come across, and enjoyed every minute of it. To document my ongoing experience as a Devangelist, I thought I’d throw together this pictorial blog to tell my story. So, here are my 10 reasons in pictures, why I love being a Developer Evangelist. This was originally an Ignite talk I
It might be weird to imagine, but the first things that come to mind when I think of tech debt and information debt is Star Trek and cats. Specifically, I think of tribbles and wrangling kittens. You might think this is a total stretch, but let me explain… Tribbles are basically little fluff balls that can multiply seemingly exponentially in a short amount of time if exposed to food. They’ll get everywhere, but are easy to capture once you get them away from food. Kittens, on the other hand are wonderful little animals that are so cute and needy, they exert control over you… If you were to combine these two creatures, you’d have a Tribble
Before you open source a library, there are a few things that you need to do to ensure you’re following all the rules and that the code is ready for the community. Here’s the 11 step pre-flight checklist that we put together internally at SendGrid: Check the code to make sure that no proprietary information like usernames and passwords are present, and that configuration uses environment variables where necessary. Your code isn’t portable if there are hardcoded database names and credentials. Environment variables are convenient and are a secure default. Make sure that dependencies are encapsulated and explicitly declared. People need to know what they’re getting and if it will work with their existing dependencies. Confirm that there is no