HN user

Watts

16 karma
Posts1
Comments29
View on HN

I agree. Let's be honest - it's kind of weird that we rely on a program that is really designed for editing photographs as our main tool for designing web sites. I'm all for exploring this further at least as a tool for doing layouts and design that CSS can handle. For everything else (e.g. designing icons), there are more appropriate tools.

I used this site starting around February of this year. I thought it was really helpful and I ended up losing close to 30lbs in 10 weeks because of it (I've also kept it off since then, too). It wasn't really the money that mattered - I guess I saw it as sort of a game and it was fun to try and beat the goals from week to week. Also, having my friends cheer me on helped a lot (you have to have a couple of friends sign up with you to keep you honest). Perhaps I could have done it on my own without this site but the idea really worked for me.

I have had success gaining fans for my Facebook page using Facebook ads. I targeted my ad to people who fit my niche and I gained fans fairly quickly. I also made sure to keep my fan page fairly active by posting there on a regular basis.

I don't agree with the idea that designers should just hand off mock-ups to developers and expect them to implement it properly. All of these points can be addressed by coding your own HTML, CSS, and Javascript. Developers don't have the time to worry about your grid, they have enough to do as it is. Design that stops at Photoshop is only half finished, and a web designer who doesn't have the skill to implement their work is not really a web designer at all.

When I work with developers, I just tell them to do their thing and make it work. Don't worry what it looks like - I'll do the rest. Using GitHub on our projects has made this really easy for me.

I have been doing something similar to the advice in this article and it's been working for me. I took a small hobby blog and got more serious about it, implementing these ideas as I go. So far it's going well, and while I think you can do a lot of things things at once I don't think you need to feel pressured to get it done all in one go.

This is fantastic news. I have been developing a mobile version of a web site this week and WebKit has been a dream. The BlackBerry version... not so much. It seems like WebKit is becoming the standard for mobile these days.

I like the idea as far as checking for visual inconsistencies goes, but after trying out the free account I think it's just too slow to use on a day-to-day basis. Rendering takes too long, and switching between the different browser views even takes around 5 seconds. And as someone else pointed out, it isn't useful for any real testing of Javascript etc.

In Defense of Sass 17 years ago

I've been using Sass since it came out and I love it. The author's tips are great - I came to the same conclusion myself. I think you could easily overdo nesting in Sass if you're not careful but like he mentions, it's really not necessary. It's been very handy for me on a recent (large) project - it's readability has been a great time-saver.