4 ms·
Front end is harder, because people that have no knowledge about how things are created can more easily justify their decisions because of the way it looks. th
by paulhauggis 12y ago
Front end is harder, because people that have no knowledge about how things are created can more easily justify their decisions because of the way it looks.
the back end just needs to work as intended. The details can be pretty much any combination of things..as long as it works.
- mthoms 12y ago> Front end is harder .... the back end just needs to work as intended. The details can be pretty much any combination of things..as long as it works. I think I know what you're trying to say - front end work is easier to justify to a client because he/she can easily "see" what you did. But your statement that front end is "harder" and that the details of backend implementation don't matter are patently false. Let me guess, you're a fronted developer right?
- justplay 12y agoMy guess is he is backend developer.
- paulhauggis 12y agoI've done both. Front-end is much harder in my experience. "don't matter are patently false" okay. I'm going to go to my boss and ask him if I should use an array or a linked list for this part of my project. He won't care. He does care if it works and if it works well. The actual details don't really matter to him. However, if I show him an admin interface, he will have all kinds of opinions on where things should go and how they should function. Developers have much more of a say in the back-end, which makes things easier. Especially when the people making the decisions have almost no experience in the matter.
- mthoms 12y agoMaybe at the entry level but what about scaling an application that handles personal info (and credit cards) over multiple servers (just for example)? What's the most complex backend stuff you can think of? Perhaps Google or Amazon level engineering? There's simply no equivalent of that on the front end. TL;DR I'm pretty sure the majority of the PhD's at Google are not writing CSS.