Teresa Gobble

This is spot on! I know several fellow bootcamp grads who have made some of these mistakes - myself included! I love the succinct explanations for why doing these things makes you look inexperienced (or rather, outs you as such), and then how to fix it and improve. It's ok for someone to approach a career through a non-traditional path. Face it, college is not attainable for everyone. But it's not a good look to make the same mistakes over and over again, never learning from those mistakes. If you're a dev who got into this career non-traditionally, take a few minutes to watch this video. Even after spending over a year in the industry myself, I found it to contain some excellent reminders! #webdeveloper #webdevelopment #softwaredeveloper #softwaredevelopment #bootcampgrad #continuouslearning #learnfrommistakes #knowbetterdobetter

6

One thing I really love and really care about is good coding conventions. While I haven't had time to dive too deeply yet into my new coding conventions in my workplace today I have been thinking about the value of writing really good pull requests - and leaving really good PR feedback as a reviewer. I think essentially the thing is to put yourself in the other developer's shoes as much as possible. If I was reviewing a PR then what would I want there to be and what would I want it to look like? I would want to understand the purpose of the code, right? If I had someone commenting on my code, then what would I want them to do - I would went them to be kind and considerate in their comments right? I would want them to criticise my code and not me as a person. I would want them to write their feedback as kindly as possible. As a developer it is important to review your own code as possible before raising a PR anyway. It is important to review it and to test it. What else is there? What have I missed? Any other thoughts on good PR raising or feedback protocol? I think the key word here is empathy. Empathy goes the longest way in the world. Empathy doesn't end on GitHub. #pr #software #softwareengineer

15

2 Comments

💡 For all the developers out there with years of experience but feeling like they lack real, hands-on skills—this is your call to action! 💡 We’ve all been there—whether stuck in support roles, “on the bench,” or in positions where the work isn’t challenging. The truth is, time in a role doesn’t always equal growth, especially in IT, where tech evolves fast. But here’s the good news: You can break free from that trap and start building the skills that truly matter. Here’s how: Take Ownership of Your Learning: Don’t wait for the perfect project. Start learning NOW. Whether it’s new frameworks, coding challenges, or open-source projects—take control of your growth. Build While You Wait: On the bench? Turn idle time into opportunity. Pick up side projects, contribute to GitHub, or explore areas you’ve always wanted to master. Expand Your Network: Engage with professionals who are doing the work you aspire to. Networking can lead to new opportunities where you can put your skills to real use. Evaluate Your Current Role: If your current company isn’t offering the experience you need, start looking. Companies that value real skills and invest in growth are out there, and they need developers who are eager to learn and innovate. Embrace the Challenge: Getting out of your comfort zone is tough, but it’s necessary. Real experience comes from diving deep into unfamiliar territory—embrace it! Experience is valuable, but working knowledge and skills are the true currency in tech. Don’t let idle time hold you back. Start building, learning, and moving toward roles that challenge and excite you! What’s the one skill you’re excited to pick up next? #CareerGrowth, #ITSkills, #SoftwareDevelopment, #OnTheBench, #Upskilling, #TechLearning, #BreakTheCycle

10

Y'all, I had a short conversation with a developer looking fr work who is deciding whether or not to put up a photo on LinkedIn and social media in general because he's worried people will judge him because he "looks" religious. Folks, this is 2024. We know ignorance is rampant in the world today, especially on college campuses and places where people are supposedly taught critical thinking skills. Hiring managers and HR/recruitment teams, from one hiring manager to another: If you're more concerned about what's on a candidate's head than what's under it, then they're not going to want to work for you anyhow. If you're more concerned about how a candidate presents themselves, or who they love, then how they do their job, and how dedicated and talented they are- check yourself. #loveislove #pridemonth #a11y #dei #inclusive #hiring (Photo credit: Nili Auerbach)

111

18 Comments

Coding interview tip: it’s an open book test Spend a half hour compiling notes on questions tour technical interviewer might ask you before your coding interview I’ve never had an interviewer say that I can’t have my text editor open during the interview If anything, it shows that you are prepared. Developers aren’t expected to know 100% of all information off the top of their head. We are expected to be able to access that information and use it quickly. You can even write algorithm templates. Know that your interviewer might ask you a sliding window search based question? Throw a code chunk in your text file so you don’t forget it during crunch time.

21

