I am starting a new role running engineering in a young startup. The stuff they

Question

I am starting a new role running engineering in a young startup. The stuff they have is in SQL Server / Windows. I get the feeling we should think about moving to an OSS architecture, main reasons being cost, the ability to test new tools on the fly as they come out, and integrate with leading technologies like RoR and Python easily.

Anyone has any suggestions on this?

Can it get ugly if we keep our DB backend on SQL Server / Windows and build a Linux / OSS architecture on top of that? Or is the software BizSpark gives you access to enough for anything you need while you stay in the MSFT world? Are tools like LINQ and SSRS good enough?

Don't mean to start a fire here, just a real issue our company is struggling with. Thanks for any replies.

Explanation / Answer

You should use whatever the startup's programmers are more experienced and comfortable with. If that's .NET, SQL Server, etc., then stick with what you've got. If that's Python or Ruby or something else, then switch.

You should probably clarify what "running engineering" means, also. It sounds hardware-related to me, but I have a sneaking suspicion that you're actually using it to refer to programming?

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.