NDepend on a Real Project (Again): Version 6's New Stuff
There's a new version of NDepend out in the wild, so I thought I'd give it a whirl on my pet object-object mapper project. Here's a quick overview of some of the new features.
Practical, Pragmatic Agile
There's a new version of NDepend out in the wild, so I thought I'd give it a whirl on my pet object-object mapper project. Here's a quick overview of some of the new features.
Design Patterns - tried-and-true solutions to common problems - have now been around long enough that many of them have very familiar names. We can use those names as part of an object-naming strategy.
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.
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.
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.