21–30 of 43 posts
Earlier quoted context omitted.
Without knowing who this is, I can't say. I know I've only done one terrible thing as a designer, which was with a really friendly dude, I was 15 at the time and just fucked up horribly. I'm pretty sure this is the incident as I've had few other big hiccups.
How'd you fuck up?
Designers: learn programming. The programmers you'll find this way will not be worth anything more than a really inefficient way to test your designs through a compiler.
There is real value to having a skilled designer and a skilled developer, but those people are rare and you aren't going to find them reliably if you don't know anything about their fields. At best, you might randomly stumble on one. Considering that communication is far more important of a skill than most other skills, the only way to find the right people is to first get to know them as people, not as objects to plug in to a whole in your project. I talk more about this on my blog (http://moron4hire.tumblr.com/post/48619863000/hiring-is-dati...)
Both of you will be far better served by the experience. You might have an idea now that seems like it has a burning need to be developed and you don't have the time to learn on your own, but it's just not true; that's the manic tendencies inside of you talking. If you give in now, you'll be in this exact, same position in N months when the next burning-a-whole-in-your-brain project idea comes along.
By all means, continue with your project as you learn. It will probably suck, but you'll come out of the other side with more skills, ready to make the next project even better.
Nice page layout. The /create page is missing a text field to tell if my project is missing a developer or a designer.
Developers: learn Photoshop and CSS. The designers you'll find this way will not be worth anything more as designers than operators of Photoshop and CSS. Designers: learn programming. The programmers you'll find this way will not be worth anything more than a really inefficient way to test your designs through a compiler. There is real value to having a skilled designer and a skilled developer, but those people are r…
I'm slowly but surely getting better at design things but I choose to focus my energy on development rather than prettifying pixels (I say that with absolutely no intent of malice).
I agree that broadening my skills to include design would be helpful. I'd also be really great off if I learned how to treat my own ailments and fix my own car. I can't do it all though, so when I have the need, I partner with designers. I look through portfolios, gauge talent and ability, and hope for the best.
Developers: learn Photoshop and CSS. The designers you'll find this way will not be worth anything more as designers than operators of Photoshop and CSS. Designers: learn programming. The programmers you'll find this way will not be worth anything more than a really inefficient way to test your designs through a compiler. There is real value to having a skilled designer and a skilled developer, but those people are r…
While I agree with the thinking here, simply learning Photoshop and CSS doesn't make you a designer and learning programming doesn't make you a programmer. I'm a front-end dev who's more than competent in Photoshop and can write really modular, daresay good CSS but if I had to decide between using a designer or making my own design, nine times out of ten, I'm going to use someone who is, by trade, a designer and has…
Developers: learn Photoshop and CSS. The designers you'll find this way will not be worth anything more as designers than operators of Photoshop and CSS. Designers: learn programming. The programmers you'll find this way will not be worth anything more than a really inefficient way to test your designs through a compiler. There is real value to having a skilled designer and a skilled developer, but those people are r…
While I agree with the thinking here, simply learning Photoshop and CSS doesn't make you a designer and learning programming doesn't make you a programmer. I'm a front-end dev who's more than competent in Photoshop and can write really modular, daresay good CSS but if I had to decide between using a designer or making my own design, nine times out of ten, I'm going to use someone who is, by trade, a designer and has…
I don't think he said that nor suggested it. The point is being able to empathize with your "other half" (dating term!). Empathy is important and critical for the success of both the technical and interface design of any web product.
Developers: learn Photoshop and CSS. The designers you'll find this way will not be worth anything more as designers than operators of Photoshop and CSS. Designers: learn programming. The programmers you'll find this way will not be worth anything more than a really inefficient way to test your designs through a compiler. There is real value to having a skilled designer and a skilled developer, but those people are r…
Basically, my CSS and HTML sucks massive schlong. But I've gotten the front-end working prettly neatly (Batman.JS with CofeeScript) with the RESTFUL (in true meaning) API.
I want to focus on an iOS version + some additional social provider authentication while you do the front-end in terms of HTML and CSS.
It's a client-side front-end. But the templates are in HTML (HTML 5 with data attributes that is)
Sometimes it isn't about skill-set, but about Time To Launch(™)
Earlier quoted context omitted.
He was 15 - does it really matter?
"I got in over my head in deliverables" vs. "I totally flaked on talking with the client" vs. "I took his advance and blew it on hookers and blow" Yes, it matters.
That said, if it was something more malicious than what you mentioned, then it would be worth looking into.