Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@irene you’d probably have to kill about 70% of them. I am a designer as well as coder, I have worked with many designers and if they are from print, they just can not grasp the fluid nature of the web. They still think like ink on paper and it drives me fucking crazy. It takes time to explain and change there mindset, slowly but surely it sinks in. The alternative is to build a bigger wall and write NO on a piece of paper and chuck it back over.
-
Who needs a designer when you can make a motherfuckingwebsite.com, @stoeptegel?
-
@creator Dat PS tho, the size of an elephant.
-
@SSDD Hence my comment, though maybe the OP meant UX designer in the first place.
-
1. You stick to your responsiveness-framework of choice, perfectly, without exception. You add a theme for colors and fonts, but you prohibit further inline styles or overrides. You save on salaries. This is a valid option for a company with < 10 devs.
2. You write your own responsive framework, from scratch. You hire a style lead who decides on layout, css classes, browser support and technologies. This person leads a team with at least a designer, a UX/UI specialist and a CSS expert. This team maintains a versioned style guide to be used by backend/frontend devs: Your company basically develops and maintains a full bootstraplike framework — and guarantee usability and quality as if the style kit with all its components was an external product.
Anything in between these options will be a road to hell. -
@bittersweet You are not accounting for design really with this approach more ‘interior design after the house is built’ limiting the design input to purely style choices. While this would produce rapid and working solutions and the life of the dev and designer would be a piece if piss, each project would be incredibly dull and formulaic. You cant build a house without the designer (architect) pushing the envelope and dictating the concept, otherwise its just a put your lego here like the millions of wordpress shites you see littering the web.
-
@rtannerf I wasn’t referring to fads trends or the latest cool thing, good design is born out of research, target audience, company ethos, competitors etc and applying that to design development. Starting from close to the end doesn’t necessarily add value to the client. Unless you can add value its like putting a business card in the newsagent window. Good designers get this, shit designers don’t do the leg work or understand the company they are designing for. Don’t confuse good design with an arty farty thing, it’s quite insulting.
-
@rtannerf This is why I am self employed and have 15 years of satisfied and repeat clients. I do bespoke design and build. I don’t use css frameworks either. I also work as a 3rd party for design companies. I don’t tell them how to design, I turn their designs into cms driven working solutions. If you box yourself in you end up saying no more often than yes. I totally see where you are coming from, but I am up against Wordpress bandits in a lot of pitches, i don’t compete on price and the ones I lose i’m happy to lose.
-
@bittersweet I don't agree. There is a middle way.
You just need people who communicate and frigging know what they are doing.
But that being said this was achieved only coz our designer also make the CSS and part of the html. -
@Grexius I agree with some german motherfucker.
-
@freakko I'd gladly do that if you can find me an end-user who is happy running everything from the console.
My friend said an intern designed this UI for an internal site.
No. Just... no
Found something true as 1 == 1
Been looking around ways to improve devrant's user experience a little, Idk whether you guys like it or not.. ...
Design team: "Is it okay if I put this here?"
Me: "No, it's not okay if you put that there."
Design team: "Are you sure? It'd be really cool if I could put that there."
Me: "No, I will need to fuck with a lot of things if you put that there, just put it in the bootstrap columns."
Design team: "Hold on, lemme see if it's okay to put that there."
Lead-dev: "He's right, you shouldn't put that there."
Company: "We should have a meeting to discuss where the design team can and can't put things."
Lead-dev: "Just put the things in the middle and devide them in these twelve columns on seperate rows, 'kay?"
Company: "Okay, the design team will now put the thing in those things, right design team?"
Design team: "Yes, we agree to putting the thing where we should put the thing."
Me: "So where do you want the thing now?"
Design team: "I want it all the way to the right, outside of the container, that'd look cool."
Me: "Fuck you."
rant
design
disagreement
bootstrap
web