4 ms·
I'm young, still gaining real-world experience, and fully aware of the fact that I have very few of the right answers (let alone all of them). Why would I go to
by falien 17y ago
I'm young, still gaining real-world experience, and fully aware of the fact that I have very few of the right answers (let alone all of them). Why would I go to the trouble of developing my own tools on a regular basis when other people who are much better at building the tools I need have already done so, and groups have put more effort into them than I will ever be able to. I look around for the best tool to do what I need and very rarely discover that I need to build my own to get what I want.
In my opinion, a much better question along those lines would be what tools you use that you consider indispensable, why, and how do they compare to the alternatives in your opinion.
- absconditus 17y agoThe types of tools I'm referring to are generally specific to the work you are doing. For instance I developed a tool that is able to parse logs of HL7 messages from our programs and then resend them with various options for testing and debugging purposes.
- mahmud 17y agoyou might as well ask for a listing of their home directory. I think most programmers write house-keeping tools when they're new to a platform (or even a given box.) once you have your environment well tailored and you're comfortable with it, you forget you even wrote tools. log parsin and transformation is basically the essence of automated system administration. if you ever had a root account in a unix box you must have written at least ONE log transformer and messaging tool of some kind. OTOH, people working on REAL engineering problems using excellent tools on posh platforms will not need to write auxillary tools. How many log analyzers does a DSP engineer need to write? just an example :-)