On 10/8/2015 7:20 AM, Uncle Monster wrote:
On Wednesday, October 7, 2015 at 3:18:33 PM UTC-5, Muggles wrote:
On 10/7/2015 3:14 PM, wrote:
On Tue, 6 Oct 2015 23:21:48 -0500, Muggles wrote:

On 10/6/2015 10:47 AM, Don Y wrote:
On 10/6/2015 7:11 AM, Robert Green wrote:

Instead, its wide-eyed "look at this neat feature I added!" ("Mommy,
I made a poops!")

Yeow, you really have a thing for FOSS writers that's pretty hostile.
Some
of the best software I have ever seen came from 17 year old FOSS
developers.

No, I'm disappointed in the efforts of my peers.

Talk to a "professional" software writer about the quality of
the code that he produces (number of bugs, lack of documentation,
stilted user interfaces, etc.) and he'll quickly blame it on
his boss/work environment:
- boss never gives us TIME to test things properly
- the bozos in Marketing that come up with these requirements are idiots
- the Sales folks who designed the interfaces listened to too many users
and didn't impose any consistency on their suggestions
- the documentation folks are all English-lit majors and completely
clueless as to technology
etc.

I.e., the *implication* is that, left to his/her own devices, you'd get
a MUCH better product! It's all the OTHER bozos on the bus that are
compromising HIS/HER product!

Then, when they are in an environment (FOSS) where there *are* no other
bozos *imposing* their will on their efforts, they produce the same crappy,
untested, undocumented, poorly defined code! And, when you call them
to task about it, they shrug and say, "No one was PAYING me for it,
so why should I do those things (that I don't WANT to do)?"

It's like looking at a house that a "professional" painter recently
finished painting and commenting on how sloppily he cut in the
trim around the windows, the fact that there is paint on the
glass, paint on the ground, the mismatch of colors on two adjacent
walls, etc. And, when questioning him, he replies "homeowner wanted
it done 'on the cheap' so I didn't bother with all the prep work,
cleanup, color matching, etc."

OK. But, then, when you visit him at his folks' house (or his own)
you notice the same slip-shod workmanship! But, now his "excuse" is
"I did the job for free; why should I bother with those annoying details
that take so much time to do properly?"

I.e., you've got an opportunity to *shine*; to create something
with no "arbitrary" constraints beyond what your own abilities
impose. And, instead of rising to that occasion, you *sink* to
your typical level of performance.

I like the idea of producing quality work/products. It makes more sense
to do it better the first time, I think.
It's the old, old question. "Why is there always enough time and
money to do it twice, but never enough to do it right?"


Exactly! I like to design various things, and usually create a
prototype first to work out the kinks before I create something for a
client. Solving design problems is fun and seeing the solution in the
finished product is really satisfying especially when the feedback is
what I was expecting from a good design.
--
Maggie

"That's too expensive. You shouldn't make it so good, it won't be used that much and we are going to produce a lot of them."......later on,"Hey! Why the frak did this thing come apart while I was using it?! What's the matter with you, I thought you knew what you were doing?!" BTDT ^_^

[8~{} Uncle Design Monster


I like to test my own products first and I'm pretty critical of how I
want things to work, and especially STAY together!

--
Maggie