When I decided to write a JavaScript game, I knew I'd need to run the same logic on the server and the browser, so Node.js was an obvious choice. It's JavaScript on the server, right? Anything I write to run in a browser will be runnable on the server as well. Easy! Well… not so much. Here's the misunderstandings and problems I faced, along with my solution.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/fwu

My current pet project uses Node, Angular and TypeScript. This is my first time working with Node or Angular and the differences in the way they approach Dependency Injection led to this post.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/fuE

Nothing that you name in coding exists in a vacuum. It will all be used and referenced in a certain way, and this should inform the names you choose. Here's some examples.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/ft1

On any project, there's a tension between writing code everyone finds easily accessible, and using more [relatively] modern techniques which make code more terse and expressive. Here's some thoughts on addressing that tension.

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/frL