4 ms·
We're doing a bit of both, with the known and quantifiable (web hosting management) supporting our pioneer efforts to be part of a new and almost entirely unset
by SwellJoe 18y ago
We're doing a bit of both, with the known and quantifiable (web hosting management) supporting our pioneer efforts to be part of a new and almost entirely unsettled territory (cloud computing). I wouldn't necessarily recommend it over other tactics, but it's what fit our business and our existing codebase--we launched based on an old and well-established Open Source project and the existing code greatly directed our first couple of years in operation. But, we also know that becoming a leader in a well-established field, full of well-funded competitors, is not necessarily a trivial endeavor.
So, while we think our hosting management products will be a nice source of revenue for years to come, it's the combination of those tools with cutting edge stuff in the virtualization space that will allow us to lead rather than follow (because no matter how good your products are in an established market, you'll probably always be playing catch up in the mind of the market).
I also think you're underestimating the amount of interesting work that can be found underlying seemingly mundane tasks. I've found that data analysis and visualization can be a really interesting and fun pursuit within systems management software, and it's an area that brings tears of joy to customers (seriously, people wet themselves over graphs and charts...if you also add export to Excel or CSV, there will be fainting).
Regardless of all of that, you have to solve problems that customers want solved. If you're doing that, the harder problems are better, if you are willing and able to solve them faster than your competitors.
But, if you are starting a business rather than a research project, you need to make your decisions based on what people want rather than what you want to work on. You cannot start from "here's a cool technology, let's figure out a way to sell it", at least not generally. You must start from, "Here is a market that is being poorly served, and I can serve this market well." If you can fit, "by building interesting and cutting edge technologies" into that sentence without breaking it, then you've got yourself a winner.
- aaronblohowiak 18y agoI'm looking forward to seeing the new virtualmin support xen. I have been trying to make more interesting out of the apparently mundane; reimplementing the google charting api internally cause we needed to make charts, and even some good ol' csv exports (interestingly, csv export formats that are useful for biz people are not the formats i would prefer as a programmer.. the more you know..) further, I'm focusing on trying to learn the best tools for the job -- picking up vim finally, trying to grok sed/awk, bash scripting where appropriate.. even perl is sneaking into my head. make stuff that people want is a great mantra. i suppose i got into programming because it was a process of discovery and a process of invention. keeping it that way seems to require intention.
- kirubakaran 18y ago> trying to grok sed/awk, bash scripting where appropriate.. even perl is sneaking into my head May I suggest that you roll all that into one neat little endeavor of learning Python... :)
- SwellJoe 18y agoI've written system administration tools in both Perl and Python. Perl is the better tool for the job (Ruby might be better still, once Unicode and performance are straightened out). My Python code always ended up being significantly longer and slower than the same task written in Perl. Partly due to CPAN (if you can imagine it, there's at least three libraries for it in CPAN), and partly due to the nature of Perl. Perl is like a DSL built for system administration. Sometimes it gets a little clumsy on non-system administration related tasks, but when you're working in Perl's sweet spot of functionality, it's a very nice experience. That said, Perl can be intimidating, because it is such a wide ranging language, and some of its features aren't quite right (references, and the way lists and arrays behave, can be confusing, and they're still a source of confusion for me after years of working with Perl). Python has its own quirks, and though I spent a couple of years working almost exclusively in Python, I didn't find it at all painful to come back to Perl. Ruby, on the other hand, is a language that could probably steal my heart. Between deciding to shutdown my old company and starting up Virtualmin, I was undecided on what to do with myself. I learned some Ruby and tinkered with Ruby on Rails. Loved Ruby instantly. RoR, not as much.
- kirubakaran 18y agoGreat info. Thanks a lot.