Susannah St-Germain, who joins to talk about becoming a Salesforce Architect without IT background, is a Salesforce MVP, Salesforce Architect, 20 x certified, BostonSFDC Co-Lead, and RADWomenCode Coach.
Sponsors:
This episode is sponsored by Clayton.
Go to Clayton website, request a demo or use the chat service by telling “salesforceway” code to receive free one month Secure Development Essentials.
Main Points
- Susannah’s self-introduction, her role in the company and the CTA exam journey
- Why and how did Susannah slowly transition from the music to the IT field?
- How did Susannah make the switch from the admin role to the developer role?
- What is the right mindset to shift to a Salesforce technical role? Susannah also shares her experience on this point.
- How did Susannah change to a Salesforce technical architecture role?
- What are Susannah’s current strugglings?
- How hungry are you to learn?
Links
Video Teaser on Salesforce Architect
Contact Me
If you enjoy this podcast, please reach me out to let me know your thoughts or simply say Hello. My (Xi’s) contact info:
Take care, until next time :)!
Transcript
AI-generated, unedited.
[00:00] This episode sponsored by Clayden. If you build on Salesforce, you know writing secure code can be really hard. Clayden makes it easy for you. Clayden plugs into your Git repos in seconds. And automatically protects you from hundreds of security vulnerabilities, such as CRUD FLS violations, code injections, vulnerable third-party libraries, and more. Clayton works with GitHub, Bitbucket, GitLab, and Azure DevOps. Go to getclayden.com/salesforceway to get one month
[00:37] of secure development essentials for free. It's getclayden.com/salesforceway. You can also find
[00:45] the link in our show notes. Clayden build on Salesforce, stay secure. Hey everybody! This is Xi Xiao. This is yet another new episode of Salesforce Way Podcast. Today I'm sitting with a new guest with me. Her name is Susannah St-Germain. Hello, Susannah. Hi, Xi. Nice to be here. Thanks. Thanks for sharing your time with us. So, before we start, would you mind to introduce yourself? Absolutely. So, my name is Susannah St-Germain. I am a technical architect at Odessa. So, we are a Salesforce ISV. And I was previously a Salesforce architect at a large customer, so I've been on both sides. And I have around nineteen certifications. I am also, yeah, I'm so I stay busy, right? I am also a co lead for Ladies Be Architects, which is a Salesforce community group. Co lead of the Boston Salesforce Admins User Group, and I'm also a Rad Women Coach. Wow, I know you are quite active in the community. Not only the the hats that you are wearing, also you are doing the presentations all around the world, right? Yes, absolutely. So last year I had the the pleasure of speaking at a number of different community
[02:16] conferences, the Dreamin events, in the U.S., in Europe, in Amsterdam. Shout out to your Dreamin. And also in in Australia, I had the amazing opportunity to go to Down Under Dreamin in Brisbane, and that was just an amazing opportunity. Yeah. That's cool. Could you also let us know a bit more about your current responsibility? You're a technical architect for the ISV solution. Am I right? Yes. You make sure. The solutions are designed in the correct manner. Exactly. So Odessa is a solution that works mostly with large enterprises. So we work to help large enterprises have data success on many levels. So data protection. We help with backup and restore, but also things like data compliance as well. And if you know anything about working with large enterprises and their data in Salesforce, it can become pretty complex pretty quickly. So I am there almost in a a consultant role to help enterprises leverage our tool, but also to make sure that they're setting up their Salesforce architecture. And customizations in a way that's going to help them protect their data and do what they really need to do, depending on where they are. If they're in Europe, you know, there's a lot of constraints and considerations around GDPR. If they're in California, here in the U.S., it's around CCPA. So things like that.
[03:46] That's a really a typical technical architecture row. And are you also after the CTA as well? Yes, so I am. I um I achieved my um two domain. Certifications, so the application architect and system architect. I achieved those now about a year more, a little over a year ago. So for the past year, I've been continuing to get experience just in you know practical, like day-to-day working architect role, and I'm hoping in the next year to really ramp up my CTA studies. And with the goal of being at least being putting my best effort into being ready by the end of 2020 is my my current goal. All the best to you. Oh, thank you. I know it's difficult. It's yes. It's really difficult to dedicate. And it's about it. I like I like it. I like the preparation because it's different from all of the other exams that are you know multiple choice, and it's more about focusing on a specific domain. What's been nice so far about my CTA preparation has been that it's more about just learning the entire broad landscape of Salesforce and also outside of Salesforce too, because there's a lot a lot of content, a lot of um. A lot of practical experience that's needed with integrations, with things like identity and access, and that really goes outside the the bounds of just you know Salesforce proper.
[05:16] I see, Susannah. I understand you didn't have an IT background, and then you somehow switched. That's correct. Yes. So I I went to school. I I did my college and my graduate degree focused on music. So I. I'll play the viola. That's what I thought I'd be doing. Yeah, that's what I thought I'd be doing. Of a life, yeah, for the rest of my life playing in an orchestra somewhere. But I, you know, I got kind of burnt out doing that. I was doing my master's here in Boston, where I still live, and. Was just not seeing really where my career was going to go. I was struggling to figure out, you know, what's my next step and all of that. And I went through a fair amount of career transition. Not at not at first with my eye on, oh, I know I am going to be in IT, or oh, I know I am going to work with Salesforce. Definitely not the case. I started to slowly transition from being a working musician to working in the business side of of music. So at a nonprofit, I was working as a fundraiser. Actually, so I was working at tracking donations and working with donors, and that's the first time I had the opportunity to work with a CRM system. And it wasn't Salesforce at the time, but I really loved the the process of learning about that particular technology. And I was part of a migration from one CRM system to another,
[06:47] and just loved the idea of thinking about how to, where does the data go? What are the structures that exist in this particular software package? And over the years, just transitioned more and more. Towards the IT side of the house, and eventually found myself, you know, being like, "Well, I wish I could do this full time. I wish I didn't have to also balance my fundraising duties with, you know, noodling around with software." Which over the over the years, I ended up working in a fundraising department that used Salesforce, and just really wanted to find a role where I could I could do Salesforce work full time. I see that you didn't know that IT was your destination. You were trying to see different things, right? You juggle in different balls on the air and see which one fits you best. Exactly. So I, yeah, I, I was. It you know I wasn't seeing my career in the music side, and then I I thought well maybe that was because the burnout is not because like a job opportunity or salary something. You know I think it was a little bit of both. I think it was a burnout paired with you know not seeing a lot of opportunity necessarily. It was around when was I in in grad school? So it was around. 2008. So in the U.S. at least during 2008, there's a lot of turmoil. For I think for a lot of folks in general around you know graduating, what am I going to do? And definitely, I felt that as well. I think
[08:17] I see. Yeah. And um, you know, I so I sort of was trying exactly what you were saying. I was trying to figure out where do I fit, right? I didn't know that it was going to be tech. I was dabbling with right with this fundraising role. And I, I then decided, okay, well, I'll try and see if this is what you know feels feels right. If this is where my I feel like my career should go, and so I went down that path for a while. I was like, okay, well, the next step if I want to do this, the next step for me would be to be like a an individual gifts officer, which is you know primarily not working in like the back back of house, not working with databases, but is out in the front line, almost like a salesperson. Raising money and closing deals. I was like, I'll try that and see if I, you know, see if I like that. Within, like almost immediately, I knew that that was not the right fit. I was like, oh. I miss you know I miss working with systems. I don't love this you know a hundred percent. Just like building relationships, it makes you know I'm. I'm a bit of an introvert. I was like, oh, I I definitely don't think this is the right fit. So I I continued to work until I I found what you know really seemed to resonate with me as a as as I don't know. Just as a person with my, I'm very, and we can talk about this in a bit. But I, you know, I love learning. That's I think something that I realized over
[09:47] lots of different roles. Like I wanted to be in a job where it was part of my responsibility to be continuously learning. And that's definitely something I found with Salesforce and with the architect role in particular. Like that's a main that's a main focus of my my job, and and that's something that I really do love. That's good to know. I want to put a bit focus on switch from maybe admin role. I understand you had admin role before as well, right? That's correct. How you shifted from admin to a developer, started writing code. You know, that's a huge gap for a lot of people. They're really scared of writing code. They don't understand. So how did you do that? Absolutely. So I was I was absolutely an admin. Didn't have the title, and I think that's something that especially people accidental admin accidental admin. But yeah, right. Especially people coming into the ecosystem. You know, you hear oh, there's admin and developer and architect. And honestly, you know, there's lots of different titles and titles vary job to job. I think that's just important to know. But I was doing admin work. Um, I was interested in solving a particular problem at the nonprofit I was at, and that problem was related to like the one trigger and the one class. Like we didn't have a lot of code, but there was a problem that needed to be solved with code, and I worked with our developer to to try and figure it out, and I. Through that process of like seeing, you know, what the Apex could do, seeing we had a couple Visual Force pages as
[11:17] well at the time, so back in the day before Lightning, seeing you know what was possible with that was really intriguing to me, and I was like, I want to understand this more. So first, it was the curiosity. So I think you know, not every admin has to become a developer. It's not a, it's not like a straight line that you start here and then you know you have to learn how to develop and then you have to be an architect or whatever it is. I think if you're not hungry to learn or there isn't that curiosity, that's that's fine. There's people who find fulfilling careers as an admin. For me, I wanted to. I was just so curious about this. I was like, how do I learn? So that was the first piece. If you don't have that curiosity and you're happy with what you're doing, that's absolutely okay. I think that's one of the pieces that sometimes people are like, "Well, I guess I have to learn how to code, so I'm going to do it." And then they're, you know, they're frustrated and they don't even. There maybe that passion isn't there. For me, it was pushing through when. I felt like you know, well, I I want to learn, but I am you know, this is frustrating. Um, I I think I you know I think it takes a particular type of person to want to push through those hard times. For me, where I found success, there are hard times. Oh, absolutely. It's even if you have a wonderful support system. So there's lots of resources out in the community that are targeted towards people trying to bridge the gap between admin and developer. Because
[12:47] honestly, for me, when I started, you know, I said, okay, I want to learn. I went, and this was before Trailhead, but I went and was like, okay, well, I'll read the developer docs. And if if any of you are admins and you're thinking about becoming developers, there's a huge gap right between. Being knowing nothing about code in general and trying to understand and use the developer docs, they're a huge wealth of resources. Once you learn how to read them and have a little bit of a base, but without that base, it's really. I agree, it is really daunting and challenging. So I I leveraged some resources in the in the community for me. That was Rad Women Code. For those who haven't heard about it, it is a ten week free. A program geared towards it's for women who are seasoned admins but are trying to bridge that gap. For me, that was the path that I took, and I'm now a coach as well. So I sort of come full circle there. But even with a great community, even with a great you know set of teachers, it's it is a struggle, and it is something that you know you need to be. I guess I had to learn how to be okay with not understanding everything a hundred percent, and and continuing to go anyway, right? Continuing to pursue it anyway, if I, and having faith in the fact that. If I keep studying, if I keep you know trying trying to learn the skill, similar to a language, if I keep pursuing it over time, it will start
[14:17] to click. Over time, little pieces will start to fit together and make more sense. And it's true. Even today, you know, I I pick up pieces of knowledge and they start to fit together when I you know when they when they do. You can't learn everything all at once. I think to anyone who is an admin that's looking to make that transition from admin to developer, that's probably a biggest my biggest piece of advice, like. It's it's not going to come easily, and I think you have to just keep persisting and keep learning, even when it feels like, even when you feel overwhelmed. That's a good thing. That means you're learning, right? If you're not feeling, if you're not feeling a little overwhelmed, if you're not feeling a little outside of your comfort zone, then you're probably not pushing yourself. Like you might be able to. Yeah, so I hear it's exciting adventure for you. But were you ever afraid of looking at the code or even open the developer console in the web page? You had that feeling as well. I definitely have. I would say not so much in being afraid to get started, but once you get to a certain point, and I feel this way, we can talk about it from the architect perspective as well. But there is a sort of leap of faith that you need to make when you are sort of ready to put yourself out there and get, especially when you're getting real world experience, because that's
[15:47] really where. You know the rubber meets the road. That's where you're really going to move your career towards. If you know it's a career goal and not just a hobby, hobbyist goal, and that's fine too. If it's a career goal, you're going to have to make that leap. To apply to your first job or to make a pitch to your current, you know, current employer that you want to start doing development work in in maybe a little bit of you know shadowing someone or or taking on a small project, but that's really where I start started to feel that right fear or where I um had to sort of overcome that was I I went and transitioned from my role as an admin to a role as a solo admin slash developer. At a at a company, and it was you know sort of that was my that was my huge test, right? I didn't, I no longer had a couple a team of a couple of people that was working. I no longer had a dev that I could ask questions to if I got stuck. It was sort of my my sole responsibility with the community. Of course, I definitely leaned on the the success community at the time, the developer community at the time to you know get me out of sticky spots when I when I got stuck. But that was, I think, the biggest hurdle for me. Like actually taking the skills that I learned and you know applying them to the real world. I think that's the the scariest part sometimes. One of my listeners, his name is Heiko Krammer, and he is a German.
[17:18] And he asked because he is from the admin to the developer role at the moment. He wanted to get the opinions like from you. What are the successful mindset to become a technical Salesforce? Well, do you have any tips for that? I do absolutely. Now that's a great question, and I love that the question is from the perspective of mindset. Like, what's the right mindset? Because I a hundred percent believe that. Anyone, if they want to, if they have the passion and they put in the time, can learn how to code. Can learn how to get a technical job, especially in the Salesforce ecosystem. You know, it. If you put in the time, it's possible. Um. So it's not a question of do I have the talent? Do I have the right background? Can I do it? I one hundred percent believe that anyone can do it. But I believe that it does take a certain mindset to be successful, especially if you are coming to this type of role, like I did with a career transition. If you don't have, you know, that. Maybe luxury of having a really nice base of understanding certain technical terms and skills and how the systems work together. So I think it's a couple things from the mindset side. I think it's not being afraid to fail. Because you are going to fail sometimes, I think that probably applies to everyone, but especially. Coming into something brand new, you're gonna get a project where you don't know how
[18:48] to do something or where you make a mistake, and I think you can't be paralyzed by that that fear. And I think it applies to pursuing, you know, taking a a leap in pursuing a job where maybe you're only you know 70 qualified or whatever is the case. I think that not being afraid to fail is one piece. I think also being committed to your own personal learning is another. So if you are making a career transition, it's likely not your full time job. To learn what you're trying to learn to better yourself, right? If you're an admin and you're trying to become a developer, you're likely not getting paid to learn how to develop, especially when you're starting out. So you have to take sort of ownership of your development and ownership of. Your time to make sure that you know if you're working a sixty hour uh an hour sorry sixty hour a week yeah sixty hour a week job as an admin or as a manager or whatever it is doing something else. It's going to be really hard to find that extra ten hours to study code, right? So you need to make decisions around that. Do you, you know? Prioritize your own learning and shut your work laptop at five p.m. You know, three times a week. Or what? Obviously, you know, different people are in different spots and have different constraints. But I do think you have to make those hard decisions around. You know, I'm going to take my lunch hour and
[20:18] I'm going to take it for me and study what I want to pursue instead of just working through lunch. You know, like you sort of do, at least in the U.S. Anyway, you know, you kind of do it without thinking. You're like, well, I'll just work through, take a working lunch, and take another meeting, or do whatever. But I think part of it's being really consistent and prioritizing your own learning is one mindset to get in. Knowing that you know you can absolutely be a wonderful employee and contribute to your company, but at the end of the day. You are, you know, you are your own CEO of your of your career. No one else is going to look out for you other than you. So I think it's really important to have that mindset, and then also just being being. Not afraid to fail, and then just the final one is getting outside of your comfort zone and being okay with the fact that you're uncomfortable. I think you know some people say, "Oh, well, if I keep practicing this or I keep pushing myself, one day I'll feel like totally at ease with." Doing these things and trying to to push myself, and the I think the fact is, it's okay if you don't feel at ease. Like I'm constantly pushing myself out of my comfort zone. Still, I've been. It's not like I would. The goal was to get comfortable in my, you know, in in learning. It was to continually push and be okay with that feeling. That feeling of, you know, what someone might feel as fear and and categorize it in their brain as fear is
[21:48] is actually maybe excitement, right? It's that excitement of trying to push yourself even farther. I love what you summarized the three points because it matches to what I thought about it. When we make the shift from admin to developer, those are the new knowledge you need to acquire, and if you say you have the passion, then you need to. You need to show it to people, right? You just you know take extra time to to work on it and practice your skills, and that's the way you get the developer role. That's the way you shift from the admin to the developer, and definitely it's a out of the comfort zone and. Yeah, and I would love to add. Just I I think it's you know putting in the time to get those skills, being outside your comfort zone. But especially, I would say this applies anywhere, but especially in the Salesforce ecosystem, it's doing that. But then, also, once you have those skills, or once you not even once you master something, but it's becoming involved in the community as well. Especially if you are trying to break into a new area, I think that that really pays a lot of dividends. If you are someone who's like, "Well, I am I am practicing, but how do I even get a job?" You know, I don't have. They want someone with a years developer experience. I am an admin. I don't have that experience. The way to really bridge that gap is to get in. I would say is to get involved in the Salesforce community, so that you make relationships, you get to know people who are. Hiring people who are looking to add to their team,
[23:18] I think that's maybe one of the the easiest ways. That's frankly how I. Got my first role in an IT department. I was working at a nonprofit. I was not IT background. I'd never had a corporate job before, but there was someone who posted on the Success Community before it was called the Trailblazer Community, and they said I'm hiring a business analyst at a company called Boston Scientific, where I worked for four years. And I saw it. I sent them a message, a direct message in the Success Community, and said. I'd love to learn more about this, you know, etc., etc. And we exchanged a few messages, and they said, "Okay, well, I'm I'm the person doing the hiring. Send me your resume, and I'll make sure that it gets, you know, to the right people." And I am a hundred, hundred and ten percent certain that had I not done that, had I not sort of taken that route to pursue a role, I would have been screened out by the HR process. In in a second because I did not have you know I didn't have the years experience necessarily I didn't work in a a medical field before Boston Scientific is a medical device company so I I had so many things that didn't meet the you know the twenty qualifications or whatever on the resume. I would have gone screened out, but because I made that connection, that personal connection with the hiring manager, they were able to. You know, I was able to sort of skip that first screening process. So.
[24:49] And it's still okay if you didn't get it in the end, right? Absolutely. Contact them if they say you are not the suitable one. You just carry on. Absolutely. Still, you are in your journey. Absolutely. And you know, the first time I. I applied to an architect role. I was at my my company. I inter I applied internally and I didn't get it. I um I applied. I went through the the entire hiring process. It was definitely a stretch role. My manager encouraged me to pursue. You know, we were like, well, go go through the interview process and you'll see where your gaps are, and you'll get some feedback. And I went through it and I didn't get it. And I was, you know, I was very much. I it was, you know, it was hard. I it was with these people that I already worked with day to day, and I was like, oh, they don't think I can do this. Should I? You know, maybe I won't ever be able to do it. Maybe I should like try and work. You know, you go through all the worst possibilities in your mind. Maybe I should go get a different job. All all these things, but I question yourself. Yeah, questioning yourself. And you know, six months later, another architect role opened on our team, and I went through the same process again. Even though I kind of didn't want to, I was like, oh. Do I have to do this again? I don't. If I, you know, if I fail again, what am I going to do? And this time, I got the role, and then worked as an architect at that company for several for several years. So I would say definitely that you know, getting being okay with failing and learning from the process,
[26:19] even though it hurts your you know hurts your ego, it can you know be hard. But that's the way that you you know that's the way that you grow. Hmm. Cool. So Susannah, what are your current struggling? I think everybody still struggles everywhere, right? Yes. No matter where you are in the ladder. Absolutely. So, where I struggle right now—that's a great question. I've been thinking a lot about that. So, I'm I am preparing for the CTA, like you said. I am. So, I'll take it in two. I'll answer it in two ways. There, I'm struggling with, or I'm continuing to fill gaps, and this is something that anyone who's transitioning into IT, especially through Salesforce, the the gaps that I need to fill now. From you know, as I think about my learning path. I'm filling in some gaps of things that I are non Salesforce directly related. So, things like learning about you know I know what SSL and TLS are. Like I know those you know acronyms, but what exactly you know? If I'm studying for CT, I need to know things like the level deeper, right? What exactly is like a VPC, a virtual private cloud versus VPN? Like, how do they actually work? Like, you know, all these buzzwords, especially as you know, just working in the the Salesforce ecosystem, you know them. But because we work in the cloud, we don't always need to think about that the actual technical layer underneath. But in order to be a CTA, you do need to know those things. You need to actually know how you know what's happening under the hood
[27:49] of Salesforce. So over the last year, that's an area where I've been continuing to learn, and I think it's important to. Take a hard look at where those gaps are. Even if you're, you know, like, well, I've been working, you know, as an architect for however many years, and I still have this gap. Well, that's embarrassing. That's fine. You need to address it and be honest with yourself about where you know you need to dig harder. So that's one thing that I I continue to I wouldn't say struggle but that I continue to be aware of I continue to you know make sure I'm I don't have any blind spots that I'm ignoring. But then from a personal sort of struggle that I think probably a lot of people can relate to is you know I'm at a point in my career now where I. Sometimes struggle with asking for honest feedback and accepting honest feedback. It's it's something that I think is so important, especially at no matter where you are, no matter what level you are at. But I think sometimes when you're just starting out, it can be a little easier to ask for feedback. Sort of ask for feedback from anyone. You're like, oh, I'm starting out. Can I, you know, pick your brain on this? I don't know anything about it. Yeah, I'm a junior. Like, let me have a conversation. But when you're at a more, you know, at a more intermediate or senior level, I think figuring out who are those right people to ask for honest feedback. Because sometimes if you ask, you know, it it some companies unfortunately, if you ask for feedback from every single
[29:19] person, they're going to be like, "Who is this person?" Especially, I'll say, you know, coming from from being a woman in IT, right? You can't just willy nilly go around asking every single person, like, "What do you think about this? What do you think about that?" Because there are, you know, some people might not take that as. Uh, being oh well, I expect her as an architect to be you know the the person who knows everything, right? Um, and you know no one knows everything, but I do think figuring out how do you ask for honest and open feedback, and then and then take that feedback and you know really apply it. At a non-junior level is is something that is sort of it's counterintuitive for all the skills that it it took you to get where you are. Right, you had to sort of push yourself and not be afraid to fail and go for like the big the big jobs. Go for the hard you know study the hard topics even if you don't get it. But at a certain point, you do need to to take a step back, I think, and ask like, am I getting this exactly right? Like, what is you know, am I teaching this back to you correctly? And so that's something that I've really been. Struggling with, but trying to do better at this year is finding those people that I can that know a lot more than me. Because there's you know there's every no matter who you are, there's going to be someone who knows something you don't know, right? And if you get in a room, there's going to be someone who knows X, Y, Z better than you. And it's been my my goal to find those people for the different areas where I'm not an expert yet, and and getting feedback and and honing my skills even more. So that's
[30:49] my current hardest struggle, I think. I have discussed with one of my guests in the past. It's about the softer skills. It's really hard to get the honest opinions. Yes. the The kind of output we had is that you need to take it seriously. You need to take even like a one to one conversation during the lunch, for example. You tell him or tell her that I'm deliberately practice this. So I think I have some mistakes. So could you tell me what I've done wrong? Once the other side see that you really put your heart in learning this, then they know. They won't really hurt you if they give you honest opinion. Yes, exactly. Conversation starts exactly, and I think you know. Honestly, people are most of the time people aren't gonna like if you're if you're someone coming into it and you're like I'm worried someone's gonna say something really mean and like tear me apart or whatever it is. In my experience. That's not the thing you need to worry about, right? People are, especially if you you sit down with them and you explain, you know, I've put in all this hard work, blah blah blah. Could you give me some feedback? Ninety nine percent of the time, the thing you have to worry about is not people being mean, but it's people being too nice. I would say, yeah, they're going to say, "Oh, you did great. Nothing. You don't need to improve anything. It was awesome." But you need to find that special person, right? Or that, and it's not always a person that's closest to you. It's not always, you know, it's it depends. But it's the person that's going to give you that
[32:20] honest feedback. That's You know, constructive. That's not hurtful, but um, that's not too nice either, right? Because otherwise, if everyone says, "Oh, don't change a thing," you did great. You know, is that is that is helpful, right? So it's a fine line. Cool. Excellent, Susannah. I think that's all I wanted to ask on this conversation. So before we round up, do you have anything else you still want to share with us? Yeah. So to wrap up, let's say I think we touched on a lot of my advice around pivoting and transitioning into a technical career. But maybe the one thing that I would add. Is that you know the the most important indicator really of how you're gonna of how you're gonna fare the indicator of your success is how hungry you are to learn I think that's if you have that hunger to learn I think you know that puts you ahead of a lot of other people I think the the second thing that is going to really give you that edge that you're looking for in in learning is Creating a strategy, and we talked about it sort of in lots of different ways in this conversation. But you need to have a strategy of how you are going to learn, and that's not just doing one particular thing. It's not just doing Trailhead, or it's not just getting certifications. It's you know what is your strategy for learning about a single topic. What topics do you want to prioritize? Because you can't learn everything about Salesforce all at once, right? It's so big. So thinking about, you know, not just being hungry to learn, but what's my strategy to make
[33:50] sure that I'm achieving the goals that I want to meet in in the short term and in the long term. So I think those are my two big pieces of advice I'd like to to leave you guys with. Excellent, this is Susannah. It's great talking to you today, and see you next time. Sounds good. Thank you.
[34:11] I am constantly looking for good guests. If you have venue guest recommendation, please reach me out. I'll make sure they are joining to the show to share their knowledge. Otherwise, thanks for listening to the show. I'll see you next Thursday.
