Comments on: Making Your Code as Beautiful as the Design Itself

By: Antone Masincup

Antone Masincup — Tue, 24 Jan 2012 12:12:06 +0000

Someone necessarily lend a hand to make severely articles I’d state. That is the very first time I frequented your web page and up to now? I amazed with the research you made to create this particular submit extraordinary. Magnificent task!

By: Calvin Murrill

Calvin Murrill — Thu, 19 May 2011 15:49:37 +0000

Hey are using WordPress for your site platform? I’m new to the blog world but I’m trying to get started and create my own. Do you need any coding knowledge to make your own blog? Any help would be really appreciated!

By: cheap printing

cheap printing — Mon, 27 Dec 2010 11:16:05 +0000

it is widely accepted that clean code is good for everyone, for developers and for those who need to edit the site and indeed for the SE’s.

By: Search Freelance Projects » Blog Archive » Making the Most Out of Unconferences

Tue, 07 Dec 2010 05:54:17 +0000

[...] Making Your Code as Beautiful as the Design Itself [...]

By: Robin

Robin — Sun, 12 Sep 2010 14:37:09 +0000

We use multi-line for CSS most of the time for legibility, but for a high traffic site where every KB counts, minifying is definitely worth doing.

By: richard

richard — Mon, 15 Mar 2010 00:12:01 +0000

I personally hate CSS code all in one line. Sure it saves on space but it’s so much clearer to have one indented line per CSS attribute, I also label sections of my CSS with labels corresponding to the HTML layout:

/*sidebar-start*/

#name {
attribute:1;
attribute:2;
attribute:3 4;
}

/*sidebar-end*/

/*footer-start*/

…etc

Another tip I always use after several headaches involving unclosed divs, is I label every closing div with what it’s closing as a comment, for example:

…

By: Belinda

Belinda — Thu, 11 Mar 2010 04:07:12 +0000

I’m not sure why I do this, but I tend to have multi line css for the majority of elements, but single line for things like link properties. I guess it’s just a habit… Weird!

By: Around the WordPress Community: CSS3 Tips and Techniques | WordCast - BBlogging news, Blogging podcasts, WordPress podcasts, WordPress plugins, WordPress themes, WordPress news

Wed, 10 Mar 2010 12:21:33 +0000

[...] Making Your Code as Beautiful as the Design Itself – FreelanceFolder – Amber Weinberg reminds us that code needs to be as beautiful as the web design you produce and gives us the reasons why. Just in case you forgot or needed a gentle reminding that code matters. [...]

By: Jorde Vorstenbosch

Jorde Vorstenbosch — Tue, 09 Mar 2010 13:57:12 +0000

I’m not saying ignore it completely, and for big teams you need some coding practices that everyone can adhere to in case someone else needs to take on your work. I’ve had that experience at first hand and know what a pain it is to take on work from someone else when everyone is doing their own thing. I’m not trying to be ignorant, and I’m not sure I was, I’m just saying I would prefer to spend my time on other things, that make users lives easier. I’d rather have a website or app that people found useful, than a website or app that was awesome code wise but nobody found useful.

@Chris, I guess I read your message the wrong way then. Because I agree with you on that, it’s the user’s experience with the application that actually counts. Not how you programmed it. Of course the way you programmed it does account for 90% on responsiveness, stability etc.

I would also love to spend time to make everything look and work as good as possible, however time = money, and money isn’t something you can endlessly spend, especially when it’s not your own money and the supplier (client) does not agree with you.

So yes the focus should be on the user experience.

@Lucideer thanks for you input, it’s just something I don’t like using because my blocks of code normally range between 25-150 lines, with exceptions both ways. (leaving comments out of it btw). And I must admit I throw in one-liners myself here and there because the readability and editbility (new word?) goes up when using them where possible, especially if you got a switch-case block with cases being particularly small.

switch{
…..case(condition){ statements; }
…..case(condition){ statements; }
…..case(condition){ statements; }
}

makes the block of code easier to read of course. Because you can easily compare them.

On a side-note: Working with someone else’s code is a pain in the *rse T-T (Which I unfortunately have to do way too much, bad written programs freak me out so much, I always end up rewriting most because it’s slow, not practical and often just plain wrong for the situation)

Kudos for you clearing a few things up Chris.

By: Chris Mahon

Chris Mahon — Tue, 09 Mar 2010 13:39:37 +0000

@jorde I’m not saying ignore it completely, and for big teams you need some coding practices that everyone can adhere to in case someone else needs to take on your work. I’ve had that experience at first hand and know what a pain it is to take on work from someone else when everyone is doing their own thing. I’m not trying to be ignorant, and I’m not sure I was, I’m just saying I would prefer to spend my time on other things, that make users lives easier. I’d rather have a website or app that people found useful, than a website or app that was awesome code wise but nobody found useful.

@amber We should be spending time on the tiny design elements because that does have an impact on the experience for every person who comes to your website whether they notice it or not (could be subliminal recognition). How you write your CSS or HTML in my opinion will not impact on the success or failure of a website though. I think if it meets the needs of the user, then how it is built becomes a bit of a mute point. I guess it depends on your target audience, but I’d rather not spend time on how my CSS or HTML looks. I’m not saying I don’t have my own system, because I do, but I don’t set myself extremely tight do’s and dont’s because I know I’ll break them when I’m pushed for time.