A printer that works after you restart it, then stops working again the next morning. A Wi-Fi connection you "fix" by toggling airplane mode, over and over, every single day. Both of these got fixed - and neither one got solved. That's the core distinction in troubleshooting: a symptom is what you can see (the printer won't print, the Wi-Fi keeps dropping). A root cause is why it keeps happening (a driver conflict, a router overheating, a setting a previous person changed and forgot about). Patching the symptom buys you time. Finding the root cause is what makes the problem stop coming back. New techs often stop at the first fix that works, because it feels like success. Experienced techs ask one more question before moving on: if I hadn't just done that, would this have happened again tomorrow? That one question is the difference between a quick patch and an actual repair - and it's exactly the mindset CompTIA A+ tests for in its hardware and software troubleshooting objectives. First 30 Days in Tech starts building that habit from lesson one, using real, low-stakes scenarios you can practice on your own device. What's something you've "fixed" more than once and never actually solved? Drop it in the comments. Join First 30 Days in Tech (free, no card required): https://www.skool.com/first-30-days-in-tech-8033

This week covered two computer-fundamentals concepts - why restarting a device clears a stuck process instead of fixing real hardware faults, and why a 500GB drive reports closer to 465GB once it's installed - plus a career note on why interviewers ask "simple" questions: to see if you can explain something clearly, not recite it from memory. Here's today's check-in, and it ties those together. Pick one of this week's two concepts - restart logic or the storage-math gap - and explain it out loud, or in a comment below, to someone with zero IT background. No jargon allowed. If you catch yourself reaching for a technical term you can't immediately unpack, that's useful information, not a failure. This is the exact skill from the interview post: interviewers (and frustrated users on a help desk call) aren't grading your vocabulary. They're grading whether you actually understand the thing well enough to make someone else understand it too. First 30 Days in Tech builds this explain-it-clearly habit from Week 1, and it's the same muscle CompTIA Tech+ and A+ Core 1 both expect you to have by exam day. Which of this week's two concepts - restart logic or the GB math - could you explain most clearly right now, no jargon allowed?

If you've interviewed for a help desk or entry-level IT role, you may have gotten a question that felt almost too basic: "Can you explain the difference between RAM and storage?" or "Walk me through what happens when you turn on a computer." It's easy to assume the interviewer is testing trivia. They're not. A basic-sounding question is really checking something else: can you explain a technical concept clearly to someone who doesn't already understand it? That is the actual job. A help desk tech spends most of the day translating technical reality into plain language for a frustrated, non-technical user. If you can't explain why a restart clears a frozen program, or why a drive reports less space than the box promised, you'll struggle to calm down a user asking that exact question in a panic. This is also why interviews don't reward memorized jargon. They reward whether you understand a concept well enough to explain it simply, in your own words, under a little pressure. That's the exact skill First 30 Days in Tech builds every week - not just learning facts, but learning to explain them - and it carries straight into CompTIA A+ Core 1, where clear technical communication is part of troubleshooting and support scenarios, not an afterthought. What's the most "basic" question you've ever been asked in an interview - and could you explain it clearly on the spot?