Comments for Caffeinated Coder

Comment on The Zen of “Go Away” Rates by Data Entry Services

Data Entry Services — Fri, 06 Nov 2009 13:14:32 +0000

I like that – go away rates! So giving over-inflated rates builds value. I try to be honest in my pricing and assessments but I can see you’re concept has value.

Comment on LINQ to NHibernate: A Vast Improvement by Oliver Mezquita

Oliver Mezquita — Tue, 03 Nov 2009 21:07:24 +0000

Very interesting. I think I’ll give it a try…

Comment on LINQ to NHibernate: A Vast Improvement by Rob Ashton

Rob Ashton — Fri, 23 Oct 2009 10:57:59 +0000

That extra join is more of a concern than you make it out to be if you’re referencing more than one property across your query – it also pulls back all the data in the select clause too!

I did a write up of this in my blog linked above entitled “Why Linq2Nhibernate is not ready for production use”

http://blog.codeofrob.com/arch.....n-use.aspx

Comment on The Zen of “Go Away” Rates by The Zen of “Go Away” Rates | Caffeinated Coder - Affordable Web Developer - Just another WordPress weblog on Affordable open source web development.

Wed, 21 Oct 2009 01:44:55 +0000

[...] Syndicated from Coder“>Russell Ball [...]

Comment on On Crimes Against Duct-Tape, Mental Masturbation, and Pretty Boy Disclaimers by On Crimes Against Duct-Tape, Mental Masturbation, and Pretty Boy … - Affordable Web Developer - Just another WordPress weblog on Affordable open source web development.

Tue, 20 Oct 2009 21:37:22 +0000

[...] Syndicated from …“>Russell Ball [...]

Comment on Should We Change the Way We Name Interfaces in .NET? by The Week in Code (XII) « Sgt. Conker

The Week in Code (XII) « Sgt. Conker — Thu, 15 Oct 2009 14:06:41 +0000

[...] Should We Change the Way We Name Interfaces in .NET? Russell Ball about dropping the I of the interface names and annotate the implementations with an Impl suffix instead. The first two comments pretty much sum up my current thoughts on this. [...]

Comment on The Not-So-Great Curly Brace-Dim Divide by zanlok

zanlok — Sat, 10 Oct 2009 07:01:11 +0000

Bullspit!

Firstly, but not most importantly, VB looks like a mess. Always has. And that is not trivial when it comes to maintainability and project longevity.

The differences are HUGE when it comes to the language features that just do not exist in VB. Yes, for many every-day app tasks, your point makes sense. However, and not to belabor the point with many examples, things like delegate handling vs. a truly strongly typed language.. there’s really not a comparison. One is for kids, and C# is for experts.

Obviously the foundation is the same, but coding style matters a lot.. that’s our mechanism, our medium, for bringing life from thought, putting ideas in motion.

Comment on The Zen of “Go Away” Rates by Troy Tuttle

Troy Tuttle — Thu, 08 Oct 2009 18:34:33 +0000

Love the project kick-off description! Seems familiar.

Comment on The Zen of “Go Away” Rates by Tweets that mention The Zen of “Go Away” Rates | Caffeinated Coder -- Topsy.com

Tweets that mention The Zen of “Go Away” Rates | Caffeinated Coder -- Topsy.com — Wed, 07 Oct 2009 13:58:39 +0000

[...] This post was mentioned on Twitter by Ville Laurikari. Ville Laurikari said: Will a "go away" estimate for project cost really make them go away? http://bit.ly/401VNg [...]

Comment on The Zen of “Go Away” Rates by Michael C. Neel

Michael C. Neel — Tue, 06 Oct 2009 15:00:09 +0000

When I worked as a consultant (solo and with a small company) we called this the “Out of bounds” effect. The client has a range in mind they expect quality work to cost – if you’re above or below this range then you’re out of bounds. Ask to little and you must not know what you are doing, or you cut corners to meet that price. Too much and you are padding the bill and charging for extra work that isn’t needed. Of course, the client isn’t really capable of making a good estimate of actual work required, so these ranges have little to do with reality, unless it’s the reality of landing the job.