Lead PHP Developer Quits
Jasper Bryant-Greene writes "Jani Taskinen, one of the lead developers of the Zend Engine (the engine that powers PHP), as well as a lead developer for the thread safety system and other core components of the PHP project, has quit in a relatively cryptic message to the php-internals mailing list. Jani has been involved with PHP for about 6 years and his loss will undoubtedly be a big blow for the PHP project."
From: Jani Taskinen
Date: Thu Jul 27 20:28:45 2006
Subject: Good bye.
Groups: php.internals
I never spent 6 years with the same people, job, hobby, women, whatever...
You only need threadsafe PHP (gettext, gd, etc) if your webpage has more than 1 concurrent user.
Only pages with more than 1 visitor need to ca.. OOPS!
-Woof woof woof!
Harsh words, sounds like there is some personal conflict involved. Or maybe he just got tired and wanted to move on to something different. Best wishes to all involved anyways.
Unfortunate for the Zend team, but I'm sure it won't be the death of PHP. There are many other developers, and you can still run PHP sites with other engines, for instance, the Quercus engine in Cauchos Resin I'm sure there are similar modules available in the mono/.Net world and others.
Being bitter is drinking poison and hoping someone else will die
But that was at a php conference...
Why is it such a shock to some that a developer got burned out working on the same code. Open source developers are often not appreciated. A few get paid and many don't. Its just constant nagging for new features or bug fixes. There are rewarding aspects too. Maybe he wanted to do something with php that hasn't happened. He was involved with thread safety and that hasn't seemed important to many people. Personally I'd like to see thread safe php so I could play with some of the apache mpms...
MidnightBSD: The BSD for Everyone
Jani "sniper" Taskinen
Jani worked on the PHP core and the Zend Engine.
Jani has contributed to php.net in the following ways over the last 12 months:
* as a lead developer for Zend Engine II
* as a lead developer for TSRM (Thread Safety Resource Management)
* by testing and maintaining the build for the PHP core
* by writing/maintaining tests for the standard functions in the PHP core
* as a lead developer for gd, a core extension
* by working as a developer on imap, a core extension
* by working as a developer on session, a core extension
* by working as a developer on sockets, a core extension
* by providing occasional fixes for the testsuite distributed with PHP
* by applying maintenance fixes to the underlying libraries in bcmath, pcre and xmlrpc
* by providing tests and occasional fixes for xml
* by providing occasional fixes for apache2filter, apache2handler, apache_hooks, cgi, cli, dba, dom, iconv, informix, isapi, ldap, mcrypt, mcve, mime_magic, msql, mssql, mysqli, mysql, ncurses, oci8, odbc, openssl, oracle, pgsql, recode, snmp, soap, sqlite, sybase, tidy and tokenizer
* by writing/maintaining tests for mbstring, mhash, pcntl, pspell, shmop and wddx
* by working as a developer on bugs.php.net
Now get back in the holodeck and strip.
Maybe we should stop wondering about him. For all we know, he's got problems with other things in his life. Let's stop making assumptions about the poor guy. If I was Jani and saw all this psychoanalysis going on about me, I'd definitely tell whoever was doing it to shut the fuck up.
I make websites and stuff. Buy one.
Let me get this straight. People are making pretty nasty judgments based on one terse post that may or may not be legitimate. And in that moment we forget and discount everything he has done over the past six years.
As a volunteer he gave a great deal back to the world. You call him childish. I say he is entitled to walk away without having to explain himself.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
It's not that different from what adults do though.
Recently, I read an interesting book by a psychologist named Paul Eckman. OK it wasn't an interesting book, it was a tedious book on a fascinating subject.
A couple of the takeways from the book: emotions are persistant mental states that are triggered by situations that bear on your future well being, and in turn trigger certain stereotyped survival related behaviors. In an emotional state, people do not process new information that would contradict the survival behavior. In other words, once you get to fighting, or to running away, you aren't going to listen to reason until you've fought it out or have run far, far away. The psychologists therefore call emotional states refractory, which is a word I learned from EE "Doc" Smith which when applied to metal means hard to work and when applied to a state of mind means hard to work with.
I've sometimes seen job listings looking for people who are passionate about their work. I'm not so sure this the right thing to look for unless you are looking for a short term employee. All jobs involve having your desires frustrated from time to time. As your emotions build up, your ability to process new information and ideas that could help you overcome your frustrations is diminished, because atavistic survival behaviors related to conflict and survival begin to strangle your productiivty.
In that case, the best thing is to take yourself out of the situation, which in all liklihood your own behavior contributes to.
You can take two people who are miserable and underperforming in their jobs, have them swap jobs, and suddenly they'll feel a great relief and surge of productivity, as they work flexibly around the exact same kinds of problems that had them stymied in their original job.
Unless you're some kind of Zen master you're going to run into this sooner or later. When you reach the point where you can't perform up to your potential, even your potential as defined by the less than perfect work situation you're in, it's time to move on. This is probably why academia, infamous for its harsh and pointless politics, evolved the institution of the sabbatical. But for the rest of us, this means quitting and getting a new job.
The emotions expressed in the email are probably universal. They do not in themselves indicate immaturity However, one thing that you do learn as you get older is when you feel strong negative emotions towards other people, hiding them is the best first reaction. In most cases you cannot change other people, especially if you are terminating your relationship to them. So the best you might hope for from negativity in the way you do this is some kind of catharsis, or perhaps some kind of public vindication. However experience teaches you don't often get those, and when you do they aren't as satisfying as you imagined them being.
Above the simple futilty of showing your anger and disappointment, expressions of strong negative emotion evoke an equal, if not stronger reaction from their targets. Often this ignites a round of petty retribution that comes back to haunt you.
So when it becomes impossible to deal with the emotional climate of work, leave. But always leave with a kind and magnanimous word. In the end that serves you best.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
From reading the mirrored post above it just seems terse and upset, but not really cryptic. Cryptic is stuff like "beware of the dwarf" and "under a big 'W.'"
Slashdot Burying Stories About Slashdot Media Owned
He's finish(ed) :-)
No no, that is not possible. He is a PHP developer, he can't possibly be lacking in security awareness!
Its just constant nagging for new features or bug fixes
...
Personally I'd like to see thread safe php so I could play with some of the apache mpms
Unless you're some kind of Zen master you're going to run into this sooner or later.
Well, he is apparently a Zend master!!
Burnout is a very commom symptom in all kinds of volunteer organisations, open source being one of the ones see more about on Slashdot.
The causes are quite straight-forward. When we do something for other people, we need some kind of reward. It can come in many forms - appreciation, money, reputation, status. The best rewards change over time and are a good mix of all these.
Open source projects consume people, with demands on their time, social life, professional capacity. The only rewards tend to be reputation. Depending on the invidual's personal life and other demands (family, job), they can sustain a heavy open source project for a few years, and as many as five or six. At some point, it either becomes a profession (with a wage) or a problem.
All volunteer organisations have this problem and it's exacerbated by peer pressure. If everyone else is spending 80 hours a week hacking, then it seems normal to spend 81. At some points, open source projects can seem like cults, and unintentionally adopt many cult techniques to keep people involved, whatever the personal cost.
(Those techniques include isolation from family, use of secret languages, separation from real time and real life, etc. I don't *think* any OS projects do this on purpose, though I have my secret doubts about the FSF. Just kidding, Richard!)
I've seen burnout cases so severe the persons involved were literally sick, unable to function normally any more, and needing psychiatric help. In other cases it's project-specific. I've had this on open source projects, where after five years I've just abandoned the software, telling the users, "sorry, it's not working any more".
Each person has different needs, but eventually if we don't get what we need, we get sick. Young people are especially vulnerable because they don't understand their own needs very well and neglect them easily.
The upside is that burnout is easily cured by a change of scene and some tangible rewards. Some people even come back to projects they've abandoned, but it can be very difficult. A good dose of selfishness ("what do I need in order to feel happy NOW") is always useful, and a good self-protection measure in many environments, open source groups included.
My blog
I found these:
http://marc.theaimsgroup.com/?l=php-dev&m=11329681 6720289&w=2 5 7711671&w=2 0 9820157&w=2
http://marc.theaimsgroup.com/?l=php-dev&m=1153255
http://marc.theaimsgroup.com/?l=php-dev&m=1153312
...which hint at conflict. Maybe one of those blew up in a way he didn't like. However, I don't think those really are the issues. I would guess it's something off-list. It's too bad. I have friends working at Zend. You never want to see someone so useful walk away.
I must admit that I'm impressed with the mailing list -- Jani said "don't reply" and nobody did. They're either a disciplined bunch, heavily moderated, or Jani's leaving just didn't have much impact.
-Tony
My Greasemonkey scripts for Digg &
Sarchasm: This weather is far worse than Hurrican Katrina
Actually, sarchasm is the gulf in understanding between someone who makes a sarcastic statement, and someone who doesn't get sarcasm.
Sarcasm: "This weather is worse than Hurricane Katrina!"
Sarchasm: "What are you talking about? Hurricane Katrina was a major disaster, this is only a heavy rainstorm."
Both your examples demonstrate sarcasm, not irony. Irony is when the person responsible for the threading engine of a server-side scripting language resigns, and nobody can read his resignation letter because the server is overloaded.
I think many of you guys need to readjust your sense of proportionality. This guy has most likely done more to both world peace _and_ open source world than 99% of the whiners on this forum.. and now you are mocking him for not revealing some interpersonal issues and saying ill-considered things in chat *once* when obviously being out of his mind.
Consider this. That guy has
1) worked deeply on a project for six years and has just made a decision to quit it,
2) has just lost a coworker in a bit questionable series of events,
3) is obviously depressed or burned out or both,
4) is constantly under threat while serving in hostile country with no infrastructure of whatsoever and having to remain calm and peaceful while in desperate situation and underpowered,
5) has had harder than normal time in service past six months and
6) people are blaming you for not answering their *software project* emails fast enough, when you have been busy with things 4 and 5.
If you can say you have experienced even *half* of these, let alone simultaneously and are willing to come up and admit it, *then* I can take you seriously when you come and say that you didn't say anything unprintable in that situation. Maybe.
And also remember: english is not his native language. It's more than a bit hypocritical to judge someone you have not even met by his writing in *chat* in *foreign language*, especially when the chat log is spread without his consent by someone who is not willing to reveal his name, nor the context of the discussion.
http://iki.fi/zds/