Drive has 700+ articles for digital transformation leaders written by StarCIO Digital Trailblazer, Isaac Sacolick. Learn more.

Php, Perl, Ruby, Java, or .Net. Many startups kickoff with one or two engineers and will often pick ‘the best’ technology stack, or just the one that they want to work on. The latest greatest framework.It’s my blog, so I get to be biased. I’ve seen about two dozen different startup environments. Not a huge number, but not a small number either. So my opinions are largely based on what I’ve seen these startup environments morph to after one or two years of development.

First, if you’re building a product that’s interfacing with native Windows systems, then you should probably be looking at a .Net architecture. Otherwise, my preference is the open source languages because of the infrastructure and licensing cost savings.

I vote a thumbs down on PERL as a web development framework. The language is very powerful, particularly for small projects, scripting, data processing, and even lightweight analytics. However, for web applications that tend to have larger code basis, I think there are better platforms. I’ve seen very large PERL code basis on the order of 1M lines of code. Ugly. That’s all I can say. If you’re strong enough to do PERL, then move over to Java and follow a framework so that others have a chance to build off your programming.

Ruby? Quite honestly, I haven’t reviewed enough large sites using it to weigh in on this relatively new language. If you’re a fan of Ruby, make sure you have a good understanding on where you’ll find other Ruby programmers.

Python has been around awhile, but I know relatively few programmers that list Python as their top language. Same rule applies to Python as Ruby.

My general preference is Java (more on this next), but if the startup team is more design oriented and not from a traditional programming background, then I would recommend Php. Java is great for software programmers but if the development team doesn’t have a strong Object Oriented background, then the resulting code will probably be a mess. A design oriented team might as well stick with a RAD environment like Php.

Why Java then? I could list several reasons; a very powerful IDE (Eclipse), a choice of app servers (open source and commercial), lots of web development frameworks to choose from based on your application needs…. But the most important reason is scalability, not processing scalability – I mean resource scalability. Most startups begin development work with a very small team and often with one (or a few) really fast experienced programmers. These developers pick frameworks that enable them to do rapid, agile development. When they need to add new development resources, they can find people that are familiar with the chosen frameworks and the new programmers can use the frameworks as a guide to learn the application specific presentation, logic, and data access patterns.. When the Founders need to upgrade their implementation in a specific functional area, they can apply standard refactoring methods to the appropriate areas of code.

This is not to say that this can’t be done in other programming languages. It can. But in my experience, the combination of the OO background of Java architects, and the tools, frameworks, and standards in Java facilitate resource scalability.

Published on:

Leave a Reply


StarCIO

My company, StarCIO, provides leadership, learning, and advisory programs for companies looking to accelerate delivering business value from digital transformation. Contact me if you’d like to learn more about partnering opportunities.


Isaac Sacolick

Join us for a future session of Coffee with Digital Trailblazers, where we discuss topics for aspiring transformation leaders. If you enjoy my thought leadership, please sign up for the Driving Digital Newsletter and read all about my transformation stories in Digital Trailblazer.


Coffee with Digital Trailblazers hosted by Isaac Sacolick

Digital Trailblazers! Join us Fridays at 11am ET for a live audio discussion on digital transformation topics:  innovation, product management, agile, DevOps, data governance, and more!


Join the Community of StarCIO Digital Trailblazers

3 comments:

  1. What’s your opinion on .NET and C#? It has really helped us cut down on development time. The only issue we face with it is finding a decent host.

  2. Thanks for taking the time to discuss this, I feel strongly about it and love learning more on this topic. If possible, as you gain expertise, would you mind updating your blog with more information? It is extremely helpful for me

  3. What is your opinion now, six year late?

About Drive

Drive Agility, Innovation, Transformation

Drive is the blog for digital transformation leaders brought to you by StarCIO and Isaac Sacolick.

Agility, Innovation, and Transformation are the three primary digital transformation core competencies that every StarCIO Digital Trailblazer must champion in their organizations. Learn more About Drive.


About the StarCIO Digital Trailblazer Community

StarCIO Digital Trailblazer Community

Revolutionizing traditional learning, networking, and advising experiences.

Visit the community


About StarCIO

StarCIO

About Isaac Sacolick

Isaac Sacolick

Author, 1,000+ articles, keynote speaker, Chief StarCIO Digital Trailblazer. Full bio


Driving Digital Newsletter

Driving Digital Newsletter

StarCIO Guides

StarCIO Agile Planning Guides

Digital Trailblazer

Digital Trailblazer by Isaac Sacolick

Driving Digital

Driving Digital by Isaac Sacolick

Driving Digital Standup

Driving Digital Standup

Coffee with Digital Trailblazers

StarCIO Coffee With Digital Trailblazers

Recognition

InfoWorld 2025 Judge
InfoWorld Technology of the Year 2024 Judge
Thinkers360 Top 10 in IT Leadership
Thinkers360 Top Agile Thought Leader
Thinkers360 Top DevOps Leader
Thinkers360 Top in Digital Transfomation
Thinkers360 Top in Analytics
Thinkers360 Top in Product Management

Discover more from StarCIO Digital Trailblazer Community

Subscribe now to keep reading and get access to the full archive.

Continue reading