While JS is old, node.js, which spans many projects on GitHub, is a relatively new architecture, which has only gained traction in the last couple of years. This stands in comparison to Java, which has a much higher degree of consolidation due to its maturity as a server-side language (this is also true to an extend with Ruby).
I understand what you're saying, but I think the OP meant how often do you deploy on average. That is, take all the deployments you mentioned, regardless of the reason they happened, and average out.
Takipi lets you attach your own source code to the project, so you will see your original source code when viewing exceptions and other events, instead of decompiled Java.
Support for prettier stack traces is in the planning.
Hi Steve. These are some valid points you're making. We are currently considering an on-premises solution for precisely this situation you are describing.
Takipi's agent records information which is relevant to the issues which are detected (exceptions, latency problems, custom conditions set by the developer).
The data and source code are then encrypted with your secret 256-bit AES key and stored by Takipi. This data is in turn decrypted in your browser and viewed by you at app.takipi.com.
When you install Takipi, you are asked to enter your top packages (e.g. "com.mycompany;org.foobar.common"). Code outside of the filter will not be shown to you when viewing stack traces.
In addition, if, for an example, an exception is thrown by Spring AND caught by Spring, you will not receive an event for that case.
Takipi may be installed locally; the same installation process will work.
However, it does not provide live debugging like in your IDE, but rather a post-event drill-down (a "time travelling debugger"), as it is designed for testing/staging/deployment environments.
The moment you sign-up for Takipi a secret AES-256 key is generated for you (and never stored by Takipi in any way or form, and you manually enter it on your machine when installing the agent). This key is used to encrypt every piece of application data which leaves the machine. The source code is also encrypted similarly. The source code and the data are only decrypted in your browser when viewing the details of the event.
The story of how the heroine matures in front of our eyes as the weight of the world is placed upon her shoulders was really moving to me. Coupled with beautiful hand-drawn animation and an overall sense of gentleness and wander, it's been an real favorite for me which I enjoy watching time over time.
I have to say that at least from standpoint, this seems to be pretty heroic (to use quite a strong word) and kind of inspiring! To be able to believe in and forge ahead working on something you believe in. Regardless of the end result my own sense is that the at the end of the day the writer Mark can really be proud of his accomplishment.
That is so true! one trick (dunno if that's the best word for it though) for dealing with the challenge of delving into some big new project is really starting small. I try and pick the smallest most trivial task and get going from there. I've found that it helps me get into things more easily (divide and conquer I think). I'm curious if anyone else has tried this or has some other techniques to share about procrastination?
It appears we sometimes focus so hard on getting the answers we need, that we forget to take that one step back and make the conversation more pleasant for both parties -- something that would in turn yield better results and better relationships.