As someone who has been an enterprise customer this depends on a lot of factors. First being who your competitors are and how their pricing is structured. At work we are evaluating three products and the one that has a yearly fee will win because the other two charge based on usage. I would definitely tend to start with a yearly model until you have lots of customers.
One thing to consider is, can you put their logo on the front of your website? Some companies I've worked for do not allow this while others will endorse your product. Be sure to think about the overall value of the customer and how you can leverage having them, but don't make your business depend on their contract.
Agreed. I became a nihilist as a teenager and still believe life mostly has no meaning. Humans will all die and the earth will keep turning. I don't really believe in an afterlife.
At the same time a person gets miserable going against the grain of society and thus you learn how to be content and how to keep your emotions in check. I do not see any conflict in these two things. I see it as the survival skills of a nihilist.
Your natural instinct will be to prosper in this life, it doesn't mean there is a bigger meaning than farting and dying.
Beanstalk is nice for rapid development. The problem I is that it doesn't scale for nontrivial architiched apps. I've converted failing beanstalk deployments to real orchestarators a few times.
I bought XOM about 2-3 weeks ago at 71.75 You're also not calculating dividends. Xom is pay 4.4 and some of my other holding have already paid a few thousand in dividends.
I average 12%-20+% yearly. I like to look at companies with a good PEG (price to earnings over growth) on a PEG of 1.00 or less unless their are good fundamentals. I like companies with a low P/E. I like dividends as I can reinvest cash.
My grandfather taught me about how industrials are cyclical and easy to make money on. Gas prices go up in the summer etc. etc.
Reading news means nothing. Understanding the overall picture of the economy, jobs, housing, commodities, macroeconomics (a fundamental understanding which few take time to learn) are key. Interpreting the "news" is important and learning to filter. Most news is (as the article kind of says) telling you what trends are happening. Never buy a trend. The news mostly tells the past. You have to focus on the present and future.
The news is actually talking about recession. The economy is strong at the moment. The news told us oil would never go below $150 a barrel. If you take time to learn the larger picture you would know these things are fear and not true. See the forest for the trees.
I was actually up 13% on ENB a Canadian pipeline company. My gain is cut in half because I doubled up on shares. I'm long on everything but RHT which is a cash payout.
Today I have 5 stocks i've bought over the past 60 days. I wont take the time to post my past 24 years of investing. I'm doing ok and so is my team of close friends I bounce ideas off of.
People who fail to read and educate themselves will listen to snake oils salesman pitches and trade stocks like a junkie on heroin. I spent years learning industries, learning how to read quarterly report, to identify signs of fraud, and pay attention to the news every single day.
Like anything you do you have to be committed and determined to be successful. It's not a dark secret that there are no short cuts in life. This article assumes we are all much dumber than I prefer to believe we are. We being people who have money to trade stocks and suffer from big losses.
I learned how to trade stocks by reading books about value investing and accounting practices. Very simple stuff that like anything worth learning takes a bit of time and effort. I don't get the upvotes on this article.
I worked for Ibm Websphere 1998-2002 in those days. I supported Aix, HP/UX, Solaris 8, and 4 rpm based Linux versions. Our job was to do nightly builds and test on each OS with DB2, Oracle etc. HP/UX and Aix were menu driven and painful for automation. Solaris was much more fun to work with. Redhat, SuSE, Yellowdog and mandrake were the linux distros. No yum to handle dependencies. I remember working on bash a lot to handle package dependencies.
One day I got an Itanium from Microsoft. It was fun to play with. Sadly I was forbidden from opening the server. It was so alpha that adjusting the clock would kill the server. It never went very far due to being so alpha.
Ansible is an imperative language while Puppet is declarative.
Ansible is push mode (ssh connection) while Puppet and Chef have an agent that pulls and enforces configuration.
Ansible is great for quick hacky or one time solutions like building a server. It's very newb friendly and easy to use out of the box. Puppet is great for enforcing a configuration every 30 minutes and scales across Data Centers. In my opinion Chef is more robust and is easier to use and share cookbooks on Supermarket.
Ansible Galaxy isn't as great for sharing work, but I find Ansible is so easy to use I don't need anyone else's work.
Once this has a pull mode (agent) it seems it will be like a very lightweight Puppet like declarative tool. Both Puppet and Chef have very mature products for serving and managing infrastructure. They can scale.
This tool might be awesome years from now, but I have to use Ansible everyday at work. From 2.0 to 2.8 it has become a solid and fairly mature product. I also use Puppet and have for 10 years. It feels old and is a pain to use across 1000s of machines in an Enterprise. There is a learning curve and training to be done at all times. At my last job I used Chef and I really love it for being powerful, easy to use, and just having a great design.
We currently install Puppet with Ansible once initial config is done to enforce policies. I could see this potentially replacing the Puppet side of that equation some day.
I'll for sure watch this tool and experiment with it in my lab as it grows. I do love Python and Puppet is far to long an overhaul. It will be interesting to see what directions are taken as this new product matures.
I do not think this is about using python instead of yaml. It is super easy to write Python modules for Ansible and use them. We have to use them for the things that aren't included in the base such as managing Infoblox etc.
IBM's customers are the same as Microsoft's customers (at least the high profit ones). Very large enterprise companies locked into contracts worth millions and 100s of millions of dollars. They move slow like icebergs and carry as much weight.
They don't worry about new customers when the largest companies in the world have gone through months or years to get them as preferred tier one vendors.
Sears on the other hand did not serve large Enterprises and were generating revenue mostly from retail. Consumer vs. Enterprise is like Apples and Oranges guys.
FTP TCP and IP are protocols, GSM is a european standard and REST is an easy method for building applications in which the backend is called the API (application programming interface) which typically use the http protocol. RESTful generally means using CRUD create, read, update and delete although it isn't a standard.
Some api's are private as in the one your bank's mobile app most likely uses. Some companies offer their API's to the public. They are both still APIs though.
One thing to consider is, can you put their logo on the front of your website? Some companies I've worked for do not allow this while others will endorse your product. Be sure to think about the overall value of the customer and how you can leverage having them, but don't make your business depend on their contract.