Comments on: Limits of performance optimization http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/ Strong opinions, weakly held Wed, 22 May 2013 13:39:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: james mckay dot net » In response to criticisms of CSS pre-processors http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4597 james mckay dot net » In response to criticisms of CSS pre-processors Tue, 08 May 2012 07:04:27 +0000 http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4597 [...] are aware of what causes the most bloat (mixins), and take a little bit of care, you’ll be fine. Maintainability versus performance is a trade-off that you have to make at every level of your code, not just this one, so it’s [...] [...] are aware of what causes the most bloat (mixins), and take a little bit of care, you’ll be fine. Maintainability versus performance is a trade-off that you have to make at every level of your code, not just this one, so it’s [...]

]]> By: Nick http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4591 Nick Fri, 04 May 2012 20:12:00 +0000 http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4591 haha yep. That's what I was saying Jason. A bit of awareness of the hole you're digging for yourself. haha yep. That’s what I was saying Jason. A bit of awareness of the hole you’re digging for yourself.

]]> By: Jason Meckley http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4589 Jason Meckley Fri, 04 May 2012 12:16:00 +0000 http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4589 Jimmy's not suggesting there should be 10 layers of abstraction.  The point is to balance performance with maintainability. To far in either direction creates a problem. Jimmy’s not suggesting there should be 10 layers of abstraction.  The point is to balance performance with maintainability. To far in either direction creates a problem.

]]> By: Nick http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4586 Nick Thu, 03 May 2012 14:51:00 +0000 http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4586 Sometimes you can make beautiful code that is easy to maintain and looks great. But your data-access and network are abstracted 10 layers deep.  Try and optimise that son. Or even better - diagnose it. A bit of awareness of what is all I'm saying based on experience of facades, wrapping, controllers, wrapping god knows what with 50 database and web service calls scattered from top to bottom of the stack. Sometimes you can make beautiful code that is easy to maintain and looks great. But your data-access and network are abstracted 10 layers deep. 

Try and optimise that son. Or even better – diagnose it.

A bit of awareness of what is all I’m saying based on experience of facades, wrapping, controllers, wrapping god knows what with 50 database and web service calls scattered from top to bottom of the stack.

]]> By: Gene Hughson http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4585 Gene Hughson Thu, 03 May 2012 13:52:00 +0000 http://lostechies.com/jimmybogard/2012/05/03/limits-of-performance-optimization/#comment-4585 Bravo.  Doggedly eking out every ounce of a given QOS criteria (performance, security, etc.) without thought to cost and need is as detrimental as sloppy work.   Bravo.  Doggedly eking out every ounce of a given QOS criteria (performance, security, etc.) without thought to cost and need is as detrimental as sloppy work.  

]]>