With the increasing popularity of structured front-end libraries (backbone, meteor, etc) this seems completely out of place?
A Proposal: Renaming Backend/Frontend to Application/UI Developers
61–70 of 77 posts
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#62Earlier quoted context omitted.
If you answer to managers and build CRUD apps to support their careers rather than your own, then you're not a professional. Pretty amazing statement from someone whose comments are otherwise among the best here on Hacker News. 1. CRUD apps run the world. They were here long before all this sexy unnecssary stuff and will be here long after these fads pass. 2. Whether you want to admit it or not, everyone answers to s…
1. CRUD apps run the world. They were here long before all this sexy unnecssary stuff and will be here long after these fads pass. Fair point. "CRUD" is a straw man. Actually, most apps should be simple. That's just good design. If CRUD is enough to solve the problem, then one shouldn't do more if it compromises simplicity or conceptual integrity. 2. Whether you want to admit it or not, everyone answers to someone. S…
> Fair point. "CRUD" is a straw man
That's not a straw man. It's not inventing a silly example and pretending that it's representative for the sake of argument. It's using negative connotations of something that is actually representative.
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#63Earlier quoted context omitted.
What is "the Douchebag Invasion"?
Douchebag Invasion: when we as a tribe lost the high-autonomy blue-sky R&D environment and it became the reality for most of us to answer to clueless douchebags who lack any respect for what we do.
> Douchebag Invasion: when we as a tribe lost the high-autonomy blue-sky R&D environment and it became the reality for most of us to answer to clueless douchebags who lack any respect for what we do.
This has always been. There is no single Douchebag Invasion. It's just when it hit your particular part of the programming world.
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#64Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#65Earlier quoted context omitted.
Sorry, I don't follow.
RoR
There's still a lot of coding for that. I'm thinking a drop-in app that looks at a database and creates list and record level editors for each table automatically. Users could still customize it from there but they'd have a good start.
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#66Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#67Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#68I personally would prefer to see this divide: - Product developer - implements the functionality, from the database to the functional UI. Lives in Ruby/Python/PHP/etc. AND Javascript - UI designer - creates and implements visual designs. Lives in Photoshop and HTML/CSS - Dev Ops - maintains the infrastructure, optimizes resources, manages deployment. Lives on the command line Of course, all these rolls have crossover…
My problem as a designer living in code is that by calling myself "UI Designer" (or "Web Designer" for that matter), I'm putting myself in the same boat as people who don't know any code (I'm basing this off of seeing what people on Dribbble's titles/"skills" are). I much prefer "UI Developer" to "Designer" because that implies I am actually able to build what I've designed while acknowledging the design/interface as…
I would take a similar stance but say that anyone who has the title "UI Desginer" or "Web Designer" should have to know HTML/CSS. If you are designing UIs for the web, HTML and CSS are your medium, Photoshop not, that is just where you formulate your ideas.
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#69Earlier quoted context omitted.
RoR
There's still a lot of coding for that. I'm thinking a drop-in app that looks at a database and creates list and record level editors for each table automatically. Users could still customize it from there but they'd have a good start.
I think it's a cool idea. So have lots of others over the decades. (From the 70's I'd bet.) In a way, RoR is just the latest wrinkle in this quest. If you can do it, you might well have something. (BTW, are you familiar with SQLAlchemy?) If you are serious, I invented a graphical interface for dynamically exploring reporting information from such an app.
Re: A Proposal: Renaming Backend/Frontend to Application/UI Developers
#70Earlier quoted context omitted.
My problem as a designer living in code is that by calling myself "UI Designer" (or "Web Designer" for that matter), I'm putting myself in the same boat as people who don't know any code (I'm basing this off of seeing what people on Dribbble's titles/"skills" are). I much prefer "UI Developer" to "Designer" because that implies I am actually able to build what I've designed while acknowledging the design/interface as…
I would take a similar stance but say that anyone who has the title "UI Desginer" or "Web Designer" should have to know HTML/CSS . If you are designing UIs for the web, HTML and CSS are your medium, Photoshop not, that is just where you formulate your ideas.
I absolutely agree with you there; but people have taken unkindly to my saying so :)