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
Related
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
I can't say I'm weak in programming but I can't come up with the logic faster. I can analyse others code and get to know the logic. But I can't do it on my own. How can I improve my programming skills?
Quite a broad question but from my own, 30yr experience I can tell you there is no way around starting to
analyze existing code,
modify some things (play with it until it feels like it's your own code)
see what the changes do
develop your own ideas on how to do things faster/better/more beautiful
implement your ideas
see if it works
go on to more complex tasks
read books (very important, because many things can't just be discovered by trial'n'error)
be very passionate and determined about what you want to become reality
if you want to learn faster, then write more code
One very important item. You should have fun with what you do is always the best guarantee for success
If you fail at these items then I'm afraid you will never succeed with programming. But then maybe it's like any other field of knowledge.
I experience the same difficulties during my learning journey, too. When I complete challenge tasks I create more complex tasks for myself to see what I can do. It takes me to the next levels of solving problems.
Practice, Practice, Practice!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have applied to couple of startups and most of them are asking to solve programming challenge before they start on the interviewing candidate.
I have submitted couple of the solution and all the time getting rejected in the initial screening.
Now what i think is, they will see my coding style, algorithm and OOD concepts that i have used to solve the problem. Can you guys input more on it as what other details are taken into consideration and how can i improve my coding for getting selected.
By the way, i did all my coding in either Java/Perl.
Nice question, I am a new grad too... One thing I notice: When you do the exercise home, they expect you to use the best algorithm out there. In my opinion code modularity, even on a small function is key. Put lot effort into the code because they are not just judging you, but comparing you against other candidate. The one which seems to have put the more effort wins.
ps: Ask this question on programmers.stackexchange, you will obtain some good inputs there.
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 8 years ago.
Improve this question
I was just wondering- is there an automated way that the "report abuse" (for profane or inappropriate posts) feature works for a large website like, say, Amazon? Is it just a simple game of numbers (e.g. 100 ppl report the link so it should be taken down) or something more sophisticated?
It is a link on a website that the website-owner implemented? I don't think there is a some sort of top-down regulated method of implementing this, everyone does it's own thing. Some will be 'just simple numbers', some will be more sophisticated.
SO does both I guess: the more flags, the more a problem (spam for instance) gets attention of people who can lock, and flags of some users way heavier then others...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
We are thinking of using a Wizard pattern to help a user complete a task.
The Wizard pattern seems to solve our problem. We are also interested in what human factors research might have to say about the basic problem of a non-expert user needing to accomplish an infrequent and complicated task-–-are there other, possibly better paradigms for doing this than a wizard?
You posted this question over two years ago and no one has offered a better interaction design pattern than the wizard.
That looks like an answer to me.
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.