Nice piece, your post. Really nice. It accurately shows your position and skills (IMHO[WTF]). You are a consultant, not a coder. Would you be the latter, you'd have come up with something to just silence your critics. A small, succinct piece of code, just to tell them to STFU. You didn't, 'cause your are a consultant. That's fine, consultants are needed sometimes to get people out of their narrow view and be helped to soar eagle-like over the broad picture, whilst having, as an eagle has, a keen eye for the smallest details. But what happens here?
Coder (random PerlMonk) : I have a problem implementing this algorithm considering X, Y and Z. The issue is here (points to code)
Consultant (sundialsvc4): Problems with implementing algorithms are known since the times of the PDP11, mostly due to memory constraints and user boundaries... (blah, blah... disgressing) ...and the 31 bit integer of S390 later... Solaris 1 and management/coder interaction... (blah, blah, blather...)
Coder: ok, got that. Have some solution? Any hint?
Consultant: first, you should do a ORM design of your overall architecture and draw explicit Venn-diagrams for your database queries, because blah, blah, blather...
Coder: -.-
See? People come here to learn Perl. People stay here to teach perl, and to learn more perl.
This is a site about real perl issues and real perl problems and real programming, and not a site for seeking advice of a consultant or giving advice as such. Sadly, not.
Code examples are necessary, because: "There is no other way of teaching than by example, and if it so must be, as a bad one." (Einstein)
...every object should be entitled to assume that its creation-time parameters have been checked. (In Perl, it is much safer IMHO to do this before instantiating the object, rather than to do it in the constructor.)
This, IMHO, is as wrong as wrong can be. It goes against Postel's Law. Soaring as a consultant eagle above the low levels of cranking out code, you should update your maps. Otherwise, your counsel is of no use at best, detrimetal at worst.
perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
| [reply] |
let me write that for you
Wow, you could not have misunderstood the intent of my request more grotesquely.
| [reply] |
I really don’t think that, in this case, I need to “let me write that for you.” It should be quite self-evident that I am talking about some function which, given (at least) a state-code as its input, returns an instance of an object. Any possible attempt by me to jimmy-up a code example would be utterly meaningless to whomever is actually going to act upon it, and also would be quite unnecessary. (I prefer to assume that people who ask questions here, most especially when they speak as the OP did, actually know how to write Perl code and don’t need any further help from me.)
Why would those people need your kind of non-answers? Bourne from years of not writing code?
Utterly meaningless and quite unnecessary spam is spam, it is not help, its spam.
Likewise, I don’t think that I need to “prove” anything ...
Not that more evidence was needed, but its nice to get fresh evidence you can't write perl code because you dont know how
If one was to judge your business company by your spams on here, it surely must stink like a sewer.
| [reply] |
apart from complete shit, you can't write anything, let alone code anything. You know Jack shit. You are a toxic individual, and the worst thing here. | [reply] |
