How Salesforce Leverages Heroku
Code[ish]
Robbie Birbeck, VP of Digital Enterprise Technology at Salesforce, joins Julián Duque to talk about how Salesforce leverages Heroku. Filmed at the Palace Hotel in downtown San Francisco, the big star of this episode is Agentforce, which helps Salesforce employees with IT and HR questions, among others.
info_outline
Building Agentic Apps with RubyLLM
Code[ish]
Vestmark manages more than 1.7 trillion in assets, and its CTO, Freedom Dumlao, joins Julián Duque to discuss how AI is helping its advisors in their day-to-day work. Filmed at the Palace Hotel in downtown San Francisco, the pair discuss the role of AI in development and why all its new products are being built using Ruby.
info_outline
Engineering Excellence and AI Productivity
Code[ish]
In our second video special from the Palace Hotel, Julián Duque is joined by Shiva Nimmagadda, Vice President of Excellence, True AI and Analytics at Salesforce. Together, the pair discuss the various ways his team is using AI to improve developer efficiency, productivity, and output.
info_outline
AI Workflows for Support Ticket Integration
Code[ish]
Filmed at the Palace Hotel in downtown San Francisco, this week’s episode of Code[ish] is the first in a short series of video specials! To kick things off, Julián Duque is joined by Keegan Bakker, CEO of audience engagement platform Audata, to explore how Heroku helped the app grow from a hobby idea to a powerful tool for major organizations across the globe.
info_outline
AI Agents and Open Source
Code[ish]
This week on Code[ish], host Julián Duque connects with Rizel Scarlett from Block, Inc., to discuss how agentic AI is changing the FinTech landscape. Block, Inc. is the parent company behind popular services like Square, Cash App, and many more.
info_outline
Getting to the Heart of Twelve-Factor Apps
Code[ish]
On this week’s episode of Code[ish], Vish Abrams joins Jon Dodson to talk about the role of AI, the ways Twelve-Factor aids developers, and how science fiction shaped a little of their own history.
info_outline
Introducing Heroku Vibes
Code[ish]
This week’s episode is an exciting one because we’re talking about our brand-new release, Heroku Vibes! Mauricio Gomes joins Jon Dodson to go over what Heroku Vibes is, what it’s capable of, and how it could be a game-changer for developers and non-developers alike. Join the pilot by visiting
info_outline
Talking Traces and OpenTelemetry
Code[ish]
Jon Dodson has an 11-year Heroku veteran with him on the podcast this week, Principal Member of Technical Staff Alex Arnell. Together they talk through the native integration of OpenTelemetry in Heroku Fir, the benefits of traces over traditional logs, how they assist debugging, and what’s next for observability in modern development.
info_outline
Heroku in the Wild: Vanshiv on Using the Right Tools
Code[ish]
You won’t find too many developers with more experience in the Salesforce ecosystem than our guest this week! Not only is Gaurav Kheterpal a Salesforce MVP and Trailblazer, he also still uses his original Salesforce org from 2007. He joined Julián Duque to discuss how Vanshiv Technologies delivers client work with Heroku, the importance of embracing AI, and why it’s vital for developers to keep an open mind in choosing the right tool for the job.
info_outline
What’s Possible with Heroku AppLink
Code[ish]
This week we’re taking a deeply technical dive into our newest feature: Heroku AppLink! Jon Dodson is joined by Chris Wall, Salesforce Architect and creator of AppLink, to explore what AppLink offers developers and how it brings Heroku and Salesforce closer together.
info_outlineIn this episode of Codeish, Greg Nokes, distinguished technical architect with Salesforce Heroku, talks with Innocent Bindura, a senior developer at Raygun about performance monitoring.
Raygun provides tools and utilities for developers to improve software quality through crash reporting and browser and application performance monitoring.
According to Innocent, the absence of crash reports does not mean that software is performing well. Software can work - but not be optimal. Thus, Innocent takes a holistic view:
“I look at the size of my audience, and if it's something sizable, that gets a lot of traffic, for example, a shopping cart that gets a lot of traffic on a Black Friday. I would want to be in a comfort zone when I know that during the peak periods my application is still performing, so I tend to look at the end-user, how their experience looks like during very high peak periods. And from there I start working my way back to the technology that is supporting that application.”
Raygun really shines in monitoring the time spent in different functions and helping to improve the performance of highly hit endpoints. This includes performance telemetry of browser pages, the current application running, and server-side performance application monitoring. Raygun has lightweight SDKs or lightweight providers that can be injected into code. These provide a catch-all to deal with unhandled exceptions. They also encourage best practices for developers.
Greg asks how to track a user's journey through the application in order to see the endpoints being hit, and the user experience. A RAM tool can provide opt-in user information. In the case of Javascript, an SDK is integrated with code to create a session ID that follows the user through every single page that they visit. This internal ID can also be associated with crash reports.
Over time, Raygun can provide a complete picture of how the user session performed “from the point they visited your page, logged in, visited a couple of pages, and then left your application. The crash reports and the traces relating to that particular user are also tied up with that session on the Raygun side.” Innocent highlights a sampling strategy that reduces the noise of APM data.
Raygun also provides a birds-eye application view that provides aggregated stats on application performance: “For the run product, you will have each page aggregated over time, regardless of how many users you've had in a period of time. You want to look at the individual sessions. That information is aggregated and you're able to see, for example, your median, your P90, and P99.”
Innocent focuses on the P99 figure because “whoever is in there has had a terrible time, and that forms the basis of my investigations. I want to know why there are so many sessions in that P99, and that P99 is probably a six or seven-second load time. I want to move that to a sub-three-second.” Innocent provides a definition of P99 for new customers undergoing the journey of performance optimization.
Next, Innocent asserts that decisions should be based on numbers and empirical evidence. He has found that the use of actionable data has enabled him to redesign applications and focus on the mission-critical command needed in real time.
Innocent concludes: “I think the life of a developer is an interesting one. We fit in everywhere situations permit, and we definitely take different routes to develop our careers. But ultimately what we should all be concerned about is the quality of the products that I produce. This definitely reflects on my capability as a software developer. What sets me apart from the next developer is not the number of cool techniques I can do with code, it's delivering a product that actually works and what better way of knowing what works when you actually measure things. Everybody should live by the philosophy of assuming nothing, measure everything. Everything and everything should be measured.”