Comments for Passionate Software

Comment on How Does QA Fit within Agile? by Jose Perez

Jose Perez — Fri, 08 Jun 2012 01:50:15 +0000

Thank you so much, It is a very interesting reflection.

I had never thought about a QA analyst that only defines and assists in the process

Comment on Why aren’t we a profession? by robert

robert — Sat, 09 May 2009 05:26:10 +0000

Hi Dave. I don’t necessarily think it would be “nice” to be part of a profession. There is a great degree of comfort in being able to claim “code monkey” status and just do whatever the boss says (or, whatever we assume the boss wants – I think we use that as an excuse way too much) and washing our hands of the responsibility. Taking that responsibility on is probably a good deal scarier and more demanding than the status quo.

Now you’ve got me very curious about how the various professions evolved. I wonder what sort of resistance, if any, there was to the organization of the professions and what that meant for the people and companies involved.

Comment on Why aren’t we a profession? by Dave Jones

Dave Jones — Fri, 08 May 2009 18:29:16 +0000

It would be nice, Robert. However, you need to remember that lawyers can get away with upholding standards their bosses don’t like because people are very willing to hire lawyers who insist upon upholding standards that their bosses don’t like. Do you know anyone who is willing to hire software developers who insist upon upholding standards their bosses don’t like?

Comment on 5 Reasons Standardizing Your Process is a Great Idea by DIY Projects » Blog Archive » Passionatesoftware.Com » 5 Reasons Standardizing Your Process is a …

Thu, 12 Mar 2009 16:15:35 +0000

[...] At a minimum, you’re going to have to write down what your process is and adhere to that process, which will require some level of standardization. This doesn’t mean you need to document and control every part of your development …Next Page [...]

Comment on Five Reasons Standardizing Your Process is a Terrible Idea by PassionateSoftware.com » 5 Reasons Standardizing Your Process is a Great Idea

Mon, 09 Mar 2009 14:46:07 +0000

[...] recently wrote about some reasons that standardizing your development process is a terrible idea. But I’ll admit there are a few reasons that it might be a great idea [...]

Comment on Five Reasons Standardizing Your Process is a Terrible Idea by idea negocio

idea negocio — Mon, 09 Mar 2009 09:31:57 +0000

idea negocio…

Totalmente acertado. Además, todo se basa en el concepto de las cosas, en la idea. Es fundamental que se analicen bien los pros y los contras antes de pasar a la acción. Pero una vez tomada la decisión, el método de ejecución de la idea es tan imp…

Comment on Why I’m Passionate about Software Development by Tom Smallwood

Tom Smallwood — Thu, 26 Feb 2009 16:28:56 +0000

Great editorial Robert!!! Its good to be reminded about out how close software reside to pure creativity. I really enjoyed your other posts as well!!!

tds

Comment on Fix your process, don’t manage it by What’s Buzzing? » Blog Archive » Cdi Chapter Developments | Acdis Blog

Sat, 21 Feb 2009 02:40:43 +0000

[...] PassionateSoftware.com » Fix your process, don’t manage it [...]

Comment on Fix your process, don’t manage it by robert

robert — Fri, 20 Feb 2009 17:31:06 +0000

Hey Richard, good to see you here. I updated my post a bit to make it clear that I also think the above process is too complicated and needs to be simplified.

I didn’t get into just how I would simplify this process, because I didn’t want the post to get too long, but I agree with your thoughts. Overall, I think there is no purpose in fighting over whether something is a bug or not, that you need a regular schedule with clear priorities, and that making the team big enough to get the code change “done done” would go a long way to fixing it.

Comment on Fix your process, don’t manage it by Richard Jensen

Richard Jensen — Fri, 20 Feb 2009 17:04:59 +0000

Hi, Robert–Could you describe the simplest process that could possibly work (in your opinion)? I’m seeing some (IMO) dysfunctions in the above description.
* Everything is priority 1
* Lots of hand offs with chances for mis-communication/interpretation

Thanks.