105 karma · joined December 6, 2012
You may never recover those costs, especially if newer more powerful ASIC rigs are release each year since more overall network computing power diminishes your existing rig's efficiency.
Also - hardware breaks down under maxed out continuous usage, so there's that too.
I would still go one step further and at least apply the strategy pattern/polymorphism when you have a large if/else/case block going beyond 2 or 3 conditions in a controller or model or something. (assuming MVC web apps)
The fact is you can write out some ugly code directly in a controller where it might get some code working fast and prevent the freeze up of your output, but once working you should immediately move it to the appropriate place like a model or library, and apply a basic OO strategy pattern (perhaps not with factory/interfaces etc until needed later) where appropriate to cut down on spaghetti/nested conditionals.
This really does not take much more time than stopping at working code that is ugly, and is a good middle ground where it is not painful to return to later.
There is still no good excuse for "taking a dump in the corner" of your code base just to get a marginal gain in output.
Good points about bad articles in general. =)
So in other words if you read big news the minute it comes out about a company, automated systems and institutional traders have already made their moves based on the news before retail investors have a chance.
"... in villages receiving payments, people spent more on eggs, meat and fish, and on healthcare. Children’s school marks improved in 68% of families, and the time they spent at school nearly tripled. Saving also tripled, and twice as many people were able to start a new business."
"...one showed the sewing machine she had saved for over a year to buy, another proudly announced she had nearly finished paying for her family’s television set, and another held up a 300-rupee blanket for the winter, of far better quality than the one it replaced..."
Sounds like overall they are responsible about what they spend on.
For me, kind of annoying after using windows and Putty for remote servers where control is always control.
As others have mentioned - image optimization will help you a lot. Taking a look at firebug Net profiling, the homepage footprint weighs in at 2MB. 500K is your "studio" image, followed by the bridge bg photo at 370K.
So just optimizing these 2 images will reduce your bandwidth by around 660K or 33%. I'm guessing you can do both in 210K (150K bridge, 60K studio = 210K) possibly better.
EDIT: decided to actually fix it instead of just talking about it.
https://dl.dropbox.com/u/6653594/pantastic-there-i-fixed-it....
studio.jpg photoshop jpg 70 quality ggb.jpg photoshop jpg 80 quality
old: 494k + 369k = 863k new: 64k + 1k + 70k = 135k
savings = 728K or 36% of your total homepage footprint.
Save more by splitting all your polaroid shadows to png, and the photos to jpg 60-80 quality.
Requires html/css change to layout studio image as 2 images stacked on top (separate shadow png)
For example, the point could be - to get the most A's (high marks) with the least amount of effort and the most free time left over for fun. You don't have to take school itself seriously, but it is similar to a career where it pays to play the game.
Maybe you are talking about running your own start-up where it might not be successful yet? And you're trying to find your market fit? Then sure, maybe just writing new code and changing the product on a whim is what is best without writing up a spec.
Now consider a software consultancy with enterprise customers. The enterprise usually wants time and cost estimates, which usually means agreeing on precisely what you will be delivering in advance. You WANT to write a spec, to prevent scope creep and limit your liability, and they want you to tell them how long and how much (and a spec helps estimate those things). It's win-win.
Most enterprise customers can't wrap their CFO's head around true agile with iterations and open-ended times and costs. They want as much of a guarantee as you can give them for what/how long/how much.
Not saying one way is better or worse - but maybe it's a case of the right tool for the job?
=)
Also what app do you have to use in Mac OS X for sane window management? One thing that bugged me about giving a 15" MBP a chance was how "maximizing" windows doesn't actually maximize them and that sort of thing. I guess I thought window management was supposed to be built into the OS out of the box.
At least I can get work done on it from the recliner and plug it in to an external 24" monitor and keyboard for more serious work.
In my opinion the greatest thing about Windows 7 (other than general stability and being less annoying than Vista) is its window key + arrow hot keys to move application windows around super fast on multi-monitor setups. (and to do exact right/left splits on single monitors)
There is nothing appealing to me about Windows RT/Surface or Windows 8 for laptop/desktop, they both look like they will just get in the way of creating or working on anything.
Also interesting to know about gmail "dot blindness" - kind of like "plus addressing" you could use it to track who adds you to spam lists, by giving out different versions of your gmail address to different vendors (not that most people have time for that - I've never done this).
Plus addressing looks like this: myusername+whatever@gmail.com sends to myusername@gmail.com, but some site's email regex check do not allow this, so dot addressing could be used instead.
The gist of it is using number values (not percent or em or px) is generally the best all around solution to scaling line-height with differing font sizes proportionally, and it suggests tweaks for issues with this like subscript/superscript and IE 6 inline images.
So... use number values. And if you care why it is best or why workarounds for superscript are necessary, check out the (99 slide!) slide deck.
It's just too bad they are hacking on their live site, and/or not ever turning it off after they don't need it.
Don't get me wrong, FTP/live editing a site on production / shared hosting are all crappy ways of doing things for serious development but I can see how it might be useful for beginners.
We've all been there, yeah? even if it was back when php 3 and 4 were common.
In my experience on Rackspace cloud 512MB instances are the minimum you should use for tiny production apps. Also, they're discontinuing 256MB on OpenStack - these were suitable for single-user dev instances, but I got more swap and or locking if ever attempting to run publicly with traffic. 512MB instances solved that issue.
Edit: Also I should mention I'm assuming you mean wanting to run a fairly standard stack, not a stack targeted toward tiny memory footprint.
And I still might wait for some google maps app reviews before I upgrade...
Video of Zeppelin: http://www.youtube.com/watch?v=BBLUmXUprvU
My dad also had a computing magazine where you could transcribe small programs or text based games into your 800XL and make your own simple programs - which probably has a lot to do with why I'm a software developer today.
That and the IBM PC junior. Good times.
If you exercise enough, your diet doesn't have to be so strict, and you're way more likely to actually lose weight and feel good. Some rough guidelines of eating higher quality foods helps, but certainly exercise or lack of it is much more the root cause of so many weight/health related issues.
Most of the time it's very simple. Basic healthy eating and exercise. The problem has always been people don't want to exercise, and there are consequences to that.
http://www.rackspace.com/apps/email_hosting/rackspace_email/
http://www.codinghorror.com/blog/2010/04/so-youd-like-to-sen...
One easy way to manage it is make a folder for each hostname, and add things like mysql root password, ssh port, public IP, pivate IP as different entries relating to the all aspects of managing the host.