Re:Common weaknesses in code
by ClayFerguson on Saturday December 10, 2016 @09:49PM
(#13149320)
This is one of those websites that drives you away immediately just because the styling and layout is so ugly that you conclude whoever is running it is like 20yrs out of date on everything. Stayed for like 4 seconds. That was all I could take.
Re:Common weaknesses in code
by ClayFerguson on Saturday December 10, 2016 @11:15PM
(#13149564)
But i'll reply to myself and admit that I don't give a damn about styling either in my own site, meta64.com, because I'm just working on back end functionality at this point. Let the hypocrisy accusations begin. I plead guilty in advance.
Re:Common weaknesses in code
by ClayFerguson on Sunday December 11, 2016 @01:14AM
(#13149843)
haha. That's hilarious. Grey background. Seriously though I'm totally focused on building a solid back-end. Front end code is solid too, but as far as styling i've just let default Google Polymer styling dominate, and it's boring. It's ok. i'm accomplishing my objectives "with flying colors" (pun intended)
Re:Common weaknesses in code
by ClayFerguson on Sunday December 11, 2016 @10:43AM
(#13151489)
Thanks for bringing that to my attention. I have minification of JS turned off right now, and it's a very big app. I'm not really trying to or expecting to get any traffic on the site yet. It's still under development.
Re:Common weaknesses in code
by junke on Sunday December 11, 2016 @01:42AM
(#13149913)
Click on development view, and then you have a tree; for example: Location, Code, Error Handling, Error Conditions, Return Values, Status Codes, Unchecked Return Value (https://cwe.mitre.org/data/definitions/252.html).
The website was amazingly confusing and discouraging. Not sure how to proceed from main page...
If you can figure it out, let me know :)
Compare it to this, for example:
https://sourcemaking.com/refactoring/smells