11–20 of 42 posts
Business wise, it is not good. But for a better understanding of the whole system. I think it is worthy. It is especially good for DIY projects for bootstrap and experiments.
If you're working on any code that's within one tier of the HTML/CSS, you should have a basic understanding of the HTML/CSS.
That general rule applies to most things. The more understanding you have of adjacent concerns, the better you will be at your own task.
From my experience I would suggest learning html/css coding but finding a creative person to do the actual design (colors, logo, white space, typography etc etc). I really doubt that it's possible to be good at everything - but html/css is 'just' coding - design however is a completely different story.
If you are like the average geek, you can spend years reading many books on good design and you still will only create ugly, flat, boring sites. Just be aware of your limitations.
One thing that definitely can help you is to screen shot or bookmark every website that you think that is simple and nice. From those example websites, you can start designing your website.
From my experience I would suggest learning html/css coding but finding a creative person to do the actual design (colors, logo, white space, typography etc etc). I really doubt that it's possible to be good at everything - but html/css is 'just' coding - design however is a completely different story.
I second that. Learning CSS/HTML is easy for a developer, not a problem. But don't think you can draw, pick color or balance objects on a page in pleasant way. Artistic style can't be taught the same way you learn a language. If you are like the average geek, you can spend years reading many books on good design and you still will only create ugly, flat, boring sites. Just be aware of your limitations.
I'm a backend guy who runs an IT department for a top 100 e-commerce site in my day job. Knowing HTML/CSS doesn't do me any practical good there.
For my side projects, I know just enough HTML/CSS to be dangerous. (http://www.almamatersports.com is all programmed by me in a couple hundred hours this year, but has obvious visual bugs on several different browsers, some layout issues, etc, but that didn't stop it from pleasing the guy paying the bills.) For those kinds of things, knowing more at the start of the project would have saved me tons of time and gotten a better looking end result, but wouldn't have changed the clients satisfaction all that much. Then again, the gameplay is so much better this year than last for him that it's not a fair comparison, since for most sites that level of visual bugs would be unacceptable.
When I think about my day job (which is what really pays the bills), in my experience it's much harder to find top-notch back-end developers than it is to find top-notch front end guys. Yes, the very cream of both crops is hard to find, but there's a much larger number of A players in the front-end space, so I'd recommend concentrating and developing your skills on the back-end and just getting a (relatively) tiny bit of exposure to front-end development issues and hiring that expertise out.
I'm going to, as someone who cannot code, take the minority view here. You are more valuable to your company or to your clients (if you're doing freelance work) if you know systems administration in and out. Between crowdSPRING + PSD2HTML, you can get a decent implementation of a design relatively cheap. There's no way to outsource "good enough" systems administration.
I would also add JavaScript and Ajax to the necessary skill set. If you are a freelancer or job hunting, JS, HTML, and CSS increase the number of gigs that you can tackle. Even when the backend is your primary responsibility, you will often be called upon to do a quick fix in the other areas.
Farming out design is good advice, but often the HTML and CSS is not really usable, so you will need to know enough to make it work on your site.
I would image that you will find it very simple to pick up and likely very rewarding.