Some will know that I was leaving my existing job after 8 and 1/2 years and was looking for a new job. Well that time has come and I finished up with my existing job yesterday. It was because of trying to tie up all the loose ends on that job, that have been neglecting mod_wsgi for some time. There was also somewhat a lack of motivation as well.
Hopefully that will now change as I start today in my new job. I still have to work out how I fit in doing work on mod_wsgi, but the new job is going to entail some serious programming and so expect a renewed enthusiasm to come from that. Working from home for this new job will also hopefully give me a lot more flexibility to schedule my time so I can do stuff with mod_wsgi again. What is the job? Well, I wasn't sure whether I was going to be able to say for the time being at least, but turns out there isn't an issue. I therefore can tell you all that am going to work for a company called 'New Relic'. I'll not say exactly what I will be doing, but if you know anything about what New Relic does or go read about their products, you can see what this could mean to the Python web community. It will also help me in being able to answer all those questions from people about how best to configure Apache/mod_wsgi for best performance. So, even if I am still slow in respect of further development on mod_wsgi, working on this other stuff will more than make up for it. As you can imagine, I am quite excited about this. :-) Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
