 There's the table of contents, elements of your developer reputation. So why do you care about your developer reputation? Hiring managers won't guess what you know. They only see what you show. And employers won't guess what you can do. They see only what you can demonstrate. And then what you take away from open source is not as important as what you give back. And really, those are the three main points, I think, of the entire. You'll see how this relates to everything else as we go through it. Elements of a developer reputation. We're going to see this slide twice, once here, and then once toward the end of this section, in the middle of the entire presentation, where we first we're going to look at what it is, and then we're going to re-evaluate what we have in light of this. So hiring managers are going to look for what you have done, what you can do, and also whether you give back. What you've done, that's evidence of experience. That's your resume, which feels a little obsolete, but everybody needs a resume still nowadays. You need to have it. Your LinkedIn profile in some ways has replaced your resume as the main thing that people look at. If you use your LinkedIn profile intelligently, then you can definitely get a lot of mileage out of it, even more so than a well-crafted resume. Because it gives you the opportunity to link directly to your previous employers, who presumably also have a presence on LinkedIn. And then if a hiring manager is looking at that, they can click through that. They can see the website that you worked on. They can see who else works at the company. They can see the person that was your manager. And they can write to them directly for a reference. They don't need to ask you for a reference. It's all connected. It's all wonderful on LinkedIn. If you fill an outright, if you really do a good job with your profile, then portfolio websites. I'm always a big fan of people setting up portfolio websites. And it doesn't necessarily need to be, if you're going for a Drupal job, you don't need to have a Drupal website. If it's a WordPress job, you don't need to have a WordPress website. If you're going for a Laravel job or a Symphony job or a Spring Boot MVC job, you don't necessarily need to use the same platform for your website. But it does help to have something online that shows that you know how to publish something online and that functions as a portfolio of work that you've done up to this point. Now, if you've got project links really, we'll get into more detail later. I guess I'll just read the table of contents. But basically, if you've got things that are live now that you built, you should link to them directly. If they are live, but they're not on the public internet, sometimes you make a site and it's only behind a VPN on a private corporate screenshot of it and include that with a description of what you did. Or if it used to be online and it's not online anymore, then hopefully you've gone to archive.org while it was live and you've got a snapshot of it or someone else has if you didn't try to do it. So all those things are evidence of your experience. Then you've got evidence of skills, code samples and public repos. There's the usual suspects, GitHub, GitLab, and Bitbucket, which I always mention. And also git.drupalcode.org, which is Drupal specific. And you get the opportunity to log into that with your Drupal .org account if you make one of those. If you don't have code samples that are full, then you can just have snippets that are just little pieces of code that kind of do something interesting that they don't really stand alone as an app or a site. And very often you see these in these code playgrounds, like CodePen, JS Fiddle, JS Bin, CSS Deck, Code Sandbox, Glitch, all of these are active links if you, I'll just mouse over it, but they're all active links. And if you download, I'll make sure I upload a PDF of the slides. And also we can link to the slides on the beautiful AI platform. So all of these are worth taking a look at. I'm not going to get too in-depth about it here. And then demo apps are mostly important if you don't have any websites. But you just want to be saying that that shows you can code something and that it looks good and it functions. That's very helpful for people when you're looking to get your first job and you don't have any professional work that is in your portfolio. Those are all evidence of your skills. And then there's the community contribution if you've contributed. If you have released software that other people are using, open source software projects like Composer or NPM packages, Drupal modules, WordPress plugins, all these things, hiring managers love this. They can download the code and see if it runs. They can look at the source code online because it's open source. They can really evaluate whether you code to the standards and follow the best practices and your code is secure and it's well-commented. It's the type of code that they're looking for someone to be able to make. Or you could contribute sometimes to open source in less substantial ways rather than having an entire project that you maintain. Maybe you've just contributed patches to other people's projects where you haven't written patches, but you've contributed bug reports to show, oh, this broke and I have a good idea why maybe someone else can write a patch. And in the Drupal world, those are called issue queues on the project page at Drupal.org. Then there's online communities. You can participate in these. Exchange, Quora, this is kind of a partial list of something I'll go in more detail later. But primarily, there's a question and answer forum. So although Drupal.org is a special case, you can also do blog writing or presenting like me at this lunch and learn today or speaking opportunities at conferences and different forms of networking. And all of these things can enhance your developer reputation. So let's talk about projects. What are projects? That's something that you did. It's professional web development work that you made for a client and it's published on the public internet. Now, I used this slide before and you'll see if you go back to the how to succeed and technical screening. But basically, there are some edge cases. Maybe you've done professional software design for a client, but it's not a website. Maybe it's a mobile or desktop app or something else. If that's the case, good on you if you've actually published a Android app to the Google Play Store or ILS app that's in the Apple App Store. Those are great things and you can link to those. And I can at least take a look at it, I actually have desire to actually download it or purchase it and put it on my phone. Maybe if it's a free app, I'll just throw it on my phone. Or maybe you've done professional software design, but it's not public facing. As I mentioned before, it could be on a private network. Maybe you need to be on a VPN to see it or something else. Or it's not online anymore. But if that's the case, then it may be archived at web.archive.org. And I will mouse over that. That is also an active link. I'm not going to bother going to it. I think that sometimes when I go over time, it's because I follow every active link in the slides. So I'll circle back to some of these if I have time to fill at the end. But the internet archive has this wonderful service. If you go to web.archive.org, then you can search for any web URL and it's going to tell you whether other people have already archived it. Or if nobody's ever archived it, you can archive it yourself right now. And there's other edge cases where it's like I haven't done any professional work yet. I know how to code, but I just haven't had clients. But maybe I've built my own website for my blog, my band, or some other project. Or I've built a bunch of demo apps in a coding boot camp. And these can be published online. And they can be very useful in terms of having links that you can send people to for evidence of your skills. So evaluating project links, you should be prepared to do this yourself before you send it out. Because reviewers may use some of the following techniques. They may view the link in different browsers. Or they may view it on phone or tablet to test for responsive design. What I like to do sometimes is I like to just resize the screen and make it very narrow and then gradually make it wider to make sure that it looks good at every width. They'll click around the site to test its functionality, see what it does. If it's something you can log on to or make a test account, they may make an account with it and see what it put it through its bases. If there's some kind of an e-commerce functionality, they might even buy a product from you or from your employer. And they may validate the HTML or CSS to make sure that you did a good job with that. You've got good HTML. And they may use browser plugins. We've got a lot of these, which are kind of like a little magic magnifying glass. You kind of look under the skin of the site and see what text stack is used, or at least make a educated guess as to what the text stack is. It's certainly not always right. And they may also test accessibility. Sorry, I had focused on the wrong thing when I clicked. They may also test accessibility for WCAG, for 508 compliance and color contrast, navigability with text-to-speech, JAWS, or NVDA, voiceover on the Mac, orka on Linux, if anybody uses that. So all of these things are definitely things that you want to test yourself before you send it out, especially if you know that the job description is going to require any of this stuff. If it requires responsive design, if it requires accessibility, you want to make extra effort to test those things before you link to it and send it out for your potential future employers to evaluate. Now let's take a look at your code samples. Let's boost your code samples. What is a code sample? Now hiring managers don't expect you to share secret stuff. This is a common misconception. People will come to us and they'll say, I can't share our code sample. All of my code is proprietary. And I can say, we get that. We don't want you to share any of that stuff. And if you did share it, we would send it back, because we can't show it to our clients. They don't want to see something that you're not supposed to share. That is actually a red flag. They won't hire you. But that is why they do expect you to provide public code samples that are released under an open source license, such as the new GPL or the MIT license, BSD license, Apache license, there's a million of them. Or just in the public domain, maybe you didn't even bother to put a license file in the repo. Do's, write your own original code, implement custom business logic, which is like your code has to do something. Show that you can code to platform APIs. If it's a Drupal module, there's Drupal APIs. It's a WordPress plug-in or whatever. Or if it's something else, you're dealing with C-sharper.net, you're dealing with Java, and you're dealing with Python and Django. You want to code to the platform APIs. And you want to follow established standards and best practices, so that if we run code validators or sniffers or linkers on your code, it's not going to show that there's a whole bunch of errors with it. But don't turn in a plagiarized assignment. I've seen this. Sometimes I get the same thing over and over from different people. And I like a code comment at the top of it, and I'll Google it, and I'll find it somewhere else online, and somebody else's repo or whatever. It's like, OK. It does show that you understand the assignment, but it also shows that you kind of didn't put too much thought and creativity into it. You should not turn in a plagiarized assignment. It doesn't have to be from work stuff, but you should come up with something that does something. It can be simple. Don't share proprietary code that's in violation of a nondisclosure agreement. Never share code that reveals personally identifiable information. That's PII. Anything that's protected under HIPAA or FERPA or any of these privacy regulations. You definitely don't want to do that, and you don't want to share code that reveals API keys or authentication credentials that are used in a client's production environment. If you did any of these things, even if the code is absolute genius, you're going to have your hiring manager looking a scans at you and saying, I don't know if I can hire this person. They're a great coder, but I question their judgment. But let's talk about your GitHub profile. This was actually the first thing that gave us the idea when Matt Pritchard and I were talking about what we should do for the next lunch and learn. You can use GitHub pages to host a static portfolio site for free or for the price of DNS if you're using a custom domain. That can be like $10 a year. Do create a stunning GitHub profile read me. And I feel like I'm just going to do it. Let's see if I can open that in a new window. This is an article about how to create a GitHub profile read me, and it's got a video and everything. Totally great. But these things are awesome. They're new as of 2020. You have to make a special repo, which has the same name as your GitHub profile. And when you do that, it says, OK, this is a special repository. Its read me and D will appear on your profile. And then you can do all kinds of cool stuff with it. You can add all these icons or add these widgets that show your GitHub stats and do all kinds of cool tricks with it. So I'm highly recommended that you do that. And if you do, this is another great suggestion. I did this for a little while. Just make your New Year's resolution or whatever to commit at least one line of code to GitHub. It really doesn't have to be a high impact thing. But as long as you do a little bit every day. And then, of course, when you're working on something, you might be doing 50 lines of code or 100 lines of code or 500 lines of code that day or whatever. And if you do it every day for a year, then your profile contribution graph will look amazing. Now I did it for a year. It wasn't from January to January. So if I show you this, you'll see where it tapers off. But this is going to be my skyline. You guys can see this. That is my profile contribution graph from 2020. And you can grab this thing and you can move it around. It's like a virtual reality thing. And each of these corresponds to a day of the week. And the 52 weeks of the year. And you can see some days I've done a lot more work than others. It looks like a cool cityscape with all these skyscrapers in it. And I love it. But that's not I feel like I didn't probably should have probably should have used. Here we go. Is there a back button? There we go. It opened it in a new tab. So there we go. And also contribute to other open source projects on GitHub. That's for free. That's just like you get flair. If you've seen office spacing, you have to wear your pieces of flair. But you'll get these cool logos and icons and stuff in your GitHub profile that show other organizations that you've contributed to their software. And that's great. Don't do this. Don't publish a lot of unfinished projects that don't do anything. Then when the hiring manager gets there, they're going to be like, oh, you've got 350 GitHub repos, but none of them are relevant to the job. And I don't have the time of day to go clicking through them and figure out which one I'm supposed to be looking at. At least if you've got 350 unfinished things, then at least just pin a couple of good ones in your top six there so that I know what to look at or tell me like a direct link to a specific repo that I should be looking at. Oh, that is your Laravel, or that is your symphony, or whatever it is. That goes a long way. And don't publish projects without a really good idea. It's OK. It's going to be like, oh, man, this is like NPM or Yarn or something. I'm going to try and spin it up. Oh, it's throwing errors. It's the wrong version of this. It's old, it's obsolete. It's not going to start. I don't know what to do. It's great to have all of your project dependencies bundled if you can with Docker so that you've actually pinned the version of everything. Using something like Lando or DDEV or Doxel or just using Docker Compose, I highly recommend you do that with your Git repos. But if you don't do that, then at least do me the favor of publishing a read me that says how to start, how to build it and start it, and what the dependencies are. If it depends on some weird version of Ruby, that's an old version. And I'm going to need to try and figure that out. Let me know. Don't leave it to me to figure it out. I'm not going to spend more than a half an hour trying to get your program to run. And if it doesn't run, I'm not going to consider it a very useful. I may be able to eyeball it, but it's not the same as something that I can actually build and run that works and does something cool. Let's talk about your portfolio site. Let's boost your portfolio site. So I reused this slide from the last thing as well, but it's the Holy Grail to me is a portfolio website. It combines so much stuff. It's a lot of the same stuff that you can get in your LinkedIn and it's a lot of the same stuff that you can give me project links or demo apps or link to different GitHub repositories. You can have this all organized in your portfolio website. And let's take a look at why they're so great. We're looking for project links that show regular activity up to the present. We're not really looking for a portfolio website that you made 10 years ago that has your old sites up until 2010 or 2011, and it doesn't have anything new. That's not great. If your sites are private or if they're archived, well, if they're private, I'd like to see screenshots and I'd like to see a description of what you did for the site. Or if it's no longer online, it's great if you can link to an archive or at least have a screenshot of it and a description. Also demo apps, if you've got them, a lot of people will put these up in the early days when they first put up the portfolio website and then they kind of move down or onto a back page and they're no longer on the front page of the site. Once you've got a portfolio of actual client work, then that kind of comes center stage. What makes a bad one? Lack of project links, vague descriptions. I actually had somebody who said, I had several clients, including nonprofits. And they said this for various periods that were like every six months for several years, they said the same thing, description. So I knew that they kind of were lying about something. Also, if there's a lack of recent projects, it makes it look like your best years are behind you and you haven't really done any work lately. So it's good to keep it fresh and try to, you know, keep your saw blade sharp, keep in there. Maybe you're doing more of something else nowadays, you're doing more project managing, you're not doing as much coding. I mean, that's fair. Or if there's gaps in your resume for some other reason, you went back to college or something, you know, like I don't know, could be anything, but those things don't necessarily work against you, but it is great. Like the best candidates are the ones that have like a sort of upward career trajectory. When they come to me, it's like, okay, you did some junior stuff, you did some mid-level stuff that looks like you're ready for a senior role. You know, that's the best. I mentioned this before, but you don't need to put up a Drupal site just because you're looking for a job. You can use a static site. And we call this now the buzzword is jam stack. This is for JavaScript APIs, mark down is the original acronym for jam stack. But the term has come to encompass a lot of different tools that are sort of static site generators that might hook up to a data source, whether it's a RESTful API or a GraphQL API or something like that. Or in some cases it hooks up to a database, but then it just generates a static site to a special directory. And then you can just take the static HTML and CSS and JavaScript that's made by the generator and you can host it somewhere. And literally you can host things on GitHub pages or Netlify for free forever until the company goes out of business. The only caveat with Netlify and GitHub pages is that if you want it to be at your domain, like my site is at hotwebmatter.com, then if you want it to be at your domain then you have to pay for domain registration. And I'm not sure if GitHub offers DNS, but Netlify does. It's accredited DNS registrar. It's accredited by ICANN, the Internet Corporation for Assign Names and Numbers. So you can buy your domain from them for like 10 or 15 bucks a year or whatever. And then you can have just a GitHub repo or GitLab or Bitbucket wherever your Git is and have it just build that site in a pipeline and spit it out on Netlify. And GitHub pages the same way. That started out with Jekyll, which is it's made out of mostly Ruby and some YAML and some JavaScript, but it's a Ruby based implementation and GitHub pages was born to support Jekyll in the first place. But you can do a lot of other things with it. There's Hugo, which is very, very popular nowadays. It's in the programming language Go, which is from Google and it has a very good reputation. I haven't used it. There's Gatsby and Next.js are React based static site generators. They are consistently in the top. In fact, the list that you're seeing here starting with Next.js, then Hugo, then Gatsby, then Jekyll, then Nuxt, which is not Next. It's sort of the view version of Next. Like Next.js goes with React and Nuxt is built on View. But these are the top six on this list of generators. And I will go ahead and click on that. This is the Jamstack website. And it explains all about what is the Jamstack? Why Jamstack? Why do you want to do it in the first place? What is it all about? But it also has this great little list of just, I mean, you can see the 333. There's 333 different static site generators here. You can pick your favorite language if you want it to be in C++, C-sharp. If you code in F-sharp, I have not. All these things are in here and there's static site generators built in. Look, Perl, Perl is still around. Awesome. I used to do Perl back in the 90s. So this is worth taking a look at and there is a link to it in the presentation. I'm going to exit full screen so I can close the tab and then I'm going to go back into full screen. Highly recommended that you use one of these static site generators to make a portfolio website. And there are tons of open source templates out there. If you just Google for it, just ask for whatever platform you've picked. You want to do Gatsby or you want to do Jekyll or whatever. And you pick one out and then you're going to Google for portfolio templates and there are a million of them. And in fact, my own website, I used an open source Jekyll template, which occasionally sometimes a candidate will come to me and I'll see that come back to me in the wild. But I also made sure that as an open source software user and advocate, I also, when I made changes that improved that template, I contributed them back upstream and I have contributed several times to that template and that's reflected in my GitHub repo. So enough about static sites. Let's talk about your public profiles. I think this is the real meat of the thing, auditing your public profiles. So what's a public profile? These are your profiles on various social platforms. They're published on the public internet. They should link back to your portfolio site or contain project links. Your LinkedIn profile is the big one. It is your de facto resume. And in some cases, it's even more important than DocX or PDF or paper resume. Then if you do Drupal, and not everybody does Drupal, but a lot of people at esteem do Drupal and if you are looking for a Drupal role, very often you will not get a callback from the hiring manager if you don't have a Drupal.org profile. So everybody, if you don't have one, go get one now if you're interested in a Drupal role. Get one right away. And then whenever you encounter a problem with Drupal or a bug, use that account to go and check the issue queues and participate in the issue queues. File bug reports, see if you can make a patch and contribute the patch. If you're lucky, then your patch gets merged to the upstream developers project and then that's credited right in your profile. That's all automatic. Drupal.org is unique in the pre-software world and the way that they keep track of all of your contributions, code and community, non-code contributions are all automatically cataloged in your Drupal.org profile. So that's really great. You also can consider source code, version control services to be public profiles. You might think they're code samples, but like your GitHub account is not a code sample. And even if you have 333 repos in your GitHub profile, you may not have any code samples in there that a hiring manager is looking for something relevant. So code samples have to show that you can implement business logic by coding to APIs. So you could have a lot of repos and none of them are code samples that your future employer is looking for. And again, the big three are GitHub, GitLab and Bitbucket. I'm also including git.drupalcode.org because if you do have a Drupal.org profile, that's connected to git.drupalcode.org. And there's a way with a little bit of configuration that you can generate an SSH key and you can use that with your Git and you can helps you to grab other people's projects when you wanna test them locally and when you wanna make patches and send that back upstream. And it also helps you if you ever have your own project that you want to publish, that's gonna be that other people can, when their composer installing their Drupal project, they can composer install Drupal slash my module. That's really amazing. But let's talk about LinkedIn a little bit more. I'm gonna give credit where credit's due. It's always good not to plagiarize. And the tips below are quoted from this YouTube video which I've linked to and you can even see it on the screen if you wanna make a note of it. This guy, Bryant Tonbutter is very entertaining and he calls himself the Kim Kardashian of software developers because he has something like, I don't know, 17,000 followers on LinkedIn or something. And his recommendations are to land your first job in tech which is the hardest, you gotta get your foot in the door. Once you have experience, you'll get hired but before you have experience, and they'll be like, oh, it's an entry level role requires three years experience. Why? And I have great candidates lined up up. Oh, they went to coding boot camps and we don't wanna interview them. They don't have enough experience yet to be a junior dev. I just don't get it. But his advice is golden. He says, get to 500 plus connections. I'm not even there yet, I'm a little shy of that. He says, connect with technical recruiters including Bianca and Rachel from Esteemed. And then you can, in your profile, you set the green open to work badge. That lets everybody know that you're looking and make your headlines that are going to goose up your engagement on LinkedIn. Make sure that when people try to contact you on there, you engage with them and talk to them and connect with them if you wanna get 500 plus connections. Do look out, some people are just scamming on there or they have their own agenda and maybe you don't wanna be friends with them forever but generally speaking, LinkedIn, it's okay to befriend a lot of people and it works to your advantage. So what are some other public profiles? There's QA forums like Stack Overflow or Stack Exchange. There's Quora, which is a whole website just dedicated asking questions about absolutely anything at all and people can answer them and read each other's answers. And then there's Reddit, which is kind of a little bit more freeform and also is a little bit of a melting pot of everything that humanity has to offer. They definitely have some good tech forums. They definitely have, you know, Drupal and WordPress and other things that are well represented on their Linux, whatever things you're, you know, Mac whatever things you're into. Then the code playgrounds, as I mentioned earlier when you don't have enough code yet for it to be a full app, but you just wanna be able to show oh, I can do this cool thing with CSS or I can do this cool thing with JavaScript then code playgrounds are a great way to show these things, CodePen, JS Fiddle, JS Bin, CSS Stack despite the name, it also allows JavaScript. Code Sandbox, Glitch I think got bought by another service but it still is the same sort of thing. Also design sharing sites, which aren't really code playgrounds, they're more like portfolios of little, of just images that are screenshots of things. And very often UX specialists, UX designers will use these to show their wireframes and kind of their design process. So Behance and there are other ones. I don't really look at them too much. I'm generally, even for front end I'm generally looking for the code, but these things are good. And if I run across a candidate who has them they certainly you're not penalized for having design sharing or thumbnail sharing like that. And then also social media services. I'm throwing this in there just because if you don't make your Insta private then you run the risk that a hiring manager might look at it whether or not you really use it for work. I personally, I don't look at Facebook and Instagram unless I have no other public profiles. If I can't find GitHub, they're applying for a Drupal role they don't have a Drupal.org account. It's like I'm looking for anything that's gonna be work related. And I can't find anything about this person except for their Facebook page. Then I might hazard a look at it. And sometimes it's even got something kind of tech related in it now rarely. But just be aware that if you've got personal stuff that's really just for you and your friends or you're joking about things that might be inappropriate for work or you're tweeting about things using salty language or whatever. Then I mean, well, there's a certain amount of profanity I suppose can be excused in the modern era, but it's not your social media have anything offensive in it, right? Because these things may be evaluated by the hiring managers if they're public. They're not necessarily, I might take a look at them and if I see something that I think another hiring manager might not like I'm gonna warn you to shut it down before someone else sees it rather than saying you can't get work with esteem. But it's just good to kind of keep that stuff in mind. Now we're back to that wonderful three column. I talked about this earlier, but we're back to it. And now we're looking at it again with the benefit of hindsight. There's still a little bit more ahead but we're in the home stretch. But we're looking back at our profiles to see do they answer these questions? What have you done? What can you do? And do you give back? So for evidence of experience, ask yourself, do I describe my role at each employer? Do I discuss the tech stack and the tools used? Do I include project links if the sites are still live if they're on the public internet? Or if they're not on the public internet and they're private, do I have a screenshot and a description of what my role was in the tech stack that I used? And if the site is no longer online, do I link to an archive of it at web.archive.org? Then what can you do? Ask yourself about your evidence of skills. Are you providing evidence of skills that in a way that it's obvious to an impartial viewer, a casual viewer that, you know, can a potential employer verify your ability to implement business logic by coding to APIs? Again, business logic, that just means it does something. Coding to APIs, that just means using Drupal as my most common example. If it's for Drupal, then it should demonstrate some Drupal APIs. Like, you know, I like to see the form API. I'd like to see that you can implement a block plug-in class. I'd like to see that you understand, yeah, like class-based dependency injection and all of the things that you're gonna expect to, you know, routing or, you know, route controllers or service classes, things like this, you know? And I wanna be able to see that you know the APIs and that you can code to them. Does your public code adhere to standards and follow best practices? This includes like, is it secure? Does it sanitize inputs? It also just includes things like, are things indented properly? You can just run a linter on it. You can just have that. You can have your, you can set up your IDE, whether it's, you know, whether you're using PHP storm or VS code or whether you're just using something like VI, you know, you can set it up. So, you know, VIM certainly can be set up to automatically indent stuff for you. Or if you don't do that, you can have, you can lint it before, you can make a get hook so that you lint it before you commit it to make sure that it's all clean code. Do your code repos have a readme.md file that explains how to build the project? So frustrating when they don't. And then you're looking at a half broken project and it just doesn't work, you know? And do your code repos link to functioning demo apps in production online? And then ask yourself whether you give back. Have you made public contributions to open source code? Have you opened issue cues or filed bug reports? Have you written documentation, blog posts, tutorials, videos? All of these things are very, very valuable to establish you as not only to show your expertise in your skills, but also to sort of establish you as a thought leader, somebody who's, you know, the tech is changing all the time. New version of whatever platform comes out and we all have to learn how it works. And when we figure it out, do we rush out to tell everyone, hey, I figured it out, here's how you do it. People that can do that are prized in digital agencies because they're the people who are the senior developers who can help to onboard junior developers and help to bring people up to speed with the new technologies. And also, do you answer questions and forms? Of course, it can be just as valuable to ask smart questions or to file bug reports even if you don't solve the bug and contribute the patch. But even better if you're the person who files the bug report with the patch, you know, wow. You know, I figured it out, here's the solution for everybody else. I'm giving back to the community. These things are just priceless. It's the attitude and the mindset of somebody who's a real, somebody who is grateful to the open source community for giving us the tools that we use to make so much money and to, you know, support our livelihood. So if we've got a couple of hours to give back to it, we certainly will give back to the community. Now, speaking of the community, how can we boost our developer community? I was talking a little bit about Q and A communities. Drupal.org has the project issue queues. Stack Overflow and Stack Exchange is all the same company, but Stack Overflow is the main one and then Stack Exchange is like another 150 or more different channels for different specific special interests like the Drupal answer is Stack Exchange, which is Drupal.StackExchange.com or whatever. And WordPress development is WordPress.StackExchange. These things are super valuable to contribute to and I actually encourage everybody, especially if you work for esteemed, go ahead and make a public account with that too. That's almost as good as the Drupal.org one. And next time you got a question that you wanna bring to us in our esteemed colleagues community and you wanna bring it to Slack, post it on there first. I'll try and answer it in Slack and then I'll put the answer on the Stack Exchange so that it doesn't get erased after a month because we're still using a free Slack for our colleagues platform for the time being. We're working on something else. But that's great, right? And then also you can get points for that and people will see that activity when they come and you can link to that as one of your public profiles and your hiring manager is gonna look and see, oh, you've been asking smart questions or even better, you've been answering questions. Then Quora and Reddit, I think I've already said as much as I wanna say about those, but they're both valuable, potentially very valuable that if you're answering questions and if that's to your developer profile as well. Now, what else can you do in the developer community? You can write blog posts, documentation, tutorials. You can participate in discussions, not just Q and A forums, but sometimes just like live chats with people on platforms like Slack or Discord or Matrix or Mattermost. You can attend events physically or virtually. You can become a speaker like me today. I'm given a presentation and you can do this. You could do a lunch and learn for esteemed. If you feel like you're a subject matter expert about something, you could definitely do one of these. We'll record it, we'll put it on YouTube with your name on it and then you can link to that and say, look what I did guys and that's gonna help you get a job or you can just network with the other members. Certainly, when you go to these events, if it's like a conference or a camp that's dedicated to a specific technology, you're gonna see a lot of people there who work for the digital agencies that you might wanna work for and you get to meet them and assign a face to that name and make a connection and they'll get to meet you and think, oh, this is a person who's interesting, who's passionate about something, who I could see them being an asset to our team. That goes a long way in, who might get a job. So amplify your voice. Think about what things you've learned, this it's brand new emerging technology, the brand new version just came out, oh, there's a new bug in the very latest version of Drupal and I worked on it and I figured it out or I did something kind of crazy with Layout Builder because it's still got some rough edges and people are still trying to figure that out. I can write an article about it or if it's something else that you're an expert on, you've got your own take on agile products with continuous integration, continuous development with test-driven development. You can write an article about that and I'm not the one but talk to the other Matt, Matthew Pritchard and we can hire you, we pay people to write for our blog or if you have ever worked for a digital agency that has their own blog, a lot of them do, then if you've written an article that's on, you know, like trying to think of agencies that have blogs where I see cool articles all the time, Lullabot or Media Current, they're out there and they definitely will publish things about WordPress or Drupal that have interesting tips or interesting tutorials right on their own digital agency blog which they use to drive SEO to their site. That's, if you've got that, that shows that like you worked at a place that valued you as a contributor to their organization so much that they trust to do a written article and represent their expertise on their own domain. You know, that's great. There's also these, you know, like Medium, Hash Node, Dev.to, Ghost, their platforms, some of them are paywalled, some of them are free. They're just platforms that are tuned for you to have a personal blog that you, you know, sometimes you get it for free or if in the case of Medium or Ghost, I think you have the option of paying like five bucks or something to get a paywall on it so people have to, they only get to read a certain number of articles for free and then if they read your article, you can get tipped out after that or it's kind of a, I don't know. I think you have to, you have to get a lot of hits to make any money doing that and I personally, I'm not a big fan of paywalls, I'm a big fan of open, you know, information wants to be free kind of a hacker ethic but certainly these things are good or if you have your own personal website, now this is a little different from anything else because I didn't get into this. Hosting a real website that is gonna be like a full CMS-based website that's Drupal or WordPress or some kind of NBC, like whether that's, you know, Python and Django or Ruby on Rails or it's something like, I mentioned, I think, Java and Spring Boot NBC or, you know, there's so many different ones that actually have to have not just like a server whether it's Apache or Nginx that supports like a programming language or in the case of Java, it might be Tomcat or whatever, that's also Apache, but it's a different server, you know, and then you also have to have some kind of data store and then you, you know, it's a full server so you have to host it on something like Linode or DigitalOcean or you might use if it's Drupal or WordPress, you might use something like Pantheon or if it's Drupal, certainly, Acquia is probably the fanciest hosting of all, it comes straight from the people who build Drupal, you know, so all of these things are different choices for full hosting or you could use different, like there's these shared hosting services like DreamHost or whatever, or you could get, you know, I mean, there's so many different options. I don't want to even get into it because it'll take up a whole presentation of its own, but if you do have your own personal website that's like a full stack website of your chosen tech stack that you're trying to get hired in, then certainly if you have your own blog on there and you have really smart articles about stuff, that counts in your favor. I even count it in your favor. If it used to be online, it's not online anymore and I can find it in the web archive, that web.archive.org. And if I find old articles from like, you know, you wrote something in 2005 about Drupal, I'm like, wow, they were really passionate about this all the way back then, that counts for something. As long as you also keep your skills fresh and you're staying up to date with stuff and we can put you to work on modern things that people are building now. Or there's speaking opportunities, you know, the esteemed lunch and learn. Again, I'm not the person to talk to, but Matt Pritchard can book you an opportunity to do exactly what I'm doing today, a slideshow and a lecture and be the subject matter expert and talk to people about that. There's tons of tech conferences and camps depending on what your niche is and you can attend these things remotely, which I have done ever since the onset of the pandemic back in 2019. I've started going to so many remote events, you know, and I find that I do more traveling now than I ever did in the country. And sometimes see, I don't think I really have gone to anything overseas yet, but I'll consider that. So that pretty much wraps it up. Any questions? How's your developer reputation? Has anybody got a question for me? I'm gonna try to bring your, let me see if I can bring the questions to the front and look at the zoom thing.