This is great advice - I would like to add a bit of philosophy that someone once gave me:
Experience is more important than achievement.
130 karma · joined June 7, 2011
Experience is more important than achievement.
This is definitely a solvable (and solved) problem.
and where do you sort? front end or back end? how much data are processing?
If you have all the data loaded clientside, sort it there. Otherwise, just make a call to the server to query for data compliant with the new sort order. Both methods are fairly low cost.
Personally, I thought it was a nice touch - there's almost no added cost to the user, more importantly, it cleans up the interface and frees up a few px of width.
I'm currently taking computer engineering and I really enjoy it. It is a mix of CSC and EE and unlike our CSC or SE majors, it requires taking higher level math and physics courses which are needed to analyze complicated circuits. I've grown to like developing software more, but it is valuable and interesting to learn about hardware as well.
Take whichever sounds more interesting to you, but in the long run, there isn't much of a difference. Also, you should be able to take some technical electives to learn specific skills.
My recommendation would be to maintain dependency versions yourself, i.e. download the version of jQuery you want to use and //= require jquery in application.js - then grab a new version of jQuery whenever you want it updated
Unconscious incompetence -> Conscious incompetence -> Conscious competence -> Unconscious competence
Here is a good HN post on Backbone and Sproutcore, with a great comment by the creator of Backbone: http://news.ycombinator.com/item?id=2119704
It was a bit cryptic to get some of the content; perhaps you could have an alternative and more straight forward navigation system.
This seems like an unfair generalization. I have come across many large non-Rails Ruby projects, e.g. Homebrew, CloudFoundry, Fog. A lot of reasons why Ruby and the like are good for web development also extend to other types of development.
I am pretty active on Stack Overflow and Github, so I think I'll put those on my resume as well.
A side benefit of Pagify is that it DRYs up what would otherwise be duplicated elements in content sites with static HTML pages, i.e. header, navigation and footer - and without any serverside processing.
That being said, a single page and this plugin in particular, certainly aren't the best option for all sites. The reason I made this was to make the development cost virtually the same for developing single page sites.
I'm going to work on an option to enable using pushState for navigation which would use hashless URLs. The only downside is that users would have to enter the site through the base URL or some JS would have to be included in each content page.
Thanks for the feedback, really got me thinking about how to add pushState support!
First impression: I'm not really sure what this is solving - the syntax is a bit ugly and the projects seem unstructured. Seems like the ability to customize the stack is minimal. I couldn't find any solid examples of this being used in production.
It looks fairly young so hopefully these concerns will be addressed.
An innovative framework that utilizes an established language for web development would be more beneficial, IMO.
- Running on Heroku is not really an asset security wise. I would put something more significant to ensure users that your site is secure.
- Make sure your site is secure; it will be attacked often and by professionals. Consider hiring an expert.
- The highlighting is kind of distracting and busy.
- You should be able to access some charts and see the going rate without signing up and loggin in.
- What is a Mt. Gox Redeemable code?
- There are laws in most countries that regulate banks in regards to leverage. Have you considered any of this?
- Margin trading is risky and some people will lose more than they bargained for, expect some repercussion.
Best of luck!
Have different environments set up. After every big push, run through a simple user flow to make sure what the user will actually see is what you intended.