• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Must Read -> Developing for the Masses - 50 Things to keep in mind.

Originally posted by: Raptor235
This is a must read page for anyone developing sites or apps for the masses, lots of great tips to keep in mind.

http://www.noyzz.com/archives/34
You're supposed to contact the mods before advertising your website in the forums.

You can be permabanned for advertising/spam and it doesn't reflect well on you or your site to ignore forum rules.
 
Sorry about that I didn't mean it in that way... I wanted to share the info to everyone and I thought this would be a good forum to do it...
 
Originally posted by: supafly
He's not trying to sell anything... unless I'm missing something.
Selling his website, trying to drum up traffic by placing an ad as a forum post.

The mods might be OK with it, but asking first is the polite thing to do.
 
Originally posted by: Raptor235
This is a must read page for anyone developing sites or apps for the masses, lots of great tips to keep in mind.


http://www.noyzz.com/archives/34

Your list is all over the map with advice. Did you rip it off a del.icio.us blog or something? It certainly reads that way.

There are some good points, but others are just confusing or wrong.

Here are the points I liked:

16. When people ask for features, get to the bottom of why they are asking for that exact thing. Solve the problem, rather than doing exactly what your asked for.
38. User Acceptance Testing (UAT) is important. Make the system suitable for the people actually using the system.
46. Morals: You have to develop a sense of morals when you build your system. It?s the user?s data; it?s not yours. Make sure they can remove themselves and their account if they want to.
50. Write simple code but keep the big picture in mind. Allways keep in mind how else you might be using the system in the future and how you should write it so it?s simple to extend it in the future.

Some points are completely nonsensical:

11. The easier the API to get in and out of, the more people will use it. There?s a long tail of smart developers. Stuff like SOAP discourages adoption. No API key = people can play with it faster; drives attention.
40. Goals skew the results. People don?t read, they cram crap in to boxes. Let people wander don?t give them tasks.

Is your list supposed to be about public web sites? Web applications? Enterprise development? Because there are different rules and guidelines to follow depending on the particular scenario.
 
Originally posted by: MrChad
Originally posted by: Raptor235
This is a must read page for anyone developing sites or apps for the masses, lots of great tips to keep in mind.


http://www.noyzz.com/archives/34

Your list is all over the map with advice. Did you rip it off a del.icio.us blog or something? It certainly reads that way.

Ya. Like this fragment "Half of his population... " - "he" is not mentioned anywhere else, so it must be ripped from somewhere.

And it should be called "developing web applications for the masses" as that's what it seems to be about.

 
There was a list floating around as a text file that people have been adding to, I've added the last couple poiints and posted it on my site... and yeah I agree those two points should be taken out.
 
Back
Top