Senior Software Developer

New software developers are often asking themselves, and others, what is it that makes developers to be considered senior?
Some senior developers, also ask themselves if and why they are considered senior (usually when they are seeking a new workplace).
Is there a list of things that I need to do in order to become senior? I would say No, and yes. Well there is no algorithm to measure how much senior a person is. Seniority is a matter of experience. And yes, there are a few ways of gathering experience.

I laugh everytime I see the distinction of senior developers as those having 5 years of experience or more. Imagine a guy who started working on his first job on the 1st of July 2011. He should be very happy right now, because in 3 days he will be baptised "a senior", as it will be the 5th anniversary of his carreer.

I will try to summarize my thoughts here. Here we are with some pragmatic points I consider as general directions to what exactly software development experience is. And everything in this list comes with a lot of experience:

• to know and recognize software design patterns
• to know and apply what is known as best practices
• to have holistic view of the solution or system or application
• to be up to date with existing and new technology developments
• to have the ability and mood to test and measure different things while designing a solution
• to be able to define the trade of technicalities with business needs and time management

Experiment as a word contains the word experience. That's what experiencing things mean. Experience means conducting experiments, and an experience software developer is the one who has experimented a lot. And of course your experiments should be based upon experiments of other people. The programming languages you use, the libraries, the frameworks and the virtual machines are (successful or not) experiments of other people. If you are not based on others' experiments, then you would need to experiment on whether "if" works as it claims, or whether "for loop" loops exactly the number of times it should!

You get some sort of experience when you are reading a book or an article about a technology, but still, this experience is far from conducting an actual experiment.
You are actually reading the procedure and the results of an experiment that was conducted by someone else. That's not bad. It's great!

That said, the most purely experienced software developer is not the one who has read a lot. It's most probably the one who have participated in a lot of different projects.

I know people who are working on the same project for years. I can't say they are not experienced. They have achieved to master another aspect of the experience: "deep" experience is often mentioned.
This is the kind of experience that can probably be referred as "specialization". And of course, "deep" experience or specialization does not come by itself... You have to mention right after "what" this "deep experience" or "specialization" is in. I mean you must be specialized in something, right? It's quite contradictary to be specialized in something that is abstract or too general...

Last but not least: have in mind that keeping up with a project for years means that it's complex enough, at first, and above that, it keeps your interest high, it's challenging. In other words, it has to be an evolving project. Otherwise, you will be "specialized" or "deeply experienced" in such a small amount or range of stuff that could make you feel embarassed.

SQL testbed sqlfiddle.com

First impression

I 'm so much impressed by this service www.sqlfiddle.com that I wanted to tell everybody about this. I discovered it through some questions and answers in stackoverflow, and I found out that it exists since 2012. I have seen several fiddles that enable online testing of other languages, but the magic of this one is that it's about databases, and you need to create and store your schema also. Moreover, you can choose among the main Database types and providers to test.

The problem(s)

I always wanted a test database server available and accessible from my PC to test different scenarios of tables, joins and performance of queries. I know it's nearly impossible to have installed Oracle, MySQL and MS SQL server on the same PC and test whatever you like... not to mention that some times the needs are to test on a specific version.

So, I was trying to find alternatives from buying a subscription to cloud services for all the above different DB vendors. Not to mention that I was thinking I could develop something like a test-bed and push it to the cloud... Fortunately, I recently found-out that somebody else did that.

Problem #1

You have a problem with a query for a client running Oracle. You are on the go and you don't have access to your development environment (of course) and you want to test the diagnostic query you want to send them before you send it (of course).

Problem #2

You have a brilliant idea on how to model your data and implement a special feature. But you don't have access to the development environment and even if you had, you don't want to bother with administration and installation of a DB server on your laptop. You just want to write SQL.

Problem #3

You want to help somebody in stackoverflow who is asking for help on a database-design SQL problem, or you may want to ask for help. The person who wants to ask for help can create a sample database schema and provide a query. That will be very convenient for other people wanting to help and reproduce the problem, as well as to test their suggested solution.

Solution

All you need is:

1. to access www.sqlfiddle.com
2. to select the corresponding DB server vendor and version. The supported databases list:
• MySQL 5.6
• MySQL 5.5
• Oracle 11g R2
• PostgreSQL 9.3
• SQLite (WebSQL)
• SQLite (SQL.js)
• MS SQL Server 2014
• MS SQL Server 2008
3. to provide a schema creation script (or have it saved with a link)
4. to provide a test data creation script (or have it saved with a link also) 

That's all. You are ready to test your diagnostic query before you send it.

More specifically:

Step 1: Select the corresponding Database and version.

Step 2: Provide the test schema creation script, and the sample data insert statements, on the left pane, and click on "Build Schema" button.

If the DB schema creation script has errors, then they will be reported at the bottom pane. If everything is fine, then the schema is created, and the right pane is activated where we can start testing our diagnostic queries.

Step 3: Ready to test your diagnostic query on the right pane. And the results appear on the bottom pane.

At the left pane, a schema browser is also available when clicking on the "Schema Browser" button. And as the results are presented in the bottom pane, a link for the "Execution Plan" is also available. What else to ask for?

Last but not least

You are thinking that sometimes you have to create a hundred of tables in order to replicate a database and address a special issue that you have. You are right, that's why www.sqlfiddle.com allows you to save your schema by keeping the link. And then you can access it from anywhere you have access to the Internet. For example, you can check the example I created for this post: http://www.sqlfiddle.com/#!9/5adfe.

The service also offers a free subscription option using authentication through Google+. This feature allows the user to maintain a list of schemas and queries under his account.

Credits

The project has been developed and maintained by Jake Feasel and it's open source at: https://github.com/jakefeasel/sqlfiddle2.

More information at: http://www.sqlfiddle.com/about.html.

In the future

I wish this service keeps up to date with latest versions of RDBMS. Moreover, a nice to have feature would be if I could choose to provide Java code with JDBC on the right pane.

However, if you need to test your Java JDBC code on MySQL, then there is http://www.tutorialspoint.com/compile_jdbc_online.php for this purpose. A review of this service is coming soon.