This is what people spend thousands of hours and hundreds of thousands of dollars on. Building a goddamned new LIST site.
Sigh. There. That's your criticism. Shameful.
We put $200k into a site that sucks. Please destroy us with your criticism
61–70 of 138 posts
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#62I'm surprised no one is asking the obvious question: why does this website exist? Why do I care about lists? When would I use this site? Does the world need another Buzzfeed/Upworthy/Viralnova? Sure, as others noted, the CSS has problems, the design looks off, and the UX is potentially confusing. But I don't think your problems are technical. The problem is your concept: you built something the world doesn't need.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#63Earlier quoted context omitted.
It looks like you're a Norwegian company? Surely Norway has programmers who can handle this at equal or surpassing quality for less money? What was your rationale for outsourcing to begin with?
In Norway a dev starts at $100k a year; or you can pay roughly $250 an hour for freelancers. Labour laws in Norway are very strict, which means hiring someone is a big step. When we first started the project we didn't really foresee how big of a task it would end up as, so we went with outsourcing. If I had to do it again, I probably would have hired one in-house dev.
[deleted]
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#641. Maybe the lists themselves should be ranked. I'd like to downvote "top 8 tracks in Mario Kart."
2. The 3-panel header interferes with swipe gestures for page navigation, like, a lot. Try not to break common interactions like that.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#65Earlier quoted context omitted.
I believe you're committing the greatest CSS Sin: Emulating the DOM structure using nesting. Here is one example: "#site-header.newheader nav>ul>li>a.buttonGreen" ... If you'd like more advice on how to fix this I have written many talks. I didn't know this was an issue until recently and now I'm slowly fixing it on my main project. I'd love your additional advice/pointers!
Of course! The idea behind using preprocessors is helping you write CSS more easily. The goal is not to write obfuscated CSS, but rather to write CSS well! What it really enables (imo) is to think of styling in an Object Oriented way. Whenever you're about to write a block of Sass think "What is this thing?". The answer is almost never a "green button" but rather "getting started button". Or something like that. It a…
To clarify, for the `.buy-button` class, is that where one should put super-specific styles like `margin-left: 12px`?
Also, is there a good place I can learn these kind of things? I'm a programmer trying to get better at CSS (SCSS now that we've setup the asset pipeline)—so far I've been reading random A List Apart and The Sass Way articles, but I feel like I could use a more holistic, in-depth understanding of CSS if there's a good book out there for that.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#66Earlier quoted context omitted.
It looks like you're a Norwegian company? Surely Norway has programmers who can handle this at equal or surpassing quality for less money? What was your rationale for outsourcing to begin with?
In Norway a dev starts at $100k a year; or you can pay roughly $250 an hour for freelancers. Labour laws in Norway are very strict, which means hiring someone is a big step. When we first started the project we didn't really foresee how big of a task it would end up as, so we went with outsourcing. If I had to do it again, I probably would have hired one in-house dev.
>In Norway a dev starts at $100k a year; or you can pay roughly $250 an hour for freelancers.
I still think you paid more than the site is worth but... you can get that kind of rate for freelancing PHP? I think I need to move to Norway.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#67Get rid of 'beta' on the site header, there is no need for that and just makes you look cheap. I also dislike ratings on 1-10 scale (instead of 1-5, for example). What's the difference between a 2 and a 3, for example, or 8 and 9? It take too much thought.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#68Earlier quoted context omitted.
Of course! The idea behind using preprocessors is helping you write CSS more easily. The goal is not to write obfuscated CSS, but rather to write CSS well! What it really enables (imo) is to think of styling in an Object Oriented way. Whenever you're about to write a block of Sass think "What is this thing?". The answer is almost never a "green button" but rather "getting started button". Or something like that. It a…
Is it advisable to just use plain old CSS these days?
Hey Id,
I'd say learn how CSS works first and really understand what it's doing. However, Sass can help you write very maintainable efficient styled code.
I will always recommend using Sass, but only if you know what CSS you're making and know that it matters what CSS is being output.
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#69Escape them inputs, dawg! www.listnerd.com/lists?letter= alert(document.cookie);
After seeing this, talking about id selectors in the css seems...
Re: We put $200k into a site that sucks. Please destroy us with your criticism
#70Earlier quoted context omitted.
Of course! The idea behind using preprocessors is helping you write CSS more easily. The goal is not to write obfuscated CSS, but rather to write CSS well! What it really enables (imo) is to think of styling in an Object Oriented way. Whenever you're about to write a block of Sass think "What is this thing?". The answer is almost never a "green button" but rather "getting started button". Or something like that. It a…
To clarify, for the `.buy-button` class, is that where one should put super-specific styles like `margin-left: 12px`? Also, is there a good place I can learn these kind of things? I'm a programmer trying to get better at CSS (SCSS now that we've setup the asset pipeline)—so far I've been reading random A List Apart and The Sass Way articles, but I feel like I could use a more holistic, in-depth understanding of CSS i…
To answer your first question, yes that is exactly where you should put your super-specific styles. You want to put your communal styles in your placeholder, styles that all types have but are different in the mixin (background color, etc) and the rest on the class itself.
The best way to get better at Sass is to follow people who are active in the community (which unfortunately is not me). Start with Chris Coyier and Hampton Catlin and work your way from there.
If you don't mind me plugging my own talks, I have a few that are really good at learning Sass:
https://speakerdeck.com/liamdanger/why-your-sass-is-bad-and-...
https://speakerdeck.com/liamdanger/what-if-css-was-object-or...