Astarin
New Member
Hi all,
Something has been bugging me for a while, and I'm wondering what opinion other designer/developers have on it, especially those who freelance.
I work in a small company right now and we do a lot of media work, graphic design, web, animation, photography, all sorts of stuff. My experience on the web side of stuff is making me think of the views that the company has which I don't agree with sometimes.
I'm a designer, I do HTML, CSS, bits of Javascript. But I'm also an animator and use some extremely complex 3D packages. I'd like to learn some more areas of coding such as PHP[color=#808080;] (We use .NET at the office though, I don't know whats best personally, anyone shedding any light on differences in todays day and age would be awesome btw!)[/color] but I also don't want to spready myself too thin . One issue I have is after having a good look around, it looks like if I really want to concentrate on design, I can. There seem's to be plenty of off the shelf packages for CMS systems, etc.
This got me onto the question of other things like blogs, tumblr, dribble. There is a rather large shift in using these prebuilt resources as well as off the shelf CMS packages. Where I'm at now however, there seems to be a constant reinvention of the wheel. Instead of using something that has already been made, instead of using a proven blog creation CMS we instead make the CMS for our own blog then get bitten for not having all the features of something that other free resources have. We also make a whole CMS for smaller websites sometimes, with the same occasional bite. It seems like such a waste of time when there are so many features out there that dont require bespoke creation. I fully understand that you can target the needs of the client so you dont force feed them all sorts of widgets and things they may not want. But I simply cant help it feels like time wasted sometimes and opportunities missed.
I'd be intrigued to know how people go about this in the design world, probably from both designer and developer perspectives. I guess you could say taking away the development of the back end is taking away the developers job almost. But if you don't land that job because its going to cost 10 grand to make a system thats already been made then its the same problem?
Thanks
Something has been bugging me for a while, and I'm wondering what opinion other designer/developers have on it, especially those who freelance.
I work in a small company right now and we do a lot of media work, graphic design, web, animation, photography, all sorts of stuff. My experience on the web side of stuff is making me think of the views that the company has which I don't agree with sometimes.
I'm a designer, I do HTML, CSS, bits of Javascript. But I'm also an animator and use some extremely complex 3D packages. I'd like to learn some more areas of coding such as PHP[color=#808080;] (We use .NET at the office though, I don't know whats best personally, anyone shedding any light on differences in todays day and age would be awesome btw!)[/color] but I also don't want to spready myself too thin . One issue I have is after having a good look around, it looks like if I really want to concentrate on design, I can. There seem's to be plenty of off the shelf packages for CMS systems, etc.
This got me onto the question of other things like blogs, tumblr, dribble. There is a rather large shift in using these prebuilt resources as well as off the shelf CMS packages. Where I'm at now however, there seems to be a constant reinvention of the wheel. Instead of using something that has already been made, instead of using a proven blog creation CMS we instead make the CMS for our own blog then get bitten for not having all the features of something that other free resources have. We also make a whole CMS for smaller websites sometimes, with the same occasional bite. It seems like such a waste of time when there are so many features out there that dont require bespoke creation. I fully understand that you can target the needs of the client so you dont force feed them all sorts of widgets and things they may not want. But I simply cant help it feels like time wasted sometimes and opportunities missed.
I'd be intrigued to know how people go about this in the design world, probably from both designer and developer perspectives. I guess you could say taking away the development of the back end is taking away the developers job almost. But if you don't land that job because its going to cost 10 grand to make a system thats already been made then its the same problem?
Thanks