Archive for July 2012
If you work for a big company chances are that the organisations structure is quite big complicated with many divisions some of which might be independent companies themselves. With many people in different positions with different goals comes politics.
Building architectures for such corporations has to follow.
Last weekend Bernhard wrote a new blog post on the official Symfony blog about the revamped form component in Symfony 2.1 and apparently it’s no longer backwards compatible. This is not really surprising as not everything in 2.0 was marked stable not was everything included in that release that is meant to go into Symfony.
Still BC breaks like this should make you think before you act.
One of my many colleagues within the company I’m working for once built a very cool an powerful service some years ago. So powerful and architecturally elegant that most of our websites use it and are heavily dependent on it. I wouldn’t know to point out a single flaw in this technology.
Other than available maintenance ressources.
Any good project starts out with a nicely shaped idea. Then they are transformed into single steps as user stories or tickets or whatever and then implementation follows.
Each of these steps are prone to wild growth. The while-we’re-at-it syndrome.
Today after lunch I was chatting with a colleague about some of the business models we see applicable in the content publishing industry. One of the models that almost all publishers try to implement one way or another is paid content.
Only I can not see that happening..
Currently entering the fourth sprint I thought it would be a good time to give an update on being a product owner. Part-time that is as I can spend only some percent of my time to this project while I’m involved in many others at the same time.
However I learned that Scrum actually nicely allows myself not paying attention.
As probably most of you experienced yourselves I recently have been asked to create a website for a friends business as a favour. It’s going to be just a simple website. We’ve all been there and we know what this could lead to.
Now how to reduce the risks?
There are many important things to consider when choosing a job. The work itself, chances to be successful, a certain level of freedom, your colleagues and a whole lot more.
One more thing to look out for is a great boss.
One of the websites I am responsible for is quite old and there is no budget to revamp it. It’s a content website that only one editor is actively working for so resources are limited.
So I started to get rid of a few things.
A few days ago I revisited one of my professional profiles and I stumbled upon a small text I wrote several years ago in a category called “wants”. It still fits my expectations today.
..and it was eye opening to read it.