Talking words into someone else's face is hard. Especially when those words are meant to describe a frustrating bug. Developers at any level, but especially juniors, often struggle to communicate clearly about their code to team members, making it hard to solve problems together. Strengthen your debugging communication skills with this handy guide!
Leigh Scherrer is a software engineer at Condé Nast: “Starting your first developer job is extremely exciting! But as with anything new, there will be things that will surprise you, and an adjustment period as you get familiar with your team, your company, and the products(s) you'll be working on.
Here are some things I wish I'd known to expect at my first (and second) engineering job, and some tips to get the most out of it.”
Have you been staring at your computer screen for 6 hours *without* fixing that pesky bug? Do you kind of want to cry? Did you maybe already cry? We've been there! STOP WHAT YOU ARE DOING RIGHT NOW and de-stress with this handy guide:
Have you ever asked a question of a friend, co-worker or teacher only to stop yourself halfway through an realize--"I got it!"
Well, there's actually a name for that in programming: Rubber Ducking. Rubber Duck debugging is a useful tactic to adopt when you’re stuck on a tricky code problem. Read more to find out how to use it!
For many bootcamp grads and self-taught programmers, the whiteboard exercise can be the most dreaded part of the interview process. Those of us lacking a computer science background can feel underprepared for this challenge and don't know how to turn it to our advantage. First, we'll learn what the whiteboard exercise really is and what to expect from it. Then, we'll break down a few strategies for you to ace this part of your interview.
Helping your fellow students learn is absolutely worth your time. It will help you gain a deeper understanding of the topic, build a strong relationship with other learners and gain the vital "peer pairing" skills that will help you excel as an engineer. So, when one of our subscribers asked for some techniques for helping other students learn, we asked Antoin Campbell a former bootcamp student, teacher and an engineer at Street Easy, to share his ideas.
You want to make a career change and become a professional dev, but there is SO much out there to learn! It's easy to get overwhelmed and feel like you'll never "catch up" to the other devs out there. But, if you build a solid foundation of some core programming skills, you can break into the tech world and land your first dev job. Let's talk about how to get started.
We've all been there: that most dreaded part of the interview, when you're asked "So, do you have any questions for me?" You freeze. "Uh...will you hire me?" Don't get caught off guard. Ask these questions to impress your interviewer and find out what you need to know before receiving and accepting an offer.
If you're looking for your first dev job, you don't have a lot (or any!) work experience. You need some side projects to show off what you can do and help you level-up your skills. Building an app from the ground up is a lot of work. It can be hard to figure out where to start. Read on to learn how to build out your very own impressive side project.
Get out there and meet some other devs by joining the #TapIntoTwitter NYC team for an informative and fun evening of discussion, refreshments and networking!
Pair programming is a popular technique in which two developers work together to ensure clean, high-quality code. Maybe you've heard of it but never put it into practice, maybe you've tried it out but you're not sure if you're doing it right, or what you're supposed to get out of it. Read on to learn what exactly pairing is, what you win when you pair and how to practice it the right way.
Edwin Lim, an experienced developer and interviewer tells you how to overcome the biggest interviewing obstacle: “team fit”:
How to present yourself as a good "fit" is a vague undertaking because interviews are inherently a people driven process that applies communication, intuition, and judgement as their primary tools.
I find the most avoidable yet very common mistake candidates make is giving disconcerting or lackluster answers about what they'd be like to work with. So, I have one essential recommendation for those interviewing.