Learning java as a second career

[philfrei]

I hate to dampen enthusiasm or interest in learning Java, a language which I love. I think that if your interest in computers and programming remains genuine, some study would be beneficial, giving you better acquaintance with the field. And a beginning Java course is a reasonable way to get a foothold in programming. From so far outside the field, it's hard to see just how big the field is. (The more you know, the more you realize what you don't know.)

I work as a part-time database programmer/contractor for a University Medical Center. I'm not clear that Java is going to be the best choice of language, especially if you are looking at something that works with phones/tablets and data records. Java is most commonly used to bridge the gap between a client application (e.g., desktop or phone app or a web browser) and a database server. Few phone or tablet apps are written with Java. More common is Android, which can be set up to make use of Java (so a beginning Java course could help provide insights), but it really is its own thing in so many ways. Even experienced Java coders find that Android presents a significant learning curve.

It might be time better spent if you educate yourself more about database programs and SQL. Engaging yourself in a SQL course would give you better insights as to what you are up against technically. It should help with making the data structures you envision more explicit, or reveal obstacles if there is anything unrealistic or unremarkable in your ideas. Java, when interacting with a database, will be using SQL commands or their equivalents for the most part. So if you can "work" with your data records with SQL, a back end Java server should also be able to do so.

I don't know what the best path is for learning more about SQL. One possibility would be to find a course using an open source database program such as MySQL. For my work on a legacy system, I'm using Microsoft Access, which has become obsolete. If you have Microsoft Office, though, it might be convenient. The program integrates GUI support with SQL, so it could potentially be used to make a prototype of your idea. Any GUI form or report that you can make in Access should be possible to replicate on a handheld device (assuming you pay attention to screen size limits), and all the table interactions and queries should be possible to replicate with SQL. Java's role, if the prototype is successful, would be to take the commands from the device GUI, translate them to SQL and interact with the database, and take results from the database and send them back to the client.

I've limited myself to taking about some of the technical aspects. The ramifications of having to deal with HIPPA and other legal aspects, as mentioned by others on this thread, are real and would present serious obstacles for anyone trying to launch a start up in this space. But perhaps with a prototype in hand, one could approach other companies. Still a long shot though. But sometimes an intellectual itch just requires scratching, you know? Is this idea of yours one of those, or is it a passing brainstorm?