Brace for takes: Going into 2024 the snake has eaten its tail on SPA vs MPA setups. Server side rendering is all the way back, but with JS on the front and back end. For a decade React has been positioned as library not a framework, but that opinion has flipped. I recommend learning react as a framework instead of a library. You learn it either way, but the framework perspective is more relevant to the moment. Learning to use Next.js is your best target. https://nextjs.org/learn If you look for a tutorial or course, look for something that teaches you React / Next.js / Typescript If you are looking for an environment that encompasses all three look at PayloadCMS. https://payloadcms.com/ CSS whips right now. Nesting, scroll timeline, has(), color spaces... we are having fun over here. Spend your time working on CSS and not SASS. (You could look into Tailwind to supplement your React journey)

3

Preparing to do the thing isn't doing the thing. Scheduling time to do the thing isn't doing the thing. Making a to-do list for the thing isn't doing the thing. Telling people you're going to do the thing isn't doing the thing. Messaging friends who may or may not be doing the thing isn't doing the thing. Writing a banger tweet about how you're going to do the thing isn't doing the thing. Hating on yourself for not doing the thing isn't doing the thing. Hating on other people who have done the thing isn't doing the thing. Hating on the obstacles in the way of doing the thing isn't doing the thing. Fantasizing about all of the adoration you'll receive once you do the thing isn't doing the thing. Reading about how to do the thing isn't doing the thing. Reading about how other people did the thing isn't doing the thing. Reading this essay isn't doing the thing. The only thing that is doing the thing is doing the thing. #careergrowth #productivity Source: Strangest Loop

57

24 Comments

Now that I have a pretty good understanding of React and comfortable with the JavaScript language (having coded with it for 2 years now). Any project ideas I should tackle from any experienced developers that will allow me to go DEEP in a certain concept rather than building another basic CRUD app? #suggestions #guidance #softwareengineering #softwaredevelopment #projects

A lot of people turn down offers due to compensation. That’s a fact. I didn’t make that up, it’s not a personal opinion, it’s an important part in making a decision. People want more transparency around compensation, so here is what I’ve been seeing on my end. I’ve been recruiting software engineers with 4+ years of industry experience. On average I am hearing people say they are targeting $180-220k total compensation. I have had a few outliers outside of that. I have people who request $120k and $150k. I’m not sure if those numbers are publicly listed somewhere, but on the lower end those are the two I get. 9 times out of 10, candidates will say they are looking for “the market rate”, “willing to negotiate”, “want to wait til the offer to discuss numbers”, and they will try to counter the total comp expectation question back to me. When we talk some more - they open up that they are willing to take less, that’s their IDEAL* compensation, and I always jot down the comp goal / never ask what they’re currently making. I believe current salary is irrelevant because you are taking a risk when joining a new organization, leaving your tenure, and should look for increase in your next role. I do have candidates who are my OUTLIERS - they request $300k+ with the max so far being $440k. In these situations, I used to let candidates know we probably wouldn’t be able to come close to that or compete. Lately though, I’ve been questioning that logic. I think Microsoft CAN compete, but you have to look at your package holistically. In the last year I have challenged myself personally to see… can I make more investing than my base pay? Can I beat out these Engineering salary expectations without being in the field/ making less? And if I can do it … can I share how* I’m approaching this because yes …. Base pay I don’t make 300k. No where close to that. But despite the ups and downs of the market, I’m determined to clear $300k this year. I believe I’m worth every penny and what those engineers who demand crazy numbers have taught me is …. you’re worth whatever number you want. You just need to get a little creative 🤑 Microsoft sets me up perfectly to do a few things: Receive: 50% 401k match 10% discount through ESPP HSA contribution The numbers below do not account for RSUs granted, bonus pay, Perks+ stipend, or healthcare benefits. My fidelity acct only includes 12 months of investing while at Microsoft, this doesn’t include any money outside of having my current 9-5 job. (This isn’t total savings, doesn’t include any side income, just an experiment.. is this possible?) Since I’m heavy on Microsoft stock/ refuse to sell, I am investing in 4 different categories: 1. Our competitors that pay dividends 2. Safe companies that pay dividends 3. ETFS 4. Outside of tech stocks - I like semi conductors, healthcare, defense and growth stocks

405

51 Comments

🚀 Calling all developers! I need your advice! 🚀 I’m gearing up to dive back into Full Stack Development and focus on Next.js, TypeScript, Node.js, Express.js, and TailwindCSS. With so many resources out there, I want to make sure I’m learning from the best possible (and ideally free) sources that provide comprehensive knowledge. So, I’m turning to you all for guidance! 👇 👉 Where should I start my revision? 👉 Which free resources or platforms would you recommend that have helped you master these technologies? 👉 Any tips or strategies that you’ve found especially useful? I’m all ears! Any advice or insights are highly appreciated. 🙌 #FullStackDevelopment #NextJS #TypeScript #NodeJS #ExpressJS #TailwindCSS #DeveloperCommunity #LearningJourney #WebDevelopment #FreeResources

