682 reputation
614
bio website zoomabug.com
location
age
visits member for 3 years, 5 months
seen Apr 6 at 3:40

Jun
20
revised Is aspect-oriented programming a misnomer?
added 462 characters in body
Jun
20
comment Is aspect-oriented programming a misnomer?
not that an unsourced Wikipedia sentence is a reliable reference, but it's certainly on par with a collection of unsourced Google results. The first sentence in the Wikipedia article on "programming paradigm" says "A programming paradigm is a fundamental style of computer programming." I believe this is completely consistent with American Heritage dictionary's definition of a paradigm.
Jun
20
revised Is aspect-oriented programming a misnomer?
Added definitions of terms for consistency
Jun
20
comment Is aspect-oriented programming a misnomer?
American Heritage dictionary defines paradigm as "A set of assumptions, concepts, values, and practices that constitutes a way of viewing reality for the community that shares them, especially in an intellectual discipline." Object-oriented programming feels clearly to me like a technique to model reality. In my coding experience, I have yet to find an applicable use case for AOP language support, and as open-minded as I see myself, at this point it appears to me an enormous leap to apply the paradigm label to aspects.
Jun
19
comment What is Object Oriented Programming ill-suited for?
I'm not sure this is a case where OOP is ill suited, but a case where one could "get by" without it.
Jun
19
comment What is Object Oriented Programming ill-suited for?
Object oriented software development does not equal inheritance. The counterexample you provided with rainbow and debt would be implemented by a good Java developer familiar with best practices of OO design and Java would likely implement these common methods with interfaces that describe the common behavior and not inheritance.
Jun
19
asked Is aspect-oriented programming a misnomer?
Jun
5
comment How can I thoroughly evaluate a prospective employer?
good point, although I can't imagine that if the other questions were well answered, that the same company would fail to recognize that "quality of life" is important to employee satisfaction resulting in higher quality of work. I suppose it couldn't hurt to ask the employees what kinds of hours they work, including how often there is "overtime" or weekend time, and how often they telecommute.
May
31
revised How can I thoroughly evaluate a prospective employer?
added 205 characters in body
May
31
revised How can I thoroughly evaluate a prospective employer?
deleted 5 characters in body
May
31
comment How can I thoroughly evaluate a prospective employer?
I like your questions very much, but I'm not sure what answers I would want to them, and even if I knew, I'm not sure they would be as important as a clearly defined and documented idea of what constitutes well-written software. The answer I'm looking for is the list of "-ilities," understable, maintainable, extendable, etc. How that's implemented will change over time, but the "ilities" should not. If the company values these, and a particular employee doesn't like it, I suppose the answer I'd like to hear is that they would patiently try to convince the employee.
May
31
awarded  Commentator
May
31
revised How can I thoroughly evaluate a prospective employer?
edited title
May
31
revised How can I thoroughly evaluate a prospective employer?
Reorganized and added a note
May
31
comment How can I thoroughly evaluate a prospective employer?
I have worked for many companies where the rosy picture painted during the interview is laughable once reality hits. I wouldn't look at it as if the interviewers were outright lying, and give them the benefit of the doubt that they may actually think they were being completely honest with you, but didn't think about things the same way. I think that's probably why it's best to make sure the questions are answered with enough detail that unless they do explicitly lie, you will have a better idea what you might be "in for." I.e., ask them to explain their branching strategy.
May
31
comment How can I thoroughly evaluate a prospective employer?
To me it's less about the specific implementations and more about the culture and how open-minded the organization is and how truly interested they are in continuous improvement of the company as well as the individuals.
May
31
comment How can I thoroughly evaluate a prospective employer?
@Aditya (+1), I agree that it needs to be done carefully, and certainly not all of the questions need to be asked to evaluate the company. Many of the questions may be rendered moot once an answer is given that indicates that a weak area. The questions can also be spread across any phone calls and then spread throughout multiple people that are spoken to at the interview. Incidentally, I am less concerned about "getting the job" unless it's a good match with my values. I think part of getting the right job is working for an open-minded employer who is also honest and forthcoming.
May
31
revised How can I thoroughly evaluate a prospective employer?
edited title
May
31
awarded  Nice Question
May
30
revised How can I thoroughly evaluate a prospective employer?
added 271 characters in body