OneMustCode - All Comments

re: The Concept of Proof of Concept.

zxevil155 — Sat, 08 Mar 2008 09:47:52 GMT

J8lk2m r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil154 — Sat, 08 Mar 2008 07:19:44 GMT

mgRSFC r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil153 — Sat, 08 Mar 2008 04:45:59 GMT

NtNPju r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil152 — Sat, 08 Mar 2008 01:30:58 GMT

Tq4nuT r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil151 — Fri, 07 Mar 2008 22:18:08 GMT

LU7a8B r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil150 — Fri, 07 Mar 2008 19:17:54 GMT

YQUb0q r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil141 — Fri, 07 Mar 2008 01:30:51 GMT

F5a1Q2 r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil136 — Sat, 01 Mar 2008 20:53:05 GMT

ExOhi6 r u crazzy? I told u! I can't read!

re: The Concept of Proof of Concept.

zxevil135 — Fri, 29 Feb 2008 15:39:30 GMT

F9bOMS r u crazzy? I told u! I can't read!

re: Do the Right Thing (your job?)

ליאור צורף — Wed, 20 Jun 2007 09:17:18 GMT

Hi,

We are planning an event for bloggers and would like to send you an invitation.

Can you please contact me with your email address at http://blogs.microsoft.co.il/blogs/liorz/contact.aspx

Thanks,

Lior Zoref

Microsoft Israel

How do you know when you're being too blunt?

Ayende @ Blog — Sat, 13 Jan 2007 20:17:30 GMT

How do you know when you're being too blunt?

re: How do you know when you're being too blunt?

Tomer Gabelֲ — Thu, 14 Dec 2006 13:10:27 GMT

I would say that this is the sign of an inexperienced team leader. An experienced team leader would listen more than talk, participate in the argument shallowly and then make a decision. I suffer from much the same problem myself - i.e. getting into heated arguments instead of listening and settling on a decision - and I imagine it's mostly due to inexperience and not realizing the depth of the transition from "hardcode programmer" to "not just that."

re: The Concept of Proof of Concept.

Tomer Gabel — Thu, 14 Dec 2006 11:44:23 GMT

Proof of concept projects are absolutely billable to the client, and I wouldn't even dream of doing one unless I was paid for it (whether as part of a bigger project or as a separate entity).

Working under the assumption that every software project is much unlike every project done before that (different problem domain, different business requirements, different methodologies, environmental requirements etc.) it's an inevitable part of the project development process.

I totally agree with Arnon, though -- pitching the POC to the client as a risk-reducing activity is not only smart from a business perspective, it's also honest and professional. It lets you provide the client with a much more accurate risk and development schedule assessment, protected both you and the client from reckless technical decisions and also allows the user to experiment with and comment on a prototype early on.

Do the Right Thing (your job?)

OneMustCode — Fri, 01 Dec 2006 07:57:46 GMT

(following up on a follow up ) So when you do have many people working under you - you need to make a

Lots and lots of Programmers

OneMustCode — Fri, 24 Nov 2006 09:23:02 GMT

(following up on a previous post ) So when I did have only two developers on my team I was a coder like