746 karma · joined January 29, 2013
A few thoughts on how to standardize the content;
It seems more logical to just send your date of birth as a ISO8601 string or a UTC unix timestamp, instead of all the fluff. (i would prefer the ISO8601)
Lat/Lng is an exact point, and i figure you removed a few digits to avoid showing your exact location. A geohash would be better suited to indicate a geographical area of users precision choice. Also more compact.
You are missing country - not everyone live in the US, or even in a city, a common geo indication seems more suited (again, a geohash).
All values should be describes with a standard name, not just the english name. so english: "en", german: "de", etc. Also, more compact.
And if you can use this library without understanding regex, you might be better of not using regex at all.
Regex looks complex at first glance, but with a good cheatsheet and tool you should have no problem.
http://gskinner.com/RegExr/ is a great tool for building and testing regexes.
It takes you about 3-4 seconds to change it for your entire project.
The fault is with the programmer. No one else.
Really cool. I trade in EUR though, so it would be nice with a mtgox EUR listing.
The access rights it wants to my twitter account is unacceptable though, so no chance i am going to bind my account to bitjoy.
And i find the "Not Constructive" to be exactly that.
Yes, it can be annoying when a question is closed and you really wanted to discuss it, but the rules are quite clear on what is and is not classified as "Not Constructive", and the discussion should just move to some of the discussion threads instead.
And i don't know what you interpret as negativity? I have never seen unfair or non-objective use of moderator functions?
Really, just add a paragraph or 2 on the frontpage with a "What is Vessel" heading.
DAYOFYEAR( CONVERT_TZ(my_datetime_field,'+00:00', '+02:00') )
Seems very intuitive to me.
This seems to add unnecessary complexity and overhead.
There is already plenty of build-in abstraction for date manipulation in MySQL, and you really don't want to be dependent on any stored procedure or function if you can avoid it.
http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functio...
I can't speak for postgres though. It might be different.
But in all seriousness, don't do this on your site. It is horrible.
What is the size and scope of the project? What feature-set are we looking at? Anything realtime? Performance critical? Large team building components at the same time? Maintainability? Scale?
If you really must pick a one-language-fits-all (and i think this poll reflects this logic) it would have to be python.
So, choosing tool before job; python. But also, you would be an idiot.
Documentation or fixes to comments in code is an obvious usecase for online edits cross-language.
If you'd really rather do the pull,open,fix,commit,push i would argue that you are too stuck in your own ways.