This is definitely not a waste of time. I do routines similar to this and I've definitely gotten stronger doing them. I also do many pull-ups as well which aren't on this chart, but all of these exercises are great exercises. You are NOT going to lose a lot of weight with this alone. However, if you are already a healthy active person then adding a routing like this only helps.
My brother spends at least 5 days a week at a gym lifting weights and eats a very strict diet. I'm more of the runner type, doing Taekwondo 2 days a week and more body weight workouts like this (and I eat fairly well for the most part). He's definitely stronger than me, but I have no doubt that I'm in just as good of shape if not better than him.
Ha! I have no problem with OO based programming. I do have a problem with OO based solutions for every problem. Sometimes it's worth pursuing alternative solutions, whether procedural or functional or a combination of what makes sense.
Not too mention, what many believe as an OO solution is often times far removed from anything remotely OO.
Not converting data into object graphs does not necessitate working with SQL in your domain model. I'm currently working on an application right now which favors simple data structures (hashes, arrays) over custom entities. It favors a business layer that operates on those data structures over composing dozens of "Model" based classes. That does not mean that persistence logic is littered within my domain.
"At some point you'll have to parse out result and build an object graph anyway"
This type of thinking has to stop! Sure, some times it may be necessary to extract data from SQL and turn it into some type of object. However, most of the time it's enough just to get the data and work with the data directly.
I actually started doing something similar to follow my own teams (thought someday I'd expand but just never have). Anyhow, one thing we've found is that player tweets are generally worthless and as others have already noted the bloggers/writers and just conversational tweets surrounding teams are often more informative.
Here is my page (which is not near as nice as yours but I really just built it for me to follow news regarding my Chiefs!):
I'm not sure that HN is a place for launching a site. It is, however, a great place to ask for feedback regarding most new software applications. I've been given great feedback on a couple of different websites I have done.
I'd like to see how .Net MVC would compare. I realize you'd have to spin it up on a Windows EC2 instance and there would definitely be some variance in the performance of that box vs. the nix EC2 instances but I'd still be interested in seeing how it fares in comparison.
I'm guessing the downvotes are for the snideness of your remark. A more respectable way to phrase your question would've been to simply ask how this framework compares to some of the other well known Node frameworks and why might I look into Sails to solve a specific problem instead of some of the others that are available.
I work from home and go into the office 1 day a week (on Thursday). Google Now has picked up on this and every Thursday morning I'll have card on my home screen showing me estimated time to the office.
To be fair, this is using a very early technology in a new way. I'm sure if their plans work out, then the speed of production can be reduced, whether it's through customized 3D printers specific to this use case or by other means. I wouldn't knock it just because the numbers are high this early in the development lifecycle.
I was going to suggest the same thing. Something like this combined with the Occulus Rift would be very entertaining and a step towards the idea of the Oasis. Not all the way through the book, but so far a great read and the technology described seems doable (for the most part).
Sure, but with USB 3.0 getting similar speeds to the internal SSD (according to Anandtech) I can add another 64gb to my surface pro for 30 bucks! Try doing that on an iPad.
Just so everyone knows, Zavers is a company (local to me here in Kansas City) that was bought by Google probably over 6 months ago now. This article doesn't even appear to mention that fact.
But, if you are forced to name alphabetically you might start naming those related instance variables in a related way (which wouldn't necessarily be bad). For example in your case you might have: myFileBuffer and myFileBufferLength which would hopefully be next to each other, no?
True, and I didn't mean to suggest that people should just use my application instead of this. I guess I was just pointing out that this to me is a simple feature (one that I think I added in less than a days time to our app) and they've turned it into a full-fledged product that they are charging for. As the commenter above stated, I guess once you have the rep of a 37signals you can charge for this sort of thing.
Thanks for the feedback and you weren't the first to be confused. We are working on new design on front side to help clear it up. We thought about larger use-cases but the problem I'd been experiencing as a parent with young kids in sports was directly related to communication with the coach (and as the coach with the parents) so that's why we focused on sports teams up front. But, I have created a "team" for other purposes in our app including the development of the app itself.
Not sure why anyone would pay 10.00 for this. We offer this functionality free in our app at http://teamloopapp.com and not only that the people on the receiving end can choose to get via SMS as well. I'm sure you can find it for free in many other places too.
$1,000 seems pretty meager to me. If I can share well over 50% of my code across multiple platforms then that is code that I don't have to rewrite in another language. If that 50% takes more than 10 hours to reproduce (allocating my time at $100.00/hr) then it is well worth the expense. That doesn't even factor in the time saved in maintaining the application going forward.
Granted, if you are just building a small application that you don't plan to support multiple platforms then that price would seem steep.
Someone writes you a check for your birthday, you don't have to drive to bank (or mail) to deposit. Simply take photo of front/back and send it via app and money is deposited into your account.
I currently use Simple for my discretionary spending account. I really love the interface. However, if they are serious about converting people to use it as their main bank then their entire focus should be on allowing multiple people on one account. I can't add my wife to my account means this can't be my primary bank. It's that Simple!
...oh and after that, please create a mobile site that allows me to login from any device. I despise having to use my wife's iPhone to check my balance!
Much like the common definition of "bootstrapping" for entrepreneurs, which HN is targeted at, it provides programmers a way to bootstrap the look and feel of a product. It may not be a long term solution but it offers a quick, easy, and decent looking solution to getting a product out the door.
Yet the refactored example is still showing application domain logic being built within the web framework. For simple applications that are only ever going to be delivered via the web and only ever rely on one particular web framework this might be ok. That being said, I'd like to see movement away from this back to using web frameworks or anything else simply as the communication platform between your application and the user.
That sounds like good advice. I'm certain they are aware of the problem. I had emailed the guy who owns the domain before any content was put up and I told him what our website was and what it did and he told me that he knew the teamsnap guys and that they run a similar site (although he refused to sell the domain). So he had explicit knowledge and I have emails that indicate that.
Well that hasn't been our experience. We've dealt with many issues and we've had customers from 4.3 up to 6.0. Not to mention devices from 3GS and the original iPad up to the latest. I haven't done any Android applications yet but I can imagine it would be worse if you wanted to target a large base of users (I will be gaining that experience rather soon).
I think the correct statement would be iOS has "less" fragmentation. They still have fragmentation though. Not only through the devices but also the version of iOS running on the device. It can get pretty hairy trying to maintain support for multiple iOS devices with versions of even just 4.3 and up.
> Because Windows and Windows apps don't support resolution-independent UI scaling.
If I'm not mistaken the new, formerly known as "Metro", UI is vector based and any applications built with the WPF which includes all Windows 8 GUI based applications (at least the non-html one's) are of course vector based so it's simply up to the designer/developer to scale it however they want.