Subscribe
Share
Share
Embed
CJ & The Duke speak with our special guest, Tim Woodruff, about his new book release: "ServiceNow Development Handbook, 3rd Edition".
We also speak about
- the pace of ServiceNow expansion
- learning in the early days
- who we look up to
And so much more
Authentic, Authoritative, Unapologetic ServiceNow commentary by Cory "CJ" Wesley and Robert "The Duke" Fedoruk
[00:00:00] Duke: Hey, everyone. Welcome to another episode of CJ and the duke as always. I am a co-host Robert, the duke at Orrick.
[00:00:06] CJ: I I'm Corey CJ, Wesley.
[00:00:07] Duke: This episode is brought to you by the service now development handbook, third edition, which was recently released by a treasure of the service now community and Titans of service. Now alum, Mr.
Tim Woodruff, Tim. How's it.
[00:00:22] Tim: Fantastic. I woke up this morning and I got to be me again for the whole day. So I'm pretty jazzed about that. And I'm also very grateful to be here.
[00:00:30] Duke: I'm super judged. Every time I wake up, and I'm not buried alive in a box. I'm just like, this is going to be a great day. I'm so stoked about today.
[00:00:39] CJ: I'm just here, man.
[00:00:44] Duke: man. Okay. so Tim, I can't imagine how it would be that somebody would be in service now, but not know about you, but just in case, why don't you give everybody a quick intro?
[00:00:53] Tim: Sure. I'm Tim Woodruff. I am a service now, developer administrator architect, kind of guy. More on the technical, and coding side. as an architect, I'm more of a technical architect. I've written a bunch of books on service now, development, administration, and architecture. including, as you mentioned, the service now development.
Now, just release the third edition of that. Also learning service now service now building powerful workflows. Don't buy that one. and, I also run SN pro tips.com service now approach tips, where you can find all kinds of free, tools, that are completely free, totally open source available to anybody and loads of articles on how.
service now works and all kinds of arcane theory like that. Just loads of fun stuff to fill your brain hole with.
[00:01:39] CJ: Nice. So Tim, I got to ask, where do you find the time to do all of that?
[00:01:45] Tim: Well, it does help not to have a life. I'm the sort of person that if I get bored, , I have to go and do something and sometimes I can bring myself to play a video game for a few minutes at a time. But then there's this voice in the back of my head that goes you piece of garbage, what do you do?
And go and build something. It's something it's a. It's relentless. I just need to always be working and, and, fortunately, or unfortunately I don't really have much of a life outside of my work, which is perhaps not so unfortunate because I really do love my work. So it works out perfectly.
[00:02:21] Duke: there was that saying, right. Do what you love. You'll never work a day in your life or something like that. I don't entirely bought into that, but I have a question and that is if somebody hasn't read a versions one or two, if somebody hasn't read additions one and two of the service now development handbook, what's it about? And then on the tail of that question, what is version three, bringing.
[00:02:44] Tim: the service now development handbook is a book that is really geared toward people who have at least a little bit of experience. So I'm really glad that you asked that question. I would hate for someone who's brand new to service now thinks I'm going to go learn service. Now, what do I want?
I want to go by the handbook. It's too short for that. And, a lot of people don't really read the descriptions of books, where it, does say that, but you don't want to pick it up. If you're brand brand new, you want to get another book that I've written called learning service now, , which is in its second edition right now.
That one is great. Learning the platform, just getting started with it and figuring things out. Once you finish that book or some of the development courses on service now, And some of the basics and you know, the platform of it, and you want to level up your skillset to the next level and maybe go from, administrator who's dabbling in development to mid to senior level developers.
Over a relatively short amount of time. That's who this book is for somebody with a little bit of experience who wants to really level up their skillset and their career.
[00:03:50] Duke: And what is sir? What is sorta addition? Bring, , the second and third.
[00:03:54] Tim: That's a great question too. , the third. edition adds, , about 60% net new content, , on top of. the previous book, so, or the previous edition. So it's just loads of stuff is in there. Some examples are like, I go into a lot of detail on the third edition on debugging. , how to, you know, when your code isn't doing what you want, how to figure out why that's happening.
, and I'm not just talking about ad, you know, GSK. Info and or GS dot log or something and print out some variables. That's obviously something you can do, but it goes into a lot more detail about how to really understand how your code is working. We even get into like rubber duck debugging, but also more on the technological side of how you do debugging client-side debugging, which a lot of people don't know how to do.
, in servicing. there's a little more stuff about like naming conventions and pedantic, stuff like that. But the vast majority of the new content is focused around the deep tech. I'm talking about performance, configurability, modularity, , learning about system properties versus user preferences versus session variables.
And. client data and understanding how all of those various options for configurability and modularity, , in your application work together and which are appropriate for which situations, talking about security, loads of new information on update managers. Cloning and clone cadences, as Well,
as some examples of how to do your clone cadences, depending on how many separate instances you have just loads of new stuff.
I think even if you've read the second edition yesterday, if you pick up the third edition today, I think you'll find, , just a boatload of new stuff. I think you'd be very happy.
[00:05:34] CJ: So, let me ask you this question. , could I take a person, I won't say off the street, but a person would, you know, some degree of it experience and some degree of. I'd say, you know, enough, industry level intelligence, right? Because they have the it experience could, give them your books and get them up to speed to be like maybe a entry-level service.
Now, admin based on your.
[00:05:56] Tim: If I have accomplished my goal, then yes. My goal is to, , create a series of books that allow you to do exactly that there are some gaps in there. , and in fact, I'm very glad you asked that question because I have an article at learn dot. S N c.guru, , about how to learn service now. And of course I mentioned my own books in there, but I also mentioned other resources as well.
It's not a post for self promotion. It's genuinely like how, do you learn this thing and give the most out of it. And some of the stuff that I mentioned in there is like, you, you really might want to understand some stuff about relational databases and how they work. , how query languages work, understand.
The learning service. Now, book is not going to teach you ITIL. It's not going to teach you a relational that, well, it is going to teach you a bit about relational databases, but there are some, some deeper concepts that it's useful to know that post gives you some, some of that additional context. Um, but aside from the, a few of the things mentioned in that post, , learning service now, and then getting yourself a little bit of experience.
Maybe reading some of the articles on SN pro tips.com and then reading after you have a little bit of experience experience there after you have a little bit of experience reading the development handbook that should, if, if I have accomplished my goal, it should get you to be a pretty hardcore service.
Now, developer.
[00:07:23] Duke: No.
[00:07:23] CJ: I love it, man. I love it. I think there, there is, a huge lack of a path I think, in this industry. I kind of stumbled my way from, , the magic community from, , old legacy BMC, shout out to, , to those Yahoo groups and, and then ended up in service now. And you can just kind of figure it out as you go, right?
Like, it's great that there isn't, that. a lot of reference material out there. , and in the form of your books and your articles, right? They can give folks, on the path to become a ghost Arizona develop.
[00:07:52] Tim: Yeah, absolutely. I mean, there, I, I remember when I was first getting started and, service now was still very new. It was something like a decade ago that I was first getting started. and I remember. All I so many moments of realization of like, oh, that's the wrong way to do this and doing it this way.
Really, really screws everything up and sets me up for failure forever. , cool. I've been doing it that way for like a year, so
[00:08:22] CJ: clients.
[00:08:23] Tim: I'm Sorry, I should start looking for a new job so that I don't have to face the shame of everything I've already built. Um, And I realized that like, , you know, at first of course it's imposter syndrome and that kicks in hard and you think, oh my God, I don't belong here.
I'm not a developer. I'm not one of you. I belong in this space. But then you realize, oh, everybody's making this mistake. You know, you get to a certain point and then you go to the developer community, slack, the discord, the community forums, and you think. Wow. Everybody else has the really stupid questions that I did too.
Maybe they're not so stupid. Maybe I'm not so stupid for having those questions and for not knowing that out of the gate. , and so when I was writing these books, both learning service now, and the development handbook, I was really trying to channel that, that inner newbie that I was, you know, when I was first getting started.
And since then, I've trained a lot of people on how to do service now of development, administration and architecture. And I was really trying to channel them as well and see the material and the concepts through their eyes, with my teaching background, I think. , it makes me pretty okay at, doing that, but the most helpful factor in the creation of these books has really been the community itself and seeing what questions people ask and getting feedback on, Hey, I've explained this thing in this way.
What do you think, is this helpful to you? Or is it maybe a little unclear in some ways? So it really is, if you're ever feeling that imposter syndrome, just go to the community and look at the questions that other people ask and realize that everybody started saying.
[00:10:02] Duke: , you know, what's crazy. , I think we're going to get a wave of that. Like we've never seen before of just everybody's a newbie again, like if you think about all the stuff that's coming down the pipe,
Like flow designer. Isn't really new, but I think it's finally there that nobody starts in legacy workflow anymore. Right.
[00:10:19] Tim: Yeah. And, and there's a lot of stuff that's, , new, but not So,
new, but that's just got to a point where companies are starting to say, Hey, we want this built in this new way. Now that it's in this in a state that it can actually have. Something close to feature parity. The same thing happened with service portal.
When it first came out, there was so many missing features and now it's, it's really good. Of course. Now they're replacing it with new stuff,
[00:10:43] Duke: Well, that's what I'm talking about. And it's just I remember when being a newbie meant figure out what catalog is, figure out how to build your own custom task based app. You know what I mean? And you were basically there.
[00:10:54] Tim: Yeah.
[00:10:55] Duke: You're not a newbie anymore, but now. you can get decent at virtual agent and still not know about everything available in catalog.
Still not know how to operate the, that new, like the front end catalog builder for the low-code depths. And then, and then now everybody's going to have, to, record. With that UI framework. If they're coming out with, that's going to be quote unquote standard in the next version or two, and it's like, we're going to go from, an industry full of pros, finally, a decade and a half later to two everybody's at zero again, because nobody had knows how to build whatever it is.
[00:11:33] Tim: Yeah.
And, uh, Rob, when you were getting started and when I was getting started as well, I think you've been doing this even longer than I have. you know, when we were all getting started service now was little more than some sugar on top of a SQL database that later became a Maria DB database. and now there are so many layers on top of that, just database and an application server running Mozilla rhino, a Java based implementation of JavaScript.
And there you go have fun. Here's an API to interact with the database, go nuts. Right? And now. It's there's so much extra stuff, not necessarily between you and the database, but also on top of the database that you then have to interact through. And they're optional, which is one of the great things about service now is it keeps the platforms so open to development and to creativity, but there's also so much cool stuff that they've built that we now, as developers want to interact with and want to provide those features and functionality without reinventing them for our clients.
But still fundamentally it's some sugar on top of a database with a Mozilla rhino Java based implementation of Java on an application server. And then all this other stuff on top. It's really cool. How far it's come and a little daunting. I'll be honest, but still really cool.
[00:12:52] CJ: So let me ask this question. , As, you know, there have been a lot of features that have been added to service now, and there's a lot of new customers and because of their, because there's a lot of new customers and because of the pandemic and everyone's moving towards a more work from home cloud centric infrastructure, I feel like there's been a, a surge in service now, , uptake and demand and so on and so forth.
How do you think all of that growth in. Impacts your book. , and from a number of perspectives, one on the ability to sell it, but then also a two on the ability to get in front of.
[00:13:28] Tim: Well, I think in. The, in the short term, I don't think it's going to make a lot of difference because it's geared toward people who already have some amount of experience. I think I, I have noticed a spike in sales of learning service. Now, the, the book that's kind of more for beginner to intermediate service now, administrators and developers.
but as far as the third edition of the handbook, I don't expect to see a significant change in the short term, but in the longer term, I might lead to more sales personally. I don't really track sales that closely though, because I suppose the main reason is I don't, I make hardly anything off the book.
I've priced it in such a way that, I want to make it as accessible as possible to everybody. I just really, truly love to teach and to help people out I've given away, you know, a bunch of free copies already to people who just couldn't afford it. I would like contrived reasons to give them away on Twitter and stuff like that.
but, uh,
[00:14:23] CJ: of love.
[00:14:24] Tim: Yeah, that's, that's really it. And the fact that the community did the same for me, like when I was first learning service, now the community did so much to get me up to speed, help me out. It was very patient with, you know, my newbie questions And not understanding the unique ways in which the platform did things.
I want to return the favor and do everything I can for the community of newcomers and seasoned pros alike, , who are out there now.
[00:14:49] CJ: And let's drill down into that a little bit, right. Because how much do you feel that the, the community helping you out actually puts you on the path wants to become a rock star, you know, service now, architect, developer slash person, right. And too, just to keep you in this industry and enable that career path to even, happen.
[00:15:09] Tim: a hundred percent of that can be attributed to the community. I would not be doing service now right now as a career at all, if not for the community, especially because back when I was getting started, we didn't have the developer site. we barely had a Wiki, uh,
[00:15:24] CJ: Ah, but the Wiki was cool, man.
[00:15:27] Tim: The Wiki was cool, but there was a time when even the Wiki was new and all of this knowledge was not well-organized or, or, you know, if it existed at all, in anything other than like some article on some, you know, medium website.
and so without the community to, you know, sometimes just to point me to an article and be like, it's already over here. And I was like, oh, now, now I know what terms to Google, , and not bothering anybody over it, but, without having that community available, I would never have been able to get to where I got to the point where I could, I think that there are two fundamental forces opposing, every developer.
One is the force pushing you forward. And maybe that's your own passion. Maybe it's the people around you. Maybe it's your bills, your spouse, or the community it's. Helping you out. And then there's the force of discouragement. the difficulty of learning something new and most importantly, imposter syndrome.
And you can really distill this battle down to imposter syndrome versus your support network and the people who are there to help you and the resources you have available. If the resources are stronger than your imposter syndrome, you might just become an amazing develop.
[00:16:39] CJ: Man. That's a great point. That's a great, great point. I think about it and the same thing, right? having the Wiki and having, the folks in the community and then having people like, , duke, who, honestly like kept pushing me along the way. When I wasn't sure how to measure my skillset versus the other folks out there, and he's telling me, man, dude, you're a rock star, you got this.
And you know, and I'm not much for a imposter syndrome, you know, I'm fairly cocky guy. but I totally had, imposter syndrome around, my service now skills early in my career. And, you know, without, like you said, without that support network and without the community and such, and being able to validate.
my knowledge against other folks, I'm not sure how long it would've persist it.
[00:17:20] Tim: I know what you mean. Exactly. If I could instill one piece of wisdom that I've learned through my failures over the years, into every single new and intermediate and even senior developer out there, I would grab their face and scream into their brain that when you feel And I think everybody gets this feeling. Maybe not, maybe it's just me, but I think everybody gets this feeling where there's a thing you don't know. And suddenly you're confronted with this feeling of, I should know that. If you approach those moments with humility or even confidence in the face of not knowing something to say, Hey, I haven't heard of that before.
I want to, I want to understand it. Don't say, oh, I should have known that already. I should already have that in my head. don't even approach it like that. Come at it. with. Wow. That's awesome. I want to know about. Tell me about that. Not only will your imposter syndrome shrivel from that impact. Also the people that you're talking to, you think they're going to go this idiot, you should totally.
know about this thing.
They're not, no One is going to do that. Nobody decent. And if anybody does excise them from your life immediately, instead, anybody worth their salt will say to you. Absolutely. I'd love to talk about this because I too am passionate about. And I love to share in my passions. I think that's the way it should be.
And that's the way most developers really are. And if you approach them with humility or confidence in the face of, you know, not knowing something, rather than trying to BS your way through, maybe an interview and this applies to interviews as well. You might think interviews might be an exception, one of the few exceptions, but no, it applies to interview as well.
If you're in an interview and somebody says, do you know about this thing. And you don't, even if it's just a throwaway question, have you ever had. I don't know, flow designer. Right? If you haven't say no, say, oh, no, but what is it? Tell me about it. Everybody will appreciate that more, including you. Okay.
[00:19:15] CJ: Yeah, totally.
[00:19:16] Duke: thing. I want to know, Tim, we talked a little bit about the community members that helped you out way back in the day.
Could you maybe make a couple shout outs to people who helped you in your.
[00:19:25] Tim: Even people who have just been like a sounding board for me to bounce, terrible ideas off of, people who, can contribute and can just listen, are so valuable to me. And, I am really bad at time and it names, but a couple people's names pop into my head. , we'll Mitchell, is, a friend of mine who, is always around for me to bounce some ideas off of, Jace Benson.
I think his website is what is it? J star pro J a C e.pro. Oh, my God. Amazing stuff. Great blog, go and read it, subscribe to it and send him goldfish in the mail or whatever it is that normal people do to say. Thank you. he's, uh, an amazing member of the community. and, I've been following your content as long as you've been making it.
[00:20:10] Duke: Oh, thanks man. But you talking about imposter syndrome early? That's me. every time I look at, gosh, the Rome release notes, man, we got improvements to this feature. Excuse me? What feature? That's a thing now. Oh my God. Yeah, I appreciate it. But I'm deep in imposter syndrome right now.
Deep.
[00:20:30] Tim: man. I had a similar moment recently with, the debugger. I was looking at the debugger and I noticed, oh, there's this little bar at the, I'm talking about the server side, a debugger here. There's this little bar at the bottom. It says console. It's got a little Chevron, little arrow facing up. I click on that.
Oh my God, there's a car. There's a server-side console. And I can just execute arbitrary code while my code is running. That's so cool. And then I, and then I posted to, uh, ServiceNow developer, community slack and discord channels. and a bunch of people were like, Yeah. that's been there for like a while. And I was like, well, why didn't any of you? Tell me.
[00:21:13] Duke: are my favorite moments. So, cause I'm always billing myself as not a real dev, like I'm not a devs dev. If, if service now imploded overnight, I would not go into development. Right. which I think is like the minimum standard to be call yourself a dev. but
[00:21:26] CJ: Man, listen, I.
[00:21:28] Duke: for me anyway, right. And I'm always hardest on myself, but like, I think.
I was talking to it like a serious dev friends of me. I really look up to and they didn't know about log points. And I'm like, then how do you, how do you troubleshoot anything on pride? You know, they give you this, they give you the stink-eye like, are you saying you can put blog statements into code on prod?
Like that's a no-no right. Not if you're using log points though. So.
[00:21:53] Tim: And, and conditional log statements too. Part of the same thing, when you go into create a well for anybody listening to this who doesn't know that you're right. Click on the little, break point, the line numbers in the script editor, right? Click on that. You got more options. You can, you can go nuts with it.
[00:22:09] Duke: It's crazy. that has been a big thing in my mind. I don't know how many weeks of labor I've spent over over 13 years. Like, oh, we have a problem in prod. I know it's a problem with descript. I know it, but it doesn't manifest the same behaviors on death. No matter what I do, it's just like, how on earth can you troubleshoot it?
Where it's manifesting?
[00:22:31] Tim: Yeah.
And to, pivot off that, the differences between prod and dev and dev and test and test and prod. , I think a lot of people, and it's actually one of the sections that I added to the third edition of the handbook is about, cloning and, instance management and update manager.
and, and tracking, keeping your instances in sync is very, nearly a full-time job. it's a constant battle between, on the one hand, you don't want to interrupt development and tell everybody, okay, export all your active development. And Paul, I have a one day freeze where the, the clone happens and all this kind of thing, but on the other hand instance, drift.
Deadly. I have tried so hard, so many times to explain to one development team or another. Listen, if you have two different dev teams working in two different dev instances and they both touch the same file, you have a problem because if you deploy them in the opposite order from which they were developed, then you're going to have a collision and it's going to be confusing and you're going to have to manually merge.
But if you deploy them in the same order, they were. Then update B will overwrite update a update, able just disappear and stop working. And you'll have no idea why, because update beach shouldn't have done anything to update a was working when you deployed it. Eh, it's, it's a thing you really have to think about a lot.
And to that point, I have a clone cadences specifically. I've got a. sub chapter section on multi development environment, clone cadences, that allows you to have basically zero downtime between clones, but also basically zero risk of instance, drift. I think it's a pretty neat approach that I've implemented it.
A couple of clients that I've worked at and it's worked out great.
[00:24:16] CJ: Nice. Yeah. I find that clones and updates and that whole ecosystem is always one of those things that it seems like everyone is always doing it different. , no matter where I land, right? Like I get to a client and say, Hey, what's your clone, cadence. All we have in cloned. Uh,
[00:24:32] Tim: oh yeah. Oh, that's the worst answer. What is cloning? Oh, God.
[00:24:38] Duke: Or something that they always, they always plan to do, but never do.
[00:24:42] CJ: yeah.
[00:24:43] Tim: there's always some reason you've got to put it off. Oh no. We have some important development right now and we can possibly pause it, but there's always that kind of.
[00:24:51] CJ: my other favorite is I pop into client big client, right? Multinational company, They got a ton of instances, right. You get in and you're engaged in a project. And all of a sudden you get an email with 20 minutes ago saying, Hey, we're closing down over the, over the instance where you're doing your work. Um, thanks.
[00:25:07] Duke: How, how else can we have been of help? Right. How else can we help you?
[00:25:12] CJ: Right. I'm like, you know what fine. If you just want to throw away all the money, you just pay me over the last three months to build this crap, whatever.
[00:25:20] Tim: Yeah, I actually I've had to do so many ultra rapid updates set and batch backups, you know, export to XML to back them up, that in most of the instances that I've worked in, I've added an exception to that a UI action that allows you to export it to an XML and updates it. so that it doesn't require that you close the updates at first.
And as long as you, you know, you, you have to be careful about it. You can't just go in and change that role. There's some logic you have to update as well, but you can do it. There's no reason that an updates that has to be closed in order to be exported for a backup. , you just want to maintain your version numbers and be careful about it.
But if you, as long as you do that, there's no reason that. You know, back them up while they're open and it does contain all of the updates. Even if they're open.
[00:26:01] Duke: That is awesome. I didn't know that.
[00:26:04] Tim: I should maybe add that to the fourth edition of the handbook.
[00:26:06] CJ: think you shut.
[00:26:09] Duke: But speaking of that, do you find that the drift between not drift or strong, but the expansion in base functionality between the platforms, is that a problem for you version to version or just not in your scope? It's the question even make sense?
[00:26:23] Tim: Between the, do you mean like between platform versions?
[00:26:27] Duke: Yeah, like between, I mean, between Paris and Rome, there have been to me like so many huge, fundamental, additions and not in terms of what we were talking about earlier, where like this stuff is kind of like maturing as it's going, but just completely new stuff, like instant scan, right. Which, helps a ton on upgrades and just general, creating and sustaining good architects.
does something like that come up in every version. You're like, oh, cut. Damn. In another chapter, I got to write.
[00:26:58] Tim: so.
[00:26:59] CJ: Fred,
[00:26:59] Tim: Ah,
[00:27:00] CJ: stop adding stuff to the platform. I can't keep up.
[00:27:06] Tim: Guys, I am writing these chapters as fast as I can. Could you please stop making it better for like a month? Um, um, not so much because between additions, I also I'm writing on SN pro tips.com and, um, if you're not subscribed there and you have, or if you buy the development handbook and you're not subscribed to SN pro tips, go get subscribed.
I really truly do not. I'd send out maybe one email, a quarter. If even that, and it always is full of content. It's never like, Hey, come and like, give me your money for consulting or something. I never use it for that. It's 100% for content and free tools and articles that you probably haven't seen yet.
So go get subscribed to that and what you'll see. His articles and tools and all that cool stuff between the big additions of the book. And some of that stuff makes it into the book. Some gets rewritten in the book as a bunch of net new stuff that never made it into an article in the book. But if you want to know what cool stuff is happening in between additions of the handbook or learning service now service now pro tips is where I put all that.
And, you know, it gives me something to do. And by writing those articles, it gives me sort of a, pre-written at least outline of the kinds of concepts that I know that I want to touch on in the next book. So it helps me out.
[00:28:25] CJ: Love it. one question that I haven't asked what made you decide to write a book to start? I mean, cause you, you, obviously you have a blog, right? Like you write posts there they're very informative folks can, subscribe and get email updates and all that kind of stuff.
And you can just continually pump out content there and it is a lot more lightweight from the perspective of a responsible. Right. They'll take it on the undertaking of creating a book or writing a book, publishing it, going through that whole process, you know, as a, as a next level layer of responsibility and just kind of effort.
So what made you actually sit down and decide I'm going to write a book about services.
[00:29:06] Tim: That's actually a really great question. , so , the reason that I did that there, there actually was a really specific reason is because I was thinking it was when I was, , writing the, how do I learn service now, article, which is at learn. S N C Don guru like Sam Nancy, Charlie . when I was writing that article, I was thinking, wow, you know, I've got a bunch of other articles here about like this specific arcane piece of the platform, but Anna got this article on this piece and this article is an introduction to that, and that's really useful for a newbie, but it, you still need some kind of foundation.
How do I. Draw some kind of wiggly line through all these articles and give you here's all the information you need. Start to finish, start here, then go to that one, then go to that one and so on. And I realized that not only all of that information, not on the blog, because of course there's a lot of stuff that, you know, most people they see in.
On that. And they're going to be like, well, that's basic stuff. Most of the people subscribed to the blog are already a little bit experienced at least. And so I don't want to necessarily write a whole article on. Here is the elements of the service now, UI that you need to know what they're called, right?
So if someone refers to them, you know what they're talking about? I don't want to make that an article necessarily. And so I realized I need another vehicle for this information. I want to write this down and convey this to somebody because I think that the existing training while often pretty good, still sometimes, Rob when, when we did that Titans have now interview, I talked a little bit about a lot of people when they're learning, learning JavaScript.
They, ask. Okay. So I I've learned enough JavaScript to write some code and make it do a thing. Where do I actually, write the code, give me like a window that I type in code and then press a button. And it runs, how do I do that? Just fundamental questions like that. I want to be able to answer those questions and tie all the other information together.
So how do I do that? And the answer was a book or a series of books on. Service now development or well administration and then development, and then architecture starting with the UI and then moving into the deeper and deeper and deeper tech. and I just decided that was the best way to go about it.
I also want to do a video series at some point and break them down into topics, but, you know, I'm lazy. So I haven't done that yet, but one of these days,
[00:31:33] CJ: Yeah. Always harder than a written word. I find. I mean, you can just pull up a word document or whatever and just start typing and that's all good when you're doing video, that, get it all altogether and, and yeah. Yeah, no, thanks.
[00:31:47] Tim: Yeah. And it's, it's hard to jump to, unless you break them down into tiny little chunks in each video is like a three minute long thing on one specific topic. , then it's hard to like search through and find exactly what you're looking for. or to go through, start to finish, cause they're all broken up and you kind of run into the same problem as the articles.
So for me, for the first version of, how am I going to get this information out there, make it accessible and make it a thing that everybody can, just pick up and just screw it. Let's go, let's learn service now, starting today, starting right now. and that the way to do that for me was.
[00:32:21] Duke: All right folks. We are at time. I want to thank Mr. Tim Woodriff for joining us again today. Please check out his book. It is at handbook dot SNC dot GRU. Some other links that he has, which you'll find in the description below. Learn dot SNC dot GRU. If you're a beginner and want to work your way up to the development.
We also have, learning service now, which is LSN dot SNC dot GRU. , we have a link for talking about service now, careers, career dot SNC, Docker, Ru, and then his blog that uses between his versions of the book is SN pro tips.com. Thanks again so much, Tim. We really appreciate it.
[00:32:58] CJ: Yeah, absolutely.
[00:32:59] Tim: Thank you very much for having me. I appreciate it. It's always a joy talking to you guys. And it was great having.
[00:33:04] Duke: Punta with ours, Corey, how many they get in touch with you?
[00:33:06] CJ: Yeah, they can find me at LinkedIn. at my full name. Corey Wesley. I typically, like I say, always except most connections. and I'd like to chat too, and if you want to reach out to me at, tech voyant.com to. that's where my businesses and where we do practically everything servicing non-related
[00:33:22] Duke: For a second there. I thought you were going to say like, LinkedIn is your site. Find me at my website, www.linkedin.com.
[00:33:33] CJ: where me and my billions of dollars hangout.
[00:33:38] Duke: All right. And if you want to get in touch with me, I'm at the duke.digital, Where you can find my course hired the definitive guide for profiles that when service now jobs. All right. Thanks for listening folks. And we will see you next time.
[00:33:49] CJ: Bye-bye.