Come join our team!
I am growing my team at Salesforce in Burlington and have a great opportunity for someone who really enjoys problem solving and enjoys a challenging enterprise codebase.
It is especially perfect for those that enjoy troubleshooting/finding bugs (though it is not QA) and also like working on a variety of issues. We accelerate resolving issues which need the scrum team's help. It is the perfect position for someone who enjoys working on tough technical problems (in the code base), working with the support teams, as well as being a member of the product development team.
Please reach out to me to ask any questions, if you are ready for your next gig, reach out!
Jeff Dangel - Director, Customer Centric Engineering
Job Listing(s): (Don't let the word support in the description sway you- we are part of Product Engineering)
I am including two job listings as they describe the position slightly differently. My opportunity is in Burlington. Let's talk!
Learning a new programming language doesn’t have to be hard. Sure, there’s a lot of new stuff to wrap your head around: syntax, keywords and symbols, conventions, how to define variables and methods, arrays, and the list go on and on! But what if there were a technique and toolkit you could use to master a new language fast?
Who should attend? Anyone who wants to learn about mob programming and how to learn a new language.
We would like to thank our event host Chewy.com for all the support for making this event possible in Downtown Boston.
Resilient architecture is crucial for all cloud implementations. In this talk, we explore different design patterns to make a distributed application more resilient.
As part of this journey, for any process, we need to ask what if something goes wrong? Then, plan a course of action to the process auto heal without any human intervention and how to lower risks by performing canary deployments. Design starts with at first understanding of requirements and performing empathy map and value chain analysis.
Thinking application as stateless for all the API calls makes the system available most of the time requires creating a cache for common distributed data. Next, we examine how to deal with cascading failures, and timeouts scenarios. Applications, as part of auto-healing, need to Detect, Prevent, Recover, Mitigate, Complement so that the service is resilient.
Key takeaways for the audience are as follows: