Poll: Do you prefer front end or back end work?
Curious if the hacker news community is more geared towards visual front end work, or back end deep in the code kind of work. If you like both equally you can vote for both or neither.
I'm specifically defining front and back end using wikipedia: "In computer science, the front end is responsible for collecting input in various forms from the user and processing it to conform to a specification the back end can use. The front end is an interface between the user and the back end. The front and back ends may be distributed amongst one or more systems." http://en.wikipedia.org/wiki/Front_and_back_ends
(
51 comments
| 43 points
| on HN
)
Don't get me wrong, a good Project that is good for the user is fun, I just hate having to backtrack and adjust for runtime issues after the code already functions on 90% of the user agents.
I much prefer backend to frontend for the projects I work on.
I am in a love affair with the weird little language that is JavaScript. I also think it is by far the best language to teach basic programming (and because of that I think JavaScript is hugely important in its own right[1]).
The amount of time it takes to whip up a five-cent program with JavaScript without even leaving my browser, heck without even leaving this tab is just astounding to me even after all these years.
One thing I noticed in my (not-very-long) career is that more than the language itself, or the "kind of work" as you put it when considering front end vs back end, is not the end-all of importance in determining the enjoyment of my work.
The tools that I use while building things in a language are what really make the work a pleasure. If I wasn't using Chrome's web developer tools I'd probably consider JavaScript to be a nightmarish corpse of a language that punishes the slightest of typos with a silent malicious grin, as code execution carries on as if A.blah = 5 and A.blsh = 5 were both equally worthy of existing to the JS compiler/interpreter. Only by the grace of tools is JavaScript tame at all. Services like BrowserStack[2] help a lot in this field too, as does StackOverflow (helps all fields and needs no introduction, though the StackOverflow JS chatroom is one of the liveliest rooms, and deserves a mention)
With the clarity of the tools for modern front-end dev, I think it's an incredibly enjoyable environment. Certainly the most pleasing one I've found.
[1] http://simonsarris.com/blog/696-the-importance-of-geocities
[2] http://www.browserstack.com/
Agreed. That's another reason why I prefer backend. The toolchains are more featuresome and mature.
I prefer doing both at the same time (separately).
Over the next 3-5 years I fully expect front-end tools to catch up to where we were in the 1990s. Which is a good thing. There may be honour and prestige to be gained from toiling in the mines of obscure incompatibilities, but there isn't much customer or social value.
For example, today I added drag + drop image upload that posts directly to S3, but not without resizing the file to maximum dimensions of 800 x 600 first, and finally kicking off a Sidekiq job to generate all of the smaller thumbnails. Hard to say whether that was more front-end or back-end code.
edit: And to add to that...browser fragmentation is still a PITA, but not nearly as bad as when I was in college and IE6 was dominant. I originally got into programming years ago because I wanted to design games, but it's only been recently that I've had a hankering to look back into it. The awesomeness at Ludum Dare has been an inspiration and I'm kind of excited at the thought of building something quirky and fun that, for the majority of people, can be experienced just as easily as any web page. What you lose in pure power and features, you gain in more universal accessibility. I even bought a book on ImpactJS the other week just to try it out...which yes, means I'll have to fork over $99 for ImpactJS, but well worth it if the programming is fruitful
For one thing I find far fewer places where I am dealing with abstraction leaks caused by sticky-taping together the vestigial organs of a document format interpreted in wildly conflicting ways.
Backend is where the client knows what she wants.
Frontend is where the client thinks he knows what his clients want.
Big difference.
Computer vision, robots, avionics, flight planners, 3D simulations, ...
From where I'm sitting, the web is a fad. (Obviously it is not, it's just how it feels to me)
Probably completely broken logic there, but my observation is that front-enders tend to be a minority on teams, and yet so much work is (looking to) shift on to the front end. It's going to be an interesting space to watch.
That is true, and if a backend programmer gets their hands on Bootstrap people probably aren't even going to notice.
Maybe the high-end front-end programmers are actually a kind of specialist role.
Consider how amazing Gmail and Google Maps were. Not so much because of the headline feature (read email! look up maps!) as their remarkable interfaces.
But for lots of stuff it's not a requirement. Do I need mousewheel-zoom support for an accounts payable report?
- The huge amount of storage space they provided - No folders, only search - No spam
Those are backend processes. I might be misremembering, but what how was the google interface significantly better or different than traditional webmail?
In terms of the application, Gmail made smooth, interactive interfaces the standard. Up until then web mail was about clicking between pages. Or, in the fanciest cases, using IFRAMEs.
I take such joy and pride in being able to build tangible tools and/or visual components in collaboration with great designers to produce work that is used and actually /seen/ and interfaced with by millions of people.
Also, tapping into my OCD side; I have a love for perfection- and I get to exhaust this love day in and day out in the everlasting X-browser css/js battle that front-end is.
With frontend work, you get to see the results right away, and interact with the user interface, and I guess that in a way it's closer to visual design part because of controlling interactions and making decisions (in some cases) about the way that users will interact with the app.
-> back end
Front End work when doing native applications.
Back End when doing browser based applications. I rather leave the pleasure of dealing with HTML/CSS/JavaScript pixel perfect UIs pain to others, when possible.
I enjoy both UI design as well as database/business logic design.
Because I can run automated tests on it.
Frontend work is notoriously hard to test.