Starting on a large project, should I split it into more concise parts?
Background: Currently an intern at a company and working on repurposing older programs (still in use, but for different departments) for use in testing new hardware. The new hardware is different in terms of register layout and firmware interface from the older iterations of hardware. I have been given free reign on how to setup this project as it is to be used for the new hardware exclusively.
God Files versus Ravioli Code
Recently I asked a question about whether or not I should refactor my code. the responses I received were most definitely in the camp of going through with the refactoring due to the presence of a God File.
Does it still make sense to think about effective code on micro scale in C++?
Early in my programming career I was in love with pointer twiddling, lean code, doing everything with as little layers of abstraction as possible and so on. The code was very C like I would say, close to metal and clever.
Practices for navigating and changing “long” code files?
Many a times I have to deal with code files which are quite long – about 5 screen pages at the minimum. Almost always there is something towards the top/bottom that I need to refer when I’m at the bottom/top (respectively). It’s a mammoth overhead to constantly scroll back-n-forth between the file parts.
Is there such thing like a “refactoring/maintainability group” role in software companies?
So, I work in a company that does embedded software development, other groups focus in the core development of different products’ software and my department (which is in another geographical location) which is located at the factory has to deal with software development as well, but across all products, so that we can also fix things quicker when the lines go down due to software problems with the product.
Are CK Metrics still considered useful? Is there an open source tool to help?
Chidamber & Kemerer proposed several metrics for object oriented code. Among them, depth of inheritance tree, weighted number of methods, number of member functions, number of children, and coupling between objects. Using a base of code, they tried to correlated these metrics to the defect density and maintenance effort using covariant analysis.
Questions about identifying the components in MVC
I’m currently developing an client-server application in node.js, Express, mustache and MySQL. However, I believe this question should be mostly language and framework agnostic.
When creating a library for a simple program, what must I do to protect others from its lack of thread safety?
When creating a library for a simple program, is it more cost effective to make it thread safe or is there a way to detect the program’s use in a multithreaded program and ASSERT() or otherwise determine (preferably at compile or link time) that it may create problems.
Futures/Monads vs Events
In an application framework
when performance impact can be ignored (10-20 events per second at max),
what is more maintainable and flexible to use as a preferred medium for communication between modules – Events or Futures/Promises/Monads?
How to have a maintainable and manageable Javascript code base [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]