11

For those that took a coding bootcamp and are currently experiencing issues with landing a job, here’s what helped me get a job after my bootcamp: 1. Find a role that is not only looking for juniors, but also has a tech stack that you learned in the bootcamp. 2. Once one is complete, find the Hiring Manager/Recruiter responsible for the role that you’re wanting to apply to. 3. Connect with them and establish a relationship. This is very important because speaking directly with this individual will allow you to get straight to the “meat and bones” at hand and establish whether or not you’re a good fit. 4. Afterwards, and probably the most important step, go DIRECTLY to the companies website and apply on their site. DO NOT APPLY THROUGH LINKEDIN. 5. Have a spread sheet created that tracks where you applied, the recruiter you spoke with, the date you replied, and then have 2-3 columns that track your follow-up attempts with the hiring manager regarding your application. 6. Go outside and keep doing your favorite hobbies. Hopefully one of those hobbies include building new apps with your tech stack so you remain ‘current’. There’s no point to all of this if you can’t maintain a level of mental clarity while dealing with a process that WILL include a lot of rejections. Because, if I'm being honest, the rejections do NOT end once you get a job. Your code will reject you as well, at times lmao. Cheers, and good luck!!! PS: If your bootcamp program provides a Career Advisor, or something along those lines, get with them ASAP. Shoutout Corey Bott for passing this down to me, you’re wisdom has been priceless! #Bootcamp #CodingBootcamp #SoftwareEngineer #SWE #SoftwareDeveloper #React #JavaScript

5

2 Comments

If I had taken the time to do this, I would have saved myself HUNDREDS of hours🕔... If there's ONE piece of advice I could give to aspiring developers, it's this👇: Gain career clarity BEFORE applying for jobs! What's "career clarity", you ask? It means having a CRYSTAL CLEAR vision of yourself and the job that you ACTUALLY want to do. It may slow you down for a few days to gain this clarity, but the return on these few days can be MASSIVE for your career growth. Now, you might be saying: "But I can spend that time gaining more skills or sending out more applications!" Look, I get it. Finding your first software developer job is not easy. When I was just starting out, I invested all of my time to build a diverse range of coding languages and skills. You see, I wanted to fill out that "skills" section of my resume to be "qualified" for more developer jobs. I thought that the wider I cast my net, the more job offers I would be able to land. It made sense to me at the time. Rookie mistake. I spent over 200 hours taking courses and watching videos, practicing as I went. But when I started applying for jobs and internships: ZERO RESPONSES. Tons of rejections later, I finally realized that I wanted to focus on web development. So, instead of spreading myself thin, I focused all my attention on building web projects and taking web development courses. Eventually, I started to get some responses. But by then, hundreds of hours of time and effort had already gone down the drain. If I had taken some time in the beginning to figure out this one problem, I would have saved so much time, effort, and stress. So if you're looking to break into tech and get that sweet, sweet first job offer, take your time, and gain some CAREER CLARITY.

19

🚨 Hiring a Junior Developer in 2024 🚨 Over the past 2 months I onboarded 8 bootcamp grads. Let me tell you, the job market is flooded with bootcamp grads, but there’s a big issue: many stop coding until they land a job, and their portfolios are often clones of the same bootcamp projects. What are companies really looking for? 🔍 Self-taught problem solvers who can adapt on the fly. A modern, self-built portfolio showcasing real-world solutions, not just coursework. Demonstrated experience with client projects or unique challenges they’ve overcome. It’s not about how many years you claim—it's about showing how you’ve applied your skills. Your portfolio should speak volumes about your creativity and drive.  If you’re on the job hunt, keep coding, keep learning, and build projects that make you stand out!

263

41 Comments

🔧 Developer Life Chronicles 🎨 🧑‍💻 Me: After weeks of blood, sweat, and countless cups of coffee, I proudly present to you... fully functional components! 👩‍💼 Client: This is fantastic! Now, let’s redesign everything! 😅 🧑‍💻 Me: 😐 internally screams in code 🚀 As developers, we've all been there. You pour your heart into creating a polished product, only to have the design direction do a complete 180° at the last minute. It’s part of the journey, and it keeps us on our toes (and our caffeine intake high)! Here's to adapting, innovating, and rolling with the punches. Every challenge is a chance to learn and grow. Cheers to all the developers out there who make magic happen, no matter how many times the design changes! 💪💻✨ #SoftwareEngineering

5

