Comments for Maccherone

Comment on The CoffeeScript emperor has no clothes by thomas

thomas — Fri, 03 Feb 2012 11:09:14 +0000

Hello,
I just wanted to let you know that you are most likely referring to Bob Dylan, not Dillon. Just thought its kind of an uncool mistake in your rockstar posting .Otherwise I totally agree , though I have only very limited experience with writing coffescript code.

Comment on The CoffeeScript emperor has no clothes by The CoffeeScript emperor has no clothes - when... | Javascript | Syngu

The CoffeeScript emperor has no clothes - when... | Javascript | Syngu — Fri, 03 Feb 2012 06:45:41 +0000

[...] Just because you can do something doesn’t mean you should. Leaving the parentheses out of your CoffeeScript might make your code look a bit more “natural”, but it almost always makes it less readable and often confuses the compiler. You should properly cloth your CoffeeScript function/method parameters before they go out in public. Javascript Read the original post on DZone… [...]

Comment on REST for a read-only API. I finally understand the benefit of HATEOAS. by The value of HATEOAS for a read-only REST API | Web Services | Syngu

The value of HATEOAS for a read-only REST API | Web Services | Syngu — Sun, 15 Jan 2012 06:33:56 +0000

[...] I’m neck deep in RESTful APIs. I’m in the late stages of designing the Analytics 2.0 APIs in my job as Product Owner for Analytics at Rally Software. I’m in the early stages of designing an API for the Lean Software and System’s (LSSC) Kanban Benchmarking and Research Program… and just today, I met with Steve Speicher and others from the Open Services for Lifecycle Collaboration (OSLC) to talk about joining one of the working committee designing RESTful services for data interchange. Web Services Read the original post on DZone… [...]

Comment on Top 10 questions when using Agile on hardware projects by Jean Tabaka

Jean Tabaka — Wed, 23 Nov 2011 15:42:09 +0000

Larry, this is exactly the sort of guidance I have been looking for to help me with some clients. You really clarify and simplify what I know deep in my core. I just couldn’t articulate it. AND, if I could, it wouldn’t have been in 10 very accessible steps.

Thanks for this.

Comment on Top 10 questions when using Agile on hardware projects by vadiraj

vadiraj — Tue, 02 Aug 2011 07:32:34 +0000

The article is thought provoking & close to reality. Some of the dimensions of hardware industry are excellently brought out in this discussion. The management of lead time, waiting time, shared resources, expert centers, testing will have to be figured out by the Scrum teams to bring the best out of the Agile methodology.

Comment on A “pretty” JSON encoder for ActionScript 3 (AS3) by Utku

Utku — Fri, 22 Jul 2011 22:49:23 +0000

thank you, output is much more readable.

Comment on The defect 4-step by Organizational memory definition - Topic Research, Trends and Surveys

Organizational memory definition - Topic Research, Trends and Surveys — Sat, 17 Jul 2010 04:44:19 +0000

[...] seen to that. Add our … Read More RECOMMENDED BOOKS REVIEWS AND OPINIONS The defect 4-step | Maccherone The defect 4-step is not a new dance craze. It’s a way to accomplish organizational [...]

Comment on How can an Agile team influence the quality of upstream components by Larry Maccherone

Larry Maccherone — Tue, 27 Apr 2010 22:19:29 +0000

@Jeff. I was responding to a question from an actual client who indicated that he was worried about the quality of the upstream components, so it wasn’t my thesis. So, you may be surprised to hear that I agree with your statement that the upstream code is not necessarily of lower quality. My background is with high assurance environments with safety and security concerns. Some of the process definitions I have used in those environments tend to produce higher quality (especially from a defect perspective) code than your average Agile team.

I’m not sure what you are objecting to with respect to peer review. Can you please say why you think it is “complete BS”?

You may also be surprised to hear that I also think there is no gain in trying to force Agile “religion” on a non-Agile team. In re-reading my post, I can see how you might think I was saying that especially when I said, “You don’t control their process but you may be able to influence it at the boundary between them and you.” However, it was not my intent to imply that the downstream team should try to force the upstream team to adopt Agile practices. All of my suggestions target the frequency and level of feedback that the downstream team gives to the upstream team. These things could be done even if the downstream team was not Agile. I chose these particular activities because they are requests that the non-Agile upstream team might be willing to accommodate.

I might also point out that peer review is not generally accepted as an Agile practice. Some might consider that suggestion anti-Agile. Its inclusion in my list is related to feedback and has nothing to do with Agile religious doctrine.

Comment on How can an Agile team influence the quality of upstream components by Jeff

Jeff — Tue, 27 Apr 2010 19:35:41 +0000

This is pretty much BS. Your entire thesis is predicated on the fact that the Agile team produces higher quality code than the non-agile team. This is not necessarily the case.

Your point about meeting cadence and automated testing stands.

Your point about peer review is complete BS.

I recommend focusing on the API/Interface, and not so much on trying to force the Agile ‘religion’ on the non-Agile team.

Comment on A multiple file loader for Flash/Flex in ActionScript 3 (AS3) by Larry

Larry — Wed, 08 Jul 2009 16:34:22 +0000

OK, there is a PHP anomaly where a third slash gets added as in http:///something. It’s fixed now.