Today i received an email from AWS telling me that one of the EC2 instance i’m running is doing DDoS against an other server (against port 80 through UDP)
Here are my suggestions to start investigating on this kind of issue:
One of the best article i have recently read: we can learn so much from failures that it’s worth to try.
« No physician is really good before he has killed one or two patients. » – Proverb
Software entrepreneur culture is full of stories of the products that succeeded. But what about the products that failed? We rarely hear much about them. This can lead to a very skewed perspective on what works and what doesn’t (survivor bias). But I believe that failure can teach us as much as success. So I asked other software entrepreneurs to share their stories of failure in the hope that we might save others from making the same mistakes. To my surprise I got 12 excellent responses, which I include below along with one of my own. It is a small sample and biased by self selection, but I think it contains a lot of useful insights. It is an unashamedly a long post, as I didn’t want to lose any of these…
View original post 5 635 mots de plus
- Don’t bother with market research, because you just know lots of people are itching to buy your new product.
- Only release the product once it is perfect. However long that takes.
- Go into a market with very strong competition and compete with them head-on, because you only need a measly 1% of this market to get rich.
- Go into a market with no competition. How hard can creating a new market and educating all the potential customers be?
- Only think about marketing once the code is nearly complete.
- Write software for people who can’t or won’t buy software (e.g. 10 year olds, prisoners, Linux fanatics, people in developing countries, developers).
- Don’t worry about marketing, because good software sells itself.
- Concentrate on the technology and impressing other developers.
- Don’t listen to what your customers say, because you know best.
- Don’t worry about usability. It took you thousands of hours to write…
View original post 42 mots de plus
I would guess that the majority of the software that I have written in my career has never been used. Or, at least, not used enough to justify the long hours I and my colleagues lavished on it. I am sure that I am far from unique in this. I flatter myself that the software was intuitive, well documented and robust, but we never managed to convince enough people that the software solved a real problem for them. Creating high quality software is hard, but it just isn’t enough. The software also has to be marketed effectively.
Effective marketing means:
- identifying a problem that people will pay you adequately to solve
- letting these people know about your solution
- convincing them that your solution solves their problem, at least enough to try it
- doing all the above cost effectively
This is no easy task in a complex and constantly changing world…
View original post 1 587 mots de plus
Choosing the right product to develop is crucial. Great execution is also very important. But if you develop a product that no-one wants or no-one is prepared to pay for, then you are going to fail, no matter how well you execute it. You can often tweak a product or its marketing to make it more successful based on market feedback (‘pivot’) . But the less pivoting you have to do, the better. Below I list some of the criteria I think are important for evaluating the potential of new commercial software products.
1. Are you solving a real problem?
Has your customer got a ‘bleeding neck’? Is your software solving a problem compelling enough that someone is going to download it, install it, evaluate it, buy it and then learn to use it, with the accompanying risks of credit card fraud and malware? It is hard to change people’s…
View original post 1 095 mots de plus
ImgCred: http://openvswitch.org/, http://socketplane.io/, https://consul.io/, https://docker.com/
Containers have no doubt been a hyped technology in 2014 and now moving into 2015. Containers have been around for a while now (See my other post on a high-level overview of the timeline) and will be a major technology to think about for the developer as well as within the datacenter moving forward.
Today I want to take the time to go over Socketplane.io’s first preview of the technology they have been working on and since announcing their company in mid-october. Socketplane.io is « driving DevOps Defined Networking by enabling distributed security, application services and orchestration for Docker and Linux containers. » and is backed by some great tech talent, Brent Salisbury, Dave Tucker, Madhu Venugopal, John M. Willis who all bring leading edge network and ops skills into one great effort which is socketplane.io. I have had the pleasure to meet up with Brent and Madhu at ONS last…
View original post 1 371 mots de plus