Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
In your practice, how do you effectively track and manage technical debt?
Is there a specific metric, like SLOC, that you use?
How do you visually display your results to stakeholders and management?
What benefits have you seen in the process?
We write story cards for technical debt. They are BLACK, with big yellow warning signs on them. Get too many on the wall, and it's REAL obvious.
Anyone who walks past can see them :)
We use #todo comments.
In Python, the epydoc tools format the #todo nicely.
We have a little code scanner that extracts the #todo comment lines. We push them into the backlog as work to be done.
I talk a little about some of the metrics used to identify technical debt in my blog entry below. Technical debt can mean much more than just code clean up items highlighted by TODO statements in code. The tracking mechanism will change depending on which risk indicator you're focused on.
http://blog.acrowire.com/technical-debt/technical-debt-part-2-identification/
There is a plug-in for Sonar that translates technical debt into $.
I haven't used it myself yet, but it looks promising.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I am new to software engineering and also I like to learn whatever new. I must be very thankful if someone help me to provide further information about How is a UI evaluated?.
Any help regarding to this matter is highly appreciated.
In common, evaluation of User Interface can be based on three common elements
• Functionality
• Aesthetics
• Performance
Functionality
Is the application usable?
Does it enable users to complete tasks?
Aesthetics
Style
How it influencing the users
How shown and presented?
How colors complement each other?
How UI elements convey their meaning?
Performance
Measured not only by speed, but also reliability.
Reliability (Even though an application looks good and feels great, crashes repeatedly, it likely won’t be very successful)
Should provide a user with full confidence.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What is considered more appropriate style of writing conditional operators?
if(1){
puts("Hello")
}
or
if(1) puts("Hello")
Similar aspects of coding style are welcome too.
That's all depends on your preference, that's why we rarely see people code in the same style.. Moreover, it depends on which programming language you're using.. IMHO, the important thing in coding is code readability and comments, so when your BOSS asks other people to help or develop your code. He /she will spend the least amount of their time to understand your code..
If you ask specifically from your example above, I would prefer the first one.. Because in my OPINION, imagining the WHOLE code, that one will give better readability. HOWEVER, some people may argue that it will spend some of your time typing those brackets over and over..
As per the PSR standards any structure must always enclose the code in parentheses.
The body of each structure MUST be enclosed by braces. This standardizes how the structures look, and reduces the likelihood of introducing errors as new lines get added to the body.
from the official website
Please have a look under control structures section http://www.php-fig.org/psr/psr-2/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
My boss does not ever want to hear the word refactoring again, because whenever he asks a person what he is working, they reply "I'm refactoring!"
I need to find alternative descriptions for refactoring that can make a manager happy. Thesaurus.com does not find anything for refactoring, any ideas what I should tell him when he asks what I am doing?
You don't even need to mention them that word. Just tell them you are working on the task at hand. As refactoring is normally an integral part of the development cycle (test - code- refactor), this is indeed (a part of the) truth.
If (s)he insists on getting more details, you can tell you are "finalizing the solution", "ensuring long term maintainability of the code", or - if (s)he fancies management speak - "leveraging the synergies within the product architecture" :-)
say that you are optimizing coherency
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
In our projects we are often asked to give ball park estimates for activities. My question does it really help in taking decisions based on the estimate.
Yes as pointed out above.
No if the client later says "Oh, but that's much more than the X days you initially estimated"
You need to be careful in explaining and agreeing on what "ballpark" really means
Yes .. it can help to give rough estimates to the client but later on these estimates can show upto +/- 50% variation.
But it can help to gauge the size of the project and roughly manday efforts
Something to add to the existing responses.
Pros:
Helpful for a teamleader to assess
the number of resources needed for a
set of activities.
Useful to assess
whether a task would fit in a pre
defined timeline
Cons:
Very rough estimate
Need to be very careful while sharing with the customer.
I often use these ballpark estimates to give a quick price quote to a client, when based on models such as WMFP or COCOMO-II they can also help me make an unbiased assessment.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Someone within my organization has started pushing for us to pilot the CMU SEI's TSP process (see website here). I have an instinctual aversion to any attempts to cure software development illnesses with alphabet soup, but I would like to know if anyone has experience with this process and can provide tangible facts.
I used to be a fan of SEI's CMM. I even read Watts Humphrey's "Managing the Software Process" book cover to cover. I haven't used TSP but I suspect it has similar strenghts and weaknesses as the other software processes.
Definitely read about it and what they claim it can do and how to implement it, but be vigilant about keeping your software process small and flexible. You need one, but be careful about taking processes from someone else.
good luck.
We've been using this process for a few months now and I'm not particularly impressed. This process is only suitable for a strict command and control style of management where programmers are essentially bean counters. Most of the good parts of this process (size estimates rather than time estimates, self reviews, detailed plans, logging time against plans, and keeping a log of defects and errors for later review) can be implemented without throwing a bunch of money at SEI.