A Front End Engineer's Manifesto
f2em.com
A Front End Engineer's Manifesto
1–10 of 43 posts
Re: A Front End Engineer's Manifesto
#2I thought it was a blank page at first... some sort of less is more statement.
Re: A Front End Engineer's Manifesto
#3"I will continue to foster both
HEMISPHERES OF MY BRAIN"
I thought this was debunked?
Re: A Front End Engineer's Manifesto
#4He may "put the user first," but he clearly doesn't put the reader first ... ouch. oO;
Re: A Front End Engineer's Manifesto
#5"I will continue to foster both HEMISPHERES OF MY BRAIN" I thought this was debunked?
There's basically enough truth to it that you can't just refute-by-reality, but not enough to make statements like this acceptable by my standards. It's vague enough that it's not actually a useful statement for anyone taking it literally.
See: http://www.psychologytoday.com/blog/brain-myths/201206/why-t...
Re: A Front End Engineer's Manifesto
#6"I will educate my friends and family that WEB BROWSER CHOICE MATTERS"
and
"Most importantly and above all, I will put the needs of the USER FIRST over my own needs as a developer."
So please do, put the needs of your USERS first. Your users do not NEED to be educated by you. It is not your business what browser they use.
Re: A Front End Engineer's Manifesto
#7I thought it was a blank page at first... some sort of less is more statement.
You failed to interpret the page author's 100% custom scrollbar (on the left edge of the screen) as an indicator that there was more content? That's ... odd.
He clearly had your interests in mind when implementing that, since browser vendors just think about themselves with their annoying scrollbars that look the same on every page, even. Simplistic fools.
Re: A Front End Engineer's Manifesto
#8Scrolling through that was very annoying. Page up/down obviously won't move by exactly one of the "pages".
Re: A Front End Engineer's Manifesto
#9"Without JavaScript or CSS, or without mobile Webkit, my site may not look pretty but will still be functional."
There goes backbone.js and other javascript MVC patterns.
This is something I'm still unsure about.
What do (you) people think of keeping your "data out of the DOM"?
Re: A Front End Engineer's Manifesto
#10Scrolling through that was very annoying. Page up/down obviously won't move by exactly one of the "pages".
I found out that the page listens to j/k just as in Vim. However, it seems the scroll directions are inverted from Vim; j goes up and k goes down.