The tools we use to get development done
Updated: Jul 1, 2020
Back in 2006, oe:gen began as a web design and development company. Throughout the years, we’ve been keeping up with the change of demand, going from standard websites to complex Salesforce Communities (and jumping over a few obstacles along the way). On this weird and wonderful journey, we’ve consistently strengthened our skills to nail the user experience of each of our projects, as well as trialled an insane amount of tools to see which are the best fit.
All this hard work has lead to what we are today – a Silver Salesforce partner full of over 30 experts in building beautiful, fully branded Salesforce Communities that our customers (and their customers) love to use.
In case you were curious about how we create these customer experiences, here are some of those tried and tested tools we continue to use.
Primary tool: JetBrains WebStorm with Illuminated Cloud 2
We fell in love with WebStorm and Illuminated Cloud 2 as soon as we used them. We were on the lookout for a solid, performant, extensible development environment for Salesforce, and WebStorm with Illuminated Cloud 2 met that brief superbly. Some of our favourite features include the great code completion, refactoring, customizable linting, git integration and general layout/usability of the app.
Honourable mention: VSCode with the Salesforce Extension Pack (and loads of other extensions)
We have developers here at oe:gen who like to be “individual” and therefore opt to use VSCode with the Salesforce Extension Pack, plus Jira, Spotify and many other extensions that slow their machines down. Bless them. This is fine, we’re not dictators here, so long as they don’t come running to us when they can’t deploy a Lightning Component.
Primary tool: ClickDeploy
We’ve read about and trialled several metadata deployment tools in our time, but ClickDeploy meets our current needs very well. It’s a huge step-up over traditional changesets, while still being very user-friendly, allowing us to deploy code and config quickly without spending hours RTFM-ing (Google it). We’re on the cusp of upgrading to the top tier, Enterprise, for all the CI / CD gubbins that brings.
Primary tool: Git with BitBucket
Need I really say anything about Git? We moved over to BitBucket from GitHub shortly after a certain software behemoth got their claws on it and haven’t looked back. We love the native integration with Jira and the configurable branch permissions.
Primary tool: Jira Cloud
oe:gen have dabbled in simpler tools like Trello in the past, but none really cut the mustard quite as Jira does. It took us many, many months to accept Jira for what it is and to learn how to customize it to meet our needs, but now we’re (mostly) there.
Primary tool: Microsoft Teams
We use Teams. We’d probably prefer to use Slack. Sometimes you don’t get what you want in life, okay? Teams has come a long way since its early days where the application would hang regularly and notifications were non-existent. It’s not perfect, but neither was Game of Thrones. You still watched all of it, didn’t you?
Primary tool: Salesforce Communities with CMS Content
Being experts in Salesforce Communities, we thought it’d make sense if we created an Employee Community where our team could go to get information about the company, our tools and processes. We’re mid-development, but are seeing a lot that we like about Salesforce CMS.
Our value of continuous improvement means we’re constantly keeping an eye out for better ways to do development here at oe:gen. But these guys have become favourites in our toolkit. If you want to find out more about how we build our “best in class by far” Salesforce Communities, chat to us today!