project-management

In our company we have staging and production servers. I'm trying to have them in state 1:1 after latest release. We've got web application running on several host and many instances of it. The issue is that I am an advocate of having the same architecture (structure) of web applications on staging and production servers to easily test new features and avoid creating of new bugs with new releases. But not everyone agree with me, and for them is not a such big deal to have different connection between staging application instances. Even maybe to have more application and connections between

Are there any dangers/caveats one should be aware of when creating JavaScript namespaces? Our project is fairly expansive and we are running a lot of JavaScript files (20+, expecting more). It is impossible to have any code maintainability without using namespaces, so we are implementing them like so: var namespace1 = { doSomething: function() { ... }, doSomethingElse: function() { ... } } And then to create hierarchies, we link them like so: var globalNamespace = { functions1: namespace1, functions2: namespace2, ... } This works fine, but it is essentially a "trick" to make JS behave as if it

I'd like to use one of my Projects where everything is configured fine and how it is need to start working as a "template" for creating a new Project within eclipse with CDT. So that time for configuring and writing a working project can be safed because it was already made somewhere else. Any hints? You could always right-click the project, choose "copy" and then hit ctrl+v (command+v on mac) to paste a new copy of the project into the workspace, then delete the source files that you don't need, leaving only the project configuration. William Symionow Just some ideas: You can also use File-

I'm planning on writing a spine/backbone.js style web application which basically just transfers a large application.js file to the client's browser that communicates with the node.js backend using ajax. The problem is that I don't know how to structure such a project, since I've never seen examples of such an application. I can picture some pros and cons with different ways of doing this Keep everything in one project folder. Both the server side and client side code resides in the same folders which means they can share resources such as form input validation and language files. This seems

Closed . This question needs to be more focused . It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 3 years ago . As a developer, I sometimes come across the term 'Critical Path' in the context of development execution. From wikipedia I know it has to do with identifying the necessary tasks that must be completed in a project. Is my understanding correct? What is the best definition of Critical Path you have encountered? How would identify the Critical Path when planning a project? I'm not