As I said in other comments sometimes on hipchat I need to have a call with teammates that I do not have on gmail/hangouts. So I need to create a hangout with a link to share so that I can copy it into hipchat and anybody can join it. There is no way to do that on gmail. You need to open google plus that takes a while to load, then you need to go to the bottom right corner and wait for the Start video chat button to appear and finally click it.
I was not aware that there was a link (https://plus.google.com/hangouts/_) that lets you create a hangout with a link to share so that other people can join it. So I created a simple landing page with a button created with google hangouts api. After learning about the link I mentioned before, I changed the google hangout button by a normal link.
Javascript is a tool. The fact that it runs in a browser and on a server means that communication between the client and the server in a Javascript-based web application becomes a lot simpler. If you know how to use the tool, it will serve you well.
You can find things to gripe about in every language you'll ever work with. Javascript is available. Use it and contribute to it's community, or don't. Griping is not contributing. It doesn't solve any problems.
If you think Javascript could use improvement, write a library to help solve a specific problem or contact emca and report your problem/issue/idea-for-improvement.
Basically just stop complaining and start working. If you are of the opinion that Javascript is a horrible language that is bound to make your project un-maintainable and disgusting regardless of your expertise then choose a different language.
It's really a question about improving my workflow and improving my programming habits, in an effort to product quality code quickly.
Sometimes I'll get pulled onto different tasks abruptly and I don't really have a choice of when I get to switch, it usually happens only four or five times a day, so it's not a huge problem but it does interrupt the blocks of time I try to spend on other larger projects. I'm just wondering if there's any way to make the process of switching between projects easier?
I would suggest taking copius notes and using writing documentation to get over the switch.
For example, when I get started on a project, I normally sit down at my computer and surf the internet for maybe 20 minutes and play around in the command line. This "down-time" helps me get into the flow of things. Plus I normally try to avoid tight-deadlines so I don't really care if I spend 20 minutes dinking around on Hacker News.
If you have a similar work-pattern, maybe those 20 minutes could be spent instead reviewing a README.md or working on a Trello board, or adding new links to an internal wiki you've set up for the project.
I've found that touching the documentation that I've created really helps me snap back into a project since I can see exactly where I left off. And if I don't know what to do, I work on planning out the project.
Also, if all of a sudden I have a great idea of what to do, I'll spend half and hour or so making files and directories and writing the code entirely in comments. Then, when I come back to the project, it's only a matter of replacing the comments with real code.
How long did it take you to build this application, and in what ways do you expect it to grow in the next 5 years? What problem does this service solve?
