60 karma · joined November 29, 2011
How is that total access/open if you don't disclose what you're building. It would much much more interesting, in my opinion, to be able to relate to your stories if we have the proper context.
* Client Side: Rich/interactive application, which usually involve lots of Javascript. If not properly architect-ed and developed, inefficient code will run slowly and make the application hard to use. That's where "high performance" is needed. An example of such client-side applications could be Facebook. You client is handling the chat list, conversations, tickers, navigation (e.g. does not refresh), auto-scroll, and many many more client-side features. Having them all working seamlessly and smoothly running together is not a trivial task. Besides optimized javascript, there are other server-side details used to improve client-side performance such as using css sprites, caching whatever can be cached, minimizing/packing javascript, etc, etc...
* Server side: A lot of things are happening on the server. Again, depending on your application, performance bottleneck will appear that need to be fixed for the server to be able to handle the load in a reasonable time. Here are a few example of what those bottle necks could be, which would call for "high performance" measures: - A "really high" number of visitors on your site, generating a massive amount of requests to your server. - A "really high" amount of data is being stored/read in your database. - A "really high" number of simultaneous connection is required for your real time application. There are many more cases, but all the above will require careful selection of server-side technologies to allow your web application to function as intended, while minimizing cost, time, and processing power. (or whichever other variable your business cares about). An example of application faced with all the challenges above is again Facebook. They have to handle millions of users online potentially chatting (real-time), looking at pictures (high requests), and posting/reading comments non-stop (read/write to database).
Hopefully I've explaining "what are those application". Now when you ask "where are they used", I would reply "when they are needed" :)
http://msdn.microsoft.com/en-us/library/windows/apps/br22958...
So while some design polishing sounds like "chores" with low ROI, they can actually increase convergence rates with subtle touches (e.g. rounding corners) resulting in a great overall ROI.
Funny thing is, it's actually up for me :D
Steam is, from a user perspective, a video game marketplace on PC. In Win8, they will have to compete with the built-in windows marketplace, where most games will published directly. In other words, Win8 is a catastrophe for them as it's endangering their business.
Most businesses look for people who can deliver a product (technical skills), work in a team (human skills), and improve over time (potential). I think your application should be able to show you got those points covered:
1- Deliver a product:
Easiest way is to use previous experience at a different jobs. If you don't have that, it's as valuable to show personal projects you brought to completion.
2- Work in a team:
They'll usually get a feeling for that in person, just be cool, respectful, and communicate well ^^
3- Potential:
Show passion, you do what you do because you love it. You learn new technologies, try out new frameworks/patterns/ideas out of pure curiosity. The industry is moving and changing very fast, you need to show that you can keep up with it. In a way, personal projects can help point 1 and 3).
If you have those elements already, make sure you're selling yourself properly to recruiters. If you don't, fill in the gaps :P Hope that helps.
So for example, show that for every signup you know: 1. Where your users come from (e.g. referer) 2. Where your users are from (e.g. geo location based on ip) 3. User Agent, Browser, Mobile vs. Desktop etc...
This information is not only "cool to know" but also useful to understand who your potential customers are.
A few more things. In your "sales pitch", you mention your competitors (e.g. LaunchRock/Unbounce). I wouldn't suggest advertising for your competitor, and loosing potential customers to them, especially if you're value proposition is weak.
Finally, I wouldn't suggest your "call to action" to be to see pricing, that's also a turnoff. Instead, maybe you ask for emails for people interesting who want to use the beta when it's ready :P
Google doesn't know who you are, so results are not as relevant.
Are you focused on creating something quick? something that scales? something optimized that needs to run as fast as possible? something portable?
For some Python, Scala, or Clojure will do. For others, C++ is, despite what you may call flaws, the language of choice.
That being said, if you're very attached to a specific technology, find a place (or create one) where it makes most sense using it.
I would look for random code people wrote, for example on github:
https://github.com/search?utf8=%E2%9C%93&q=sort&repo...
And then just look at the code and try to understand how it works. This result for example seems to implement basic functions and is well commented:
https://github.com/erlide/erlide/blob/6b836bcb0770d23c4471f4...
Hope this helps
Fastest: Invested ~10k in Apple stock during afterhours before they froze trading before announcing their earnings. 30minutes later, sold those with an 8% ROI. 800$ (-commission/tax) in 30minutes.