Skip to main content

PJE, I Have Little Time For What I Don't Prefer

Phillip J. Eby, I have a lot of respect for a lot of the things you right, including most of your recent posts. Dimwits refuse to learn, assholes yell at you for suggesting it, and good developers can acknowledge and embrace their faults and ignorance. No matter how much I learn I never want to think I have nothing left worth learning.

There are a lot of technologies and solutions I do not use. I'm sure all of them have their good points and their bad points, Zope included. However, I probably won't ever get to know much or anything about them. The time to familiarize myself in any valuable degree with Zope, Django, Turbogears, and mod_python is simply more than I have after using the solutions I actually apply to real usage.

Besides the things I can't find time to learn, even if I know they probably have really interesting aspects, there are definitely things I just won't learn or won't learn any more of. PHP is a good example, and many people know just how I feel about that. Yes, I might fit some of the descriptions PJE defined for people he would not hire. Asked about my worst experiences, I would likely bring up PHP and I don't believe I could have anything good to say about it. Is that ignorant of me, or is it just that bad? Maybe I just saw the limitations and before I learned real merits of the system, I moved on. Regardless, I've not locked myself into having no good answer for the interview question!

Never stop learning is a great rule to live by, but it doesn't mean you can't stop learning about particular things you deem invaluable to your precious time.

Comments

Florian said…
Yeah I guess I fall right off the PJE job grid for denying Zope too.

Though I've seen one woman who hated zope and left her job because of it and it's community. Then I was hired to hate the same job until I replaced Zope by something reliable, flexible and enjoyable.

We are passionate because we care. We care about our time and that of others. That is why those who have learned their lesson and did not stop caring like PJE voice their opinion in a clear and understandable way.
PJE said…
PHP has some important strengths as a platform; you don't have to *know the language* to know that:

1. It's widely available and rapidly deployable

2. It has a very low barrier to entry for low-skill personnel

3. There's a large amount of already-written software in it.

Does that mean I want to program in PHP? Not if I can help it, no. The shortcomings (including massive security holes) are well and widely known.

But my wife's store's website uses osCommerce, which is one of the easiest to install and use, most comprehensive low-end open source ecommerce website packages out there. It's written in PHP.

One of *my* business sites also uses Plone, even though I don't particularly like it. I use what gets the overall job done economically, not what I'd like to use if I had time to write the whole thing from scratch in an "ideal" way. Plone won out over a variety of PHP solutions I evaluated, in part for UI reasons and in part because I figured I had a better chance of being able to hack it into shape if I needed to. But there were a *lot* of PHP contenders that outclassed Plone in relevent raw feature counts.

Anyway, yeah, if somebody couldn't name or think up on the spot at least one of the PHP strengths above, they probably wouldn't have been qualified to work for me. It doesn't take a lot of imagination to come up with those, only the lack of bias.

As for Florian's suggestion that I have "stop[ped] caring", I would have to say that I prefer to focus my passion in *positive* directions. Focusing on the negative is what really wastes time and lives. I stopped developing with Zope many years ago; I don't feel a need to carry grudges about its shortcomings indefinitely.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho