What is TypeScript and should I learn it after JavaScript?
Lots of job posts mention TypeScript. Is it a separate language I need to learn properly, or just a small addition to JavaScript?
37 questions · 0 followers
Core programming questions answered — languages, logic, debugging, data structures and problem-solving skills that transfer to any stack.
Lots of job posts mention TypeScript. Is it a separate language I need to learn properly, or just a small addition to JavaScript?
My commit history is full of 'fix', 'update' and 'asdf'. What does a useful commit message look like and does it actually matter?
I'm not good at maths and it's the main thing stopping me from starting. How much do I genuinely need for normal development work?
I'm in my thirties working in a non-technical role and want to move into tech. Is it realistic and where do I start?
Every standup I feel like the least capable person in the room and I'm sure they'll realise soon. Does this ever fade?
I keep hearing these three together and I'm not sure where one ends and the next begins. Can someone explain the split in plain terms with an example?
I have an interview loop coming up at a large company and don't know what to expect across the rounds.
I have a coding interview in a month. What should I actually spend that month on to maximise my chances?
I've been told to always use === but I don't understand what actually differs and when == would be wrong.
I've read a dozen definitions and they all say 'application programming interface' as if that clears anything up. What is an API actually doing, in normal language?
I'm told to build projects but every idea I have is either a to-do list clone or something wildly beyond my ability. How do I find the right-sized idea?
Self-taught developer here building working apps without ever formally studying DSA. Is it a real gap or just interview theatre?
The two most recommended first languages. I don't have a specific goal beyond 'get into tech'. How do I break the tie?
I hit these constantly and my approach is basically random edits until it works. What's a systematic way to read and fix JavaScript errors?
My code works but when I come back a month later I can't follow it. What are the habits that make code readable?
I pushed a change that broke production for two hours. I'm terrified. What's the right way to handle this?
I understand JavaScript in the browser. What is Node actually adding, and why would anyone choose it over Python or Java for a backend?
I've been building projects and just saving folders with names like project-final-v3. Every job asks for Git. What problem does it solve that folders don't?
I know JavaScript well and need to pick up Python for a project. What's the fastest sensible way when the fundamentals already exist?
My styles just aren't applying and I've wasted an hour. Is there a standard checklist for debugging CSS that isn't showing up?