386 karma · joined July 21, 2009
Japan? Even if it's Japan, its economy isn't doing that well either.
Sometimes I think it's just me forgetting the details of what I've learnt so I can't explain it to someone properly.
But apparently if you have been paid for a job you agreed to do then that's considered a contract even if no documents were signed. If there are any lawyers out there please correct me.
There is no NAT in IPv6. The address that you get should be globally routable, Unless of course your ISP have any IP filters in place. In the end it will depend on how your ISP allocates IP addresses to you.
Initially, the main issue was non-IPv6 capable CPE devices like your cheapo ADSL modem. The way around this was via Teredo tunneling, tunneling on IPv6 packets within IPv4 UDP packets.
Windows Vista and above supports IPv6 pretty well out of the box including Teredo tunnelling out of the box. Most BSD flavours are alright via the KAME project... not too sure about Darwin though.
Anyway, it's been awhile since I've worked in the IPv6 area so god knows what else they've come up with.
Probably the problem with most technically inclined people is the inability to see the world through the eyes of the majority less technically inclined people. Then again I guess it depends on the target market and the product you're building.
Sort of reminds me of murphy's law. "Build a system that even a fool can use and only a fool will want to use it." :)
Although it may seem that I'm describing why and not what, a couple of weeks later I would be looking at that piece of code and wondering what's the purpose of that piece of code. :|
This happens quite a bit when pseudo-coding in the code and these comments get left behind. However, sometimes these green comments are good to quickly scan through blocks of code.
Seriously... probably looking at examples of beautifully design sites and getting some 'insipration' from them. Articles on smashing magazine are pretty good, http://www.smashingmagazine.com/
And I've recently found http://www.metalabdesign.com/
I reckon it just boils down to practice and lots of redoing your design over and over again. I don't like doing it because it seems like a waste of time compared to the amount of code I could have written.
This reminded me of a number of random crashes that a client of my previous company had. Stackdumps just showed random errors. We had about a years worth of crash logs from a couple thousand of network switches (they were an ISP). We initially suggested that this might be a problem with cosmic rays. We even checked the frequency of the random crashes with sunspot cycles. No relationship found. Turns out it was due to another component failing due to a design error.
Be careful of saying that the software is done and launching it big. What you have is probably a product that you think what others will want. Until you get feedback and slowly releasing it to the world, you do not know. Probably getting those unmotivated people around you to try your software might be helpful as a start.
I think historically there's been a higher chance of failure but as long as you learn from the mistakes, you'll do fine. Fail fast.
fyi, I used to lecture CS in Malaysia :) and I failed trying to launch an ecommerce site in Malaysia. But I'm at it again.:)
This article may shed some light on your dilemma http://www.fourhourworkweek.com/blog/2008/10/03/harnessing-e...
Keep reading and learning. If you don't already know, I find the following things helpful - http://ecorner.stanford.edu/ - http://steveblank.com - twitter
It's not about the idea. It's the execution. If it's a good idea, someone else is probably doing the same thing...unless you have a crazy idea. Know your competition and realised that you are one person against probably a whole team of people if it's not a niche enough market you're targeting.
Well that's my opinion anyway...:)
Actually, I wonder if there's another motive behind the filtering. I reckon by blocking access to certain foreign sites, it is actually giving opportunities to the locals to come up with their own home-brewed version of the service. The government is helping you kill off foreign competition.
Maybe it should be a case of "when there's a big problem, there's a big opportunity."