264 reputation
28
bio website woni.at
location Austria
age 27
visits member for 3 years, 3 months
seen Oct 13 at 8:26

Jun
27
comment Who should be the architect in an agile project?
I accepted this as answer, because it showed me a bit what agile development should be and that it is not what we are practicing. The key part was that you have to welcome change. In a system where changes take too long it is not really welcomed. The main goal of agile development is good working code, not one and not the other. It is not to get user feedback. It is to understand the user feedback and craft that in the best results you are able to. The sad thing, many people think they are agile, but simply spoken, they are often not. Thanks to @RobertHarvey and Kyle Hodgson for your support.
Jun
26
comment Who should be the architect in an agile project?
I understand what you are going to tell me, but I have to agree @RobertHarvey in his concerns about some major design decisions. Splitting up a repository into two or more smaller ones, is a huge impact on workflow. There isn't the question wether I need it or not. I know I would need it, because of some reqirements, but I try to move out the decision to a later point. If such major decisions are made upfront, you might save much time.
Jun
26
comment Who should be the architect in an agile project?
@Euphoric: Feedback is hard for that kind of software, because no one would ever see it. It will always be behind the scenes. Maybe agile is definitely the wrong practice. But, wouldn't you describe "Your code is messed up.", as user feedback too? Isn't technical excellence a goal of agile development? I could put all stuff into one assembly, one class, or I could split it up from beginning, as best as I can, thats part of my continious refactoring. There wouldn't be to much more effort, done right.
Jun
26
comment Who should be the architect in an agile project?
@RobertHarvey: Yes that's our problem, software quality is no requirement for the customer (our boss), but it would be one for me. I can't convince him that there is value behind the early investions necessary for high quality software. The team is waiting for a requirement to make maintainable software. So we might have a deadlock here.
Jun
25
comment Who should be the architect in an agile project?
The problem in my opinion is the clash between "do the least necessary" against "do it the cleaner way". It feels not right for me mixing up the logic for feeding the IoC-Container with initialization infos with the logic for a hardware driver, because I know that I don't need the IoC-Container in that driver. Even if it is not intended to be used further, it is, at least for me, easier to understand what part of the programm is assigned to do what. Can you give me an example how to solve such an issue?
Jun
25
comment How to define implementation details?
but wouldn't that lead to test code duplication, testing the internal classes both as SUT and as part of public SUT?
Jun
25
comment How to define implementation details?
No, the code is used internally only.