Jonathan White

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

After finishing my SWE bootcamp, I thought I knew how to work with React. Boy, was I wrong—I merely knew just enough React to barely get my foot in the door. Early on, in my first job as a React developer at a software agency, I still vividly remember getting publicly scolded on Slack by far more experienced developers when I submitted my first couple of PRs. My coworkers made it very clear that my approach to coding was more like swinging a sledgehammer at a problem when a more elegant and refined approach was needed. I’m not ashamed to admit I didn’t take nearly enough time to think about the rest of the development process... because I never had to before. These kinds of mistakes are easy ones to learn from, and I never made them again. I think it’s safe to say you’ll learn far more every month working as part of a team than you can in six months on your own. If you’re out there looking for your first job, I can’t recommend strongly enough finding other developers to work on projects with. It’s one thing to learn how to center a div; it’s another thing entirely to KNOW you’re not uncentering another one. #react #javascript #typescript #softwaredeveloper #juniordeveloper #css #centeradiv #softskills #teamskills

23

5 Comments

Does LeetCode Promote Bad Coding Practices? I’ve been using LeetCode on and off for a while, but these past two weeks have been my most consistent stretch with it. And I’ve noticed a recurring issue: LeetCode seems to prioritize space and memory optimization over writing maintainable, easily refactorable code. In my experience as a Software Engineer, memory optimization has rarely been a concern, but I’ve had to refactor and rewrite code countless times due to changing requirements. Many of the “optimal” LeetCode solutions seem like they would completely fall apart with even minor changes. Here’s my take: If these were real interview questions, I’d probably fail. And fail hard. How are we supposed to come up with the perfect algorithm under pressure, on a whiteboard, with people watching? It feels like you either know the solution or you don’t. That being said, I love how tough the questions are and how they push you through all the core concepts. It’s a real test of knowledge and problem-solving. Anyone else feel this way? I’d love to hear your thoughts. #LeetCode #Coding #SoftwareEngineering

58

18 Comments

Hey Besties! As many of you know, I've been focusing on adding TypeScript to my arsenal. CodeCrafters.io (YC S22) has been instrumental in helping me sharpen my skills and build real-world projects along the way. I'm currently working through the "Build your own HTTP server" course with TypeScript and honestly, I'm LOVING it! If that's not your area of focus, you can do these projects using 19 other languages including Rust, Go, Python, Java, and more. I take great pride in never promoting anything I don't ACTUALLY use myself or find real value in, but there's an obvious reason CodeCrafters is the #6 repo on GitHub. If, like me, you're active in your job search, it's imperative to keep building and learning along the way. I'm blessed to have a super special link that allows you to check them out FOR FREE (no credit card required), and if you decide you love it as much as I do, you'll even get an exclusive discount. Idk, feels like a win-win to me. ✨ Don't just take my word for it. Check it out for yourself here! https://lnkd.in/gk7qsPxp Pictured below - ya girl passing all her tests like a boss 😎 #tech #buildinpublic #coding #devlife #womenintech

130

43 Comments

Ever had a moment in your career that you wished you could rewind? Here's a post on a decision that haunted me for years. We needed a Backend Engineer for a big project. The budget was set at $140k. But, just as we were about to make the offer, things took a turn. Despite being able to offer the full $140k, our CTO decided to cut the offer to $120k. I knew it was below what the candidate deserved, but I went along with it. The candidate, needing the job, accepted the $120k. It felt like a win for our budget at the time. But the real cost of that decision was something I hadn't anticipated. As we worked closely, developing a new project over 2.5 years, the candidate became more than just a coworker. He became one of my closest friends. Never did his salary come up, nor did he receive the raise he deserved. The guilt of my initial complicity grew every day we worked together. On my last day at the company, our farewell conversation turned to his salary. I confessed my role in the initial lowball offer. His reaction was a mixture of disappointment and understanding. It hurt to know I had played a part in undervaluing him, not just as an engineer but as a friend. This experience taught me a crucial lesson: Don't let the short-term wins dictate long-term relationships. Integrity and fairness in hiring are not just about budgets, but about respect and decency. In the end, treat every professional decision as if it's personal. It's not just business; it's people's lives. Don't make offers you might live to regret.

1