Writing music is hard. I love doing it but I have yet to write a piece where I did not have significant writer’s block. What I often do is wakeup early and spend an hour or so working on a piece before starting work. I have been writing and playing music for a few years and it is still hard each time. It really is 10% inspiration, 90% perspiration. Enough so that I stopped and wrote a blog entry about it.
There has been a lot of talk over the past several years about the difference between performance and scalability. Never mind that the difference between the two will probably not really affect most developers. Never mind that the “difference between performance and scalability” argument is often used when someone’s code performs poorly and their best argument is “Yeah, but my code scales”. Yeah, sure it does.
I deployed this blog about a week ago. Since then there has been little traffic, mostly because I have not promoted it and I have also been working on a bunch of other content and such. Since I also just needed to just get it out the door and running I have not spent a lot of time testing for performance. This blogging app is based off of Zend_Application and as such there is a bit of overhead. Since I was not expecting traffic to be that heavy I was not (and am not) overly concerned about snappy performance at this point. As long as the page loads and displays in the browser I’m fine with it.
If you are reading that title and thinking “what is that guy smoking?” then you are probably in good company. Developers often make development decisions based off of philosophy. Some developers go the route of “we will decide on the best tool (language) for this individual job” and end up having hundreds of individual tools that they need to end up supporting. Others desire to take a more puritanical approach in saying that “we will only use this one tool (language) for this individual job.” The problem is that the decision is often not as cut and dry as many development philosophies allow.
So there’s been a little bit of interest in the music I wrote for Zendcon in ’09. Some people liked it, some didn’t. I remember reading some of the Twitter posts on the wall and feeling a little nervous. The sound guys played it more up-front than I was expecting. I had no idea that they were going to turn it up the way they did. It wasn’t that loud (according to Kevin’s reckoning ) but I was expecting it to be background music. So the fact that I wasn’t chased out of there with pitchforks made me glad.
I saw on our Zend Technologies page on Facebook a question on how to get a logged in user profile when using Zend_Auth. The exact question was this:
hye guys, i need help in Zend … i m implmenting web based application using zend framework the version i am using is 1.9.5 but i got a problem, i dont know how to display a user profile once he or she login into the system? anybody can help me doing so? i tried googling but mostly the code there is for zend 1.5 i guess.. wish can get it done as soon as possible
You may be wondering why there are no comments on the site or any kind of interraction. That’s because I haven’t written it yet. I intend to make the web site much more interractive but I’m also writing all of it myself. That means progress will be slow. Not because I’m slow (I might be) but because I’ve got a bunch of stuff to do. But if you have something to say feel free to do it on the Facebook page or my Twitter.
One of the cool things in Zend Framework is the Zend_Service layer. What it basically does is provide access to a variety of different service-based… well, services, so that you can easily integrate your application with other services. One example is, of course, Twitter. Often, to connect to various services you need to have an API key that you use to connect. The same is true for Twitter, except for public feed information. What this means is that you can search Twitter for free, with no API, easily.