Quote:
Originally Posted by kazana
I've got the maddest respect for folks struggling with project 0, yet, dreaming about the awesome stuff they can build with the tools of choice.
The main reason being, I suspect, because I have become disentchanted over the years and that type of passion hasn't been mine for a long time.
The secondary reason being that, in most cases, they are right. It may not be the perfect angle or solution, but almost any solution is better than none.
Yes and no. I mean, we are talking about people that don't study at home and want to learn Java, config, JVM, and working with 3rd-party APIs on work time. For certain, we all dreamed of something large when we first started, but I think that something large is small beans compared to what they are trying to take on.
irt to disenchantment: I think one of the benefits of working for a non-tech company is that you really get to learn about tools from an end-user perspective. If you are technical (and you are willing to use it), you create something that you own deeply because you are working on solving problems you lose sleep over.
I don't buy the "better than nothing" argument. I think many of the tools used by small business ultimately cause the company to lose money in the long-run. My coworkers and I aren't professional programmers, but with two remote servers, FOSS programs, a database, VBA, one-off macros, Excel equations and JavaScript, we've created many tools to make up for the short-comings of the systems we are forced to work with. In a perfect world, there would be a department solely dedicated to creating a robust company-baked system that unifies everything, works as advertised, and isn't a total money-sink. I'm not entirely sure if this is possible with the current knowledge pool, but we did compare what we created with 3rd party tools, and to be honest, what we created is far better, so there is some hope.
When this talk of creating something started a long time ago, there was an open debate about languages. I shot down C# (not paying), Pascal, and C++. I did suggest using Python, Java, or Ruby, only because it would be easiest to find replacements. Of course I would most prefer to use Python since that is one of my better languages, but since I have no part of this, I didn't push for anything.
There was myriad reasons Python was shot down, but the two main ones were omg! significant white space and "no one uses it for anything."
I was fascinated by how emotional and irrational this whole debate was even among people with no knowledge. I'd love to see experts debate this stuff.