Visual Studio Community 2013
-
I would look at the possibility of anything new going to PostgreSQL and only use MS SQL Server when you have to. Yes that's two things to maintain but the cost savings might be big over time.
-
@scottalanmiller said:
I would look at the possibility of anything new going to PostgreSQL and only use MS SQL Server when you have to. Yes that's two things to maintain but the cost savings might be big over time.
Adding to list...my goal is to make 2014 the "year of development" (why does that make me think of the movie, 2010: The Year We Make Contact... :bowtie: )...going to try to close out 2014 of all lingering "admin" issues and then just maintain those "admin" issues and gear toward development. And hitting the books too...no gaming! (like I get to anyway!)
-
Look at Python as a general purpose language going forward. Super flexible, easy to use and can run on anything.
-
Python is almost always a good option.
-
Finally around to downloading this now
-
@scottalanmiller said:
I would look at the possibility of anything new going to PostgreSQL and only use MS SQL Server when you have to. Yes that's two things to maintain but the cost savings might be big over time.
I'm definitely a one database guy. And that one database is MS SQL Server. I did start using MySQL for a while, but life was too short to learn two database systems.
-
I use PostgreSQL, MySQL, Redis, MongoDB, Sybase, MS SQL Server, MariaDB, Oracle, SQLite or whatever fits the need at the time. Those are the ones that I used most of the time, though. But with so many new ones coming out now, using different databases for different things is more and more common.
