•Re: Re: Re^3: VarStructor 1.0

[merlyn]

Can't believe I'm jumping in here again, but:

One of the reasons I'd be reluctant to release a subroutine of my script as a Perl module is that it would probably be pounced upon and improved beyond recognition and beyond my ability to work with it any longer, and I wouldn't want to lose my first baby.

if this is true, then you are not yet a professional-level programmer, nor ready for a public review cycle. Please learn that you are not your code. It's not "your baby". This sort of pride will keep you from learning what you need to learn to become a better programmer, and perhaps even in some ways, a useful programmer.

Code is just code. A series of steps that you happened upon while trying to solve a problem in order to solve it repeatedly. There are very likely always better steps to do the same thing. It's not personal when someone says "here are better steps": it's just what it is, better steps!

The end product of coding is getting the job done. Not having something pretty to look at. This is technical work, not art.

I can now see why you react so badly to feedback, if you truly believe this way. And my hope for you is that some day, you'll realize how narrowing and ineffective your view forces you to be.

[Wassercrats]

I'm more receptive to recommendations than you all think, but I'd prefer those recommendations to involve more than style. I'd rather have a module that I don't have to learn to understand, especially since I'd be expected to maintain it, than one that's easier for others to understand. When it comes to my parameter handling vs. tkil's, and using strict and "my" and stuff, I'd just as soon have everyone downvote me than change, unless I hear something more substantial about why the change would be beneficial and not just unsupported claims that it would be easier for me and safer.

When it comes to people saying that my module wouldn't be useful, it's hard to believe that because VarStructor has some advantages over Xref, and people have no problem with Xref, but that doesn't matter any more because I intend to turn VarStructor into a commercial product, described at Re: Do not feed the trolls.... The variable values it displays would be as they are within the blocks they're scoped to, and I'll also have it optionally work with all used modules. Then you'll all be sending me money and gifts and naming your children after me because I'd have a unique, indispensable debugging tool that revolutionizes Perl programming.

And they'll be TWO dots next to my posts!