863 reputation
310
bio website
location Guildford, United Kingdom
age
visits member for 2 years, 11 months
seen Mar 26 at 12:17

Mar
26
comment Designing application tier - what is your best practice?
@igor Not sure if we're saying the same thing here, but a service layer and application tier are not the same thing. The service layer is the public-facing API that exposes the functionality of the application tier. It exists partly to reduce chattiness between two tiers (because they may be out-of-process). If you don't have separate tiers, you don't need a service layer.
Mar
26
comment Designing application tier - what is your best practice?
@igor And, just to be clear, all of that logic is in a separate application - a different process - from the UI that may, or may not, be deployed to a separate physical machine? (I've seen people trying to introduce service layers within the same application as the UI before.)
Mar
26
comment Designing application tier - what is your best practice?
@igor Do you actually have an application tier, i.e. a separate process that contains business logic? What is your need for a service layer?
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
If your mockup is really complex, perhaps that's an argument for moving their design inside the agile process so that they are kept as simple and as close to the original problem as possible?
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
@nwinker I've worked with your second approach in the past. The problem I found was that there was a large backlog of pre-requisite work being done that was either wasted if the story was changed or never accepted, or created a pressure to accept a story because this work had been done. Does this happen with you? Like you say, Kanban might be better suited, and the more I've worked with it, the more I like it.
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
Separating stories into "Account Screen UI" and "Account Screen Dev" strikes me as a very bad idea. These aren't stories - they are tasks that are part of a story, but the story is either delivered or it isn't. A story delivers business value and what value to the customer is developing the wireframe? None at all. If you separate stories like this it makes it very difficult to prioritize them in order of business value since, as well as the issues of dependency that you mentioned, you simply cannot evaluate the value to the business of a task.
Feb
19
comment Is it fair to ask a team to start using CoffeeScript?
@YannisRizos So I'm going to add some BananaScript to the project, and Joe, the new guy, is going to use SomeMadeUpScript because he saw it once and it looked cool. Neither of us tell anyone, but it's fine because they are even easier to learn than CoffeeScript, so there will only be a small learning curve. ;-) Where do you draw the line?
Feb
19
comment Is it fair to ask a team to start using CoffeeScript?
@YannisRizos "The compiled output of CoffeeScript" is not what you're asking your fellow developers to maintain. It's the source CoffeeScript.
Oct
5
comment Automated unit testing, integration testing or acceptance testing
I'd just like to add a belated link to JB Rainsberger's Integration Tests Are A Scam. It highlights many of the reasons integration tests are a false economy.
Sep
25
comment Is agile about development or management?
@pdr Well he's definitely agile, he just doesn't follow any agile development process that we would adhere to. But perhaps it's more talking about "Agile" the noun, i.e. the process that's a bit like Scrum, that irks me most.
Sep
25
comment Is agile about development or management?
Am I the only one who doesn't think "agile" should have a capital letter? I'm not just being a grammatical pedant - it's important. Understand agility as a quality: if your team is agile, it is flexible, adaptable, methodical. I always find confusion starts when they talk about "Agile" as if it's the name of a standard pattern or process to which they must adhere.
Sep
25
comment Is agile about development or management?
Scrum is agile. With a lowercase 'a'. Agile is an adjective, not the name of a thing. Apart from that, I think this answer makes sense.
Aug
15
comment Does following TDD inevitably lead to DI?
The 'no' part being I don't think it's a direct link between TDD and DI. It's indirect via code quality. Which is splitting hairs probably, but just thought I'd point out that code quality is the thing you're aiming for, not just testability.
Aug
14
comment Function declaration as var instead of function
@Austin There's nothing wrong with a function definition within an if statement either!