News for hackers. Stuff that matters.

asciitaxi

Re:An Open Letter To Business People on Thursday November 11, 2010 @07:38PM (#1896025)
I think a "code plan" is the equivalent of a "business plan". Neither have much value. A working product is execution of the code plan. A working business is the execution of the business plan.

When the technical person creates the working product, they have delivered on their side of the bargain. I think the problem is that many non-technical founders think they have made the equivalent contribution by having "a plan". They haven't. They will have made the equivalent contribution when the execute the plan and make money.

Re:Is Microsoft in trouble? on Tuesday October 19, 2010 @05:56AM (#1806646)
I think the problem is that MS used to sell everyone Windows for $300 and Office for $300. Then everyone had to buy them again at work. I'm not sure how they can make this up licensing a phone OS. What can they charge? Ten dollars?
I have used AWS on 2 projects now.

On the first project, we used 2 small instances as web servers, 1 small instance as a database master, and another as a slave. The slave machine handled backup of db and uploaded files by zipping everything up and throwing it onto s3. There was no EBS or RDS at this time. The main problem we had was sharing user uploaded files between instances. We used Gluster (http://www.gluster.org/) for this, but it was complicated and gave us problems. In general this setup worked fine and we could add webserver instances to handle traffic spikes. Even this limited setup took a bit of effort to maintain and I often wondered if we could have just handled the whole thing with one large or extra large instance. Does anyone know if there is some bottleneck that comes from vertically scaling like this?

Sadly, on the second project we haven't really needed to scale at all, so we just use one small instance for everything and have our mysql files and user uploaded files in an EBS volume. I haven't really figured out backup and restore from snapshots yet, so I just zip up the contents of the EBS and transfer it to S3. We are using cloudfront to serve static files and it seems to work fine.

Ask HN: How are you using AWS to serve and scale your web app?

Which Amazon Web Services products are you using and what is your setup?Do you scale your EC2 instances horizontally or do you find you can handle most bottlenecks by moving to a bigger instance?Do you put your db in EBS, RDS, or just use EC2 storage? Why do you or do you not use RDS? How do you handle backups?How do you share user uploaded files between web server instances?Thanks!

( Read More... | 1 comment | 3 points | on HN )
Re:Simplicity Is Highly Overrated on Friday September 03, 2010 @07:17AM (#1659194)
I think before the advent of personal computing, a bit of extra complexity was ok. Life was pretty simple. You had a car, a stereo, a tv with a button for each channel, a stove/oven, and a calculator. You actually had room in your mind and time in your weekend to read the manual and figure out your new VCR. It was fun!

Making complex things was actually expensive to do, so a microwave with lots of functions cost more than one with a single button that said "heat up my food". This made it a bit of a status symbol. It was also the start of everything becoming digital, so it was cool for everything to have lots of buttons and a fancy readout.

Now we have several TVs, all with several boxes, incorporating our audio system, and connected to several services. We have smartphones, computers, tablets, printers and routers. Then there's all the software on and off the web to figure out, configure, and get working together. And you have to deal with all that at work, too. It's tough just to stay afloat.

So, the last thing you want is a digital toaster. They can make it look as complex as they want, but it won't make it look any more expensive. Today something looks expensive if it is simple, heavy, and looks like it was handcrafted by a German man. People still lapse into 1980s thinking and make the association that complicated means better, but that will wear off.

I'm not saying that extra features aren't sometimes important, but features are so easy to add to things today. You just have to type a few lines of code. Making someting look complex is easy and inexpensive. Making something complex look simple takes much for time, effort, money, and talent. Increasingly, people will pay for that.

Re:iPad: Or, why you have to look at the advertising on Thursday January 28, 2010 @01:38AM (#1083197)
Really brilliant article
Good stuff! I'll be moving to Canberra in January and I was a bit worried that there was very little of this sort of thing. If you're still meeting in 2 months, count me in.