Good morning, LinkedIn, Sorry for the long absence but today's post is pretty big for me. I took a big step in my programming development and decided just to get out of my own way. Why recreate the wheel when it's already been made? Good Question. So, with that out the way, I recently purchased the FantaCode Melee Combat system Unity package. (Best Investment I've made so far). Simply because what was taking me weeks and months has already been done and all I have to do is just plug in some animations and viola... Action-Adventure game here we go! The combo system needed a quick tweak for the ease in and ease out of animations which was an easy fix and Athul Dilip was very responsive and helpful with creating a quick fix for the project. After watching the tutorial. Here is some quick progress. Enjoy and Thank you! #unity #unitygamedev #unity3d

55

12 Comments

The Ugly Truth: Why 95% of New Software Engineers Fail to Land Their First Job. Confession: I never walked across a stage for a college degree. Never went through a coding bootcamp, either. Yet, in three months, I had 4 interviews before finally getting hired 💻 How? By avoiding the pitfalls I'm about to share. Tired of seeing new software engineers struggle to land their first job, I want to share some insights. Here are 5 reasons why you might be struggling: 1. 😤 𝗬𝗼𝘂 𝗵𝗮𝘃𝗲 𝗮 𝗯𝗮𝗱 𝗮𝘁𝘁𝗶𝘁𝘂𝗱𝗲: — Job hunting can be soul-crushing, I get it. But letting that frustration seep into your interactions? Big mistake. Remember, you're not just being evaluated on technical merit. Employers are assessing your potential as a long-term team member. Stay positive and maintain a positive outlook throughout the whole process. 2. 🎯 𝗬𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗮𝗽𝗽𝗹𝘆 𝘁𝗼 𝗲𝗻𝗼𝘂𝗴𝗵 𝗷𝗼𝗯𝘀: — Job hunting is a numbers game. I applied to A LOT of positions before landing those 4 interviews. Set a daily application goal. Quality matters, but quantity is crucial for breaking through. You have to cast a wide net! 3. 🏳️ 𝗬𝗼𝘂 𝗴𝗶𝘃𝗲 𝘂𝗽 𝘁𝗼𝗼 𝗲𝗮𝘀𝗶𝗹𝘆: — Did you know only 2-3% of applications in our industry convert to interviews? Do the math, and adjust your expectations accordingly. View each interaction, even rejections, as valuable data points for refining your approach. Persistence is key! 4. 🔊 𝗬𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗸𝗻𝗼𝘄 𝗵𝗼𝘄 𝘁𝗼 𝗺𝗮𝗿𝗸𝗲𝘁 𝘆𝗼𝘂𝗿𝘀𝗲𝗹𝗳: — In an oversaturated junior market, standing out is non-negotiable. Your technical skills are just the baseline. I highlighted my unique business and marketing-minded approach, and also highlighted my ability to easily get along with others. What's your X-factor? 5. 🤝 𝗬𝗼𝘂 𝗱𝗼𝗻’𝘁 𝗵𝗮𝘃𝗲 𝘀𝗼𝗳𝘁 𝘀𝗸𝗶𝗹𝗹𝘀 𝗼𝗿 𝗰𝗼𝗺𝗽𝗹𝗶𝗺𝗲𝗻𝘁𝗮𝗿𝘆 𝘀𝗸𝗶𝗹𝗹𝘀: — While coding proficiency is essential, it's often not the differentiator at the entry-level. Focus on developing and showcasing skills like clear communication, teamwork, and problem-solving methodology. These can set you apart in a sea of technically competent candidates. 𝙍𝙚𝙢𝙚𝙢𝙗𝙚𝙧, 𝙣𝙤 𝙤𝙣𝙚 𝙤𝙬𝙚𝙨 𝙮𝙤𝙪 𝙖 𝙟𝙤𝙗. 𝙔𝙤𝙪'𝙫𝙚 𝙜𝙤𝙩 𝙩𝙤 𝙨𝙝𝙤𝙬 𝙩𝙝𝙚𝙢 𝙬𝙝𝙮 𝙩𝙝𝙚𝙮 𝙘𝙖𝙣'𝙩 𝙖𝙛𝙛𝙤𝙧𝙙 𝙏𝙤 𝙉𝙊𝙏 𝙝𝙞𝙧𝙚 𝙮𝙤𝙪.  So, to all the aspiring devs out there: keep pushing, keep learning, and keep believing in yourself. Your breakthrough is coming! What's been your biggest challenge in the job hunt? Drop a comment below – let's help each other overcome and make it a great year! --- #TechHiring #SoftwareEngineeringCareers #JobSearchStrategy

3

A quick list I put together of my least favorite times to be rejected: - 8 minutes after submitting - on my birthday - federal holidays - after work hours - on the weekend - ever (please hire me) #webdevelopment #jokes #softwareengineer #webdev #hireme #helpmeImpoor

10

1 Comment