• 1 Post
  • 239 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle
  • Yeah, absolutely agreed.

    Btw, you probably already know this, but if you don’t. The later versions of Node can run typescript natively. By “run”, I mean, it can run a subset of the language, if your project indirectly or indirectly references a file that has “decorators” or something like that, then you’ll need to use another compiler.

    ts-node or tsx are runners that I use typically if I just want to “run” something. They’re basically zero config runners and I can debug with them with VS Code.


  • I’m a former .NET dev … I stopped quite a few years ago after I joined a Bay Area company. It was quite a change. React 1 was just coming out and I used to just write bad JS on my webpages and I had to rewrite our front-end in React. Also, ES5 or 6 or whatever was getting popular and we had to transition from CoffeeScript.

    The JS world gave me whiplash after doing so many years of Enterprise .NET. The .NET tools felt so much more polished.

    The fundamentals of Node to me were different than .NET. .NET felt like it had a lot more cruft and “magic” at first. With Node it felt deceptively simpler at first. Then when the require syntax was going away and we had imports but then it wasn’t a real import. It was a TypeScript import or a webpack import that did a require behind the scenes. Then I had to understand why we used typescript but then what was the point of tsc vs babel vs webpack vs esbuild what their roles were and I kind got a bit obsessed with understanding what they did and what was happening under the hood. Then Node officially did do import and I had to understand what that was all about and how it affected our compilers or bundlers.

    Sorry I rant pointlessly. Godspeed on your journey!










  • I think they’re stupid too. Going into an interview is already stressful enough and these types of questions don’t put me into “problem solving” mode. They put me into “brain teaser” mode which is a different type of thinking for me. You know how we nailed these questions when I was in uni? We traded them after our interviews between each other and you just had to pretend you’ve never heard it before. So the main thing people were testing was whether or not the question had made it to them.

    For programming, there are so many better ways to test out of the box thinking to me … I think the “what happens when you press a letter into a web browser address bar” or something is better and at least relevant. One that I like is, “there’s an outage in production, how would you go about diagnosing it?” Then as an interviewer I’d reshape the scenario and see where they put their focus and where they give up.