Badges4-README.md-Profile VS xzntrc

It's only possible because of Shields Project, Simple Icons & beloved all Contributors. We do respect & love our all contributors.

I started on GitHub by uploading a small project (a tool that converts host-names into IPs); so I wanted to make a beautiful README profile. I looked up some examples, and I found that most of them used badges from the alexandresanlim / Badges4-README.md-Profile (a huge collection that I recommend checking out). To be honest, I didn't really like them at first, simply because they were "too pointy". So, as a respectable developer, I decided to make my own.

Don't stop! Wherever you are in your journey, keep going. If you feel like something isn't working, adjust it. If you're getting technicals, but no offers do mock technicals and study up. If you're dumped at behavioral interviews, do mock behaviorals. Hearing nothing back? It's your resume. Don't just spin your wheels and wear yourself out, think like an engineer and try something else! Learn to not fear rejection. "What if the interviewer laughs at me, and says I'm dumb for not knowing x!" Then they're an asshole and they wasted your time. The literal worst that can happen is you figure out that you don't wanna work with them. Actually, the worst that can happen is not to try in the first place. If a job says they want 5 years or less of experience then apply anyway. Job postings are a wish list. If it says they have 2000 applicants already, apply anyway. If a company looks good to you and is asking for qualifications in the vague realm of anything you've seen before, apply. Sometimes a Sr level job posting could also be filled by 3-4 Jr's but you won't know if you don't apply. Qualify and prioritize you job leads. I will spend an hour or so finding job postings, saving the links, and then ordering them by which one's I am most excited about/ think I have the best shot of getting. Then I apply until I run out of energy and usually I won't make it to the end of the list. Then the next day I'll find more postings and order them including the one's I found the day before so I am only applying to postings I am really excited about. Last thing I can think of right now off the top of my head is to max out your LinkedIn and your GitHub profile, and to make a personal website from scratch (no word press). For LinkedIn fill out all the sections, list ONLY skills relevant to your job search, spin past experience to highlight transferable skills, list your title as the title you want, list your portfolio projects and links, and for bonus points make a custom profile banner in Figma or the like instead of the generic bland whatever banners most people have. For your website, make it simple AF (single page is best IMO), have your picture, links to projects, and a SHORT bio where you basically just say "hi." You want it short because recruiters are gonna spend .5 seconds on your website and you don't wanna spend to much time building it. Its not a project, its a display case for other projects (still put the code up on GH tho). Lastly, for GitHub make your profile look nice, have a nice picture of just your face as the prof pic, list your stack (use badges for some visual flair), and pin your projects to the page as well. Stats can be a good section to include as well. Avoid walls of text, no one will read it. Don't worry a ton about the "wall of green." If you are working on your projects consistently the commits you make naturally will be enough. As a bootcamper/self-taught/straight out of college/anyone with no professional tech experience, hiring managers are going to care most about your technical interview and your projects. They don't care about your GA cert, or the Udemy course you took, or the college degree you may or may not have. They care about what you can do. So show them. If you really knock these out of the park they will CARRY you (mostly, you still need to be able to explain them, and talk about your code in a meaningful way). Not all projects need to be visually flashy, and I am a big proponent of simple is better, BUT if your project has a GUI make it look decent. At the very least it will turn off recruiters and other non-technical people (and many technical people as well for that matter) if it is clear you put no effort into the appearance of your project. I can't stress enough that by look decent I mean a single column app that doesn't break when you change the screen size and has a color scheme that is intentional. Whatever you do, be intentional about it because you will need to be able to talk fluently and concisely about your intentions in your projects. Lastly, make your README docs spectacular. Have an intro section with a picture or (better yet) a GIF of your app in action, if it needs to be installed or setup in any way have directions that are so simple it is broken down BARNEY STYLE. Have a section where you talk about your planned features, what is the minimum viable product, and your proposed timeline for the project. If you do all this and really polish your README it WILL be noticed.

I cleaned up my GitHub a bit, based on the instructor's advice, then returned back to my little OS project on the old Acer Inspire 5740 (Win7, Intel i3, 4GB). I decided to install Peppermint 10 (so fast!) after pulling everything (15MB) off the old girl and onto an external 1TB usb drive. I might make the future-upgraded Dell a server.... and run some other light Linux system.

Thanks to Anuraghazra for the GitHub Stats badge Thanks to For The Badges for the powered by badges Thanks to Alexandresanlim for the social & language badges Thanks to Ileriayo for the language, tool, & framework badges

Tech stack badge images can be find here, Skill badge

Alexandresanlim’s Repo

Hey! Sorry you can just lookup the repo name, either way here is the direct link, I've added some additional README's: https://github.com/Eccentrici/Eccentrici