I'm a guy who gets things done. I like to have my tools, options, and crew all laid out in the open so that I may determine an effective way to solve whatever problem is at hand.
... I solve problems. Not problems like "What is beauty?", because that would fall within the purview of your conundrums of philosophy. I solve practical problems.
I prefer to code web content, specifically because it's one of the environments that allows me to easily satisfy my below priorities in order. Making a website allows me to tell someone "Hey, check out this thing I did" and all they have to do is go to a page and it works. I don't have to tell someone to download an app, agree to my terms and conditions, load a framework, or install my specific runtime environment for something they may not even care for.
I have used many languages over the years in an assortment of IDEs and some by plain text, some more than others. I have found that most languages at least operate in very similar ways, they just use differnt syntax (If you understand the concept of a ternary operation, it's just different syntax between Java or C# or whichever object oriented language). So far I have used:
Web Based Languages
- HTML5 (including BootStrap)
- Django (Python)
- PHP3 and CURL
- Some Google APIs (including Maps)
- RESTful Web Services (including Yahoo! Weather)
Application Based Languages
- Java (including Android, jUnit, and JavaFX)
- C++ (Hobby level, with Ogre Framework)
- Microsoft Access
- Git (Command Line)
- Batch Scripting
- HamsterSpeak PlotScripting
In addition, I also have my Class C First Aid, WHMIS certification, and a class 5 driver's license.
My Priorities, in order
OOB Functionality (Out-Of-the-Box)
A tool is hardly good to anyone if it doesn't function, and if it functions right out of the box without any necessary preconfiguration, the users can quickly and easily get it up and running and on with their job. If the tool is truly powerful enough, people may take the time to learn it, but the chance is much greater that they will simply find a different tool.
All Inclusive/Cross Platform
Dedicating your work to any one platform limits your audience. It is important to understand that even though one platform may hold a dominant market share, they may wane in the future which will reduce your application's reach. By being multi-platform, you are able to reach many more people, and be recognized in more communities.
I have places to be and so do you. We need to get the product, get it working, fix our problem, and move on. This site used to be bare HTML, specifically to be as small as possible and ensure you get the information you want in as few packets as possible. Following this mentality reduces load time and stress on transmission hardware. I later decided to Bootstrap this site on the grounds that people would likely already have the CSS and scripts cached on their machines, making the load time irrelevant.
I will do my best to make something for you that will suit your every need. Unfortunately, sometimes "you" refers to a group of people and what suits one person may not suit everyone, but we have to try. This is why I love to leave a sort of "access panel" of some sorts to the user, so that in the event my program doesn't suit them, they have the ability to make the necessary changes themselves. One size doesn't always fit all, so let the end user customize it to their liking.
People like things to look nice. Given the option, you will always make it look nice. I have, however, ranked design last as functionality must always take precedence. If a program doesn't function, it is useless regardless of its design.