Home > Development > My Legacy

My Legacy

In July 2004, I was offered a development job by a start-up firm I will refer to as ‘ABCD’. I was sorely tempted at the time, however ABCD were undergoing a round of funding at the time and they couldn’t guarantee when I could actually start.

In August 2004, I was offered another development job, this time by a three-year-old firm I will refer to as ‘Acme’. Acme had a small team of developers already, were offering me the same salary as ABCD, and would let me start work as soon as internal issues (relating to the individual I was succeeding) were resolved.

In September 2004, I took a job working for Acme. A Delphi-based software house, the managing director was astute enough to realise that they were blindly following a dead platform, and I was tasked with leading the company’s development forwards. Within a fortnight, all the developers were on a course to assist them with transitioning to VB.net, and my work had begun.

Since then, I pride myself on the way that I’ve pushed the development within the company forward:

  • The code was overhauled completely, migrating to VB.net where possible or providing (with a view to eventually ending) support for clients using existing Delphi software.
  • As each new version of Visual Studio was released, it was evaluated and software slowly migrated onto it for continuing support.
  • Where possible, applications were migrated to the latest version of the .NET framework itself, and to updated versions of SQL Server to take advantage of newer features.
  • Seeing the potential drop in support for VB.net both from Microsoft and the community in general, I started learning C# in my own time and within a week was easily able to convince the MD that, for the benefit of future recruitment and support, all new projects should be written in C#.
  • Spotted the advantages of object-based database models, and as soon as was viable dropped our database layer in favour of Microsoft’s own Entity Framework, giving us access to toolsets including LINQ.
  • Saw the ease in which MVC allowed the splitting up between development and user interface work, and (having rejected the original asp.net MVC and MVC2) evaluated then adopted MVC3 for all future work.
  • Kept track of best-practises, and whilst never dictating rigid development standards still ensured that all code would be written in a manner familiar to any other team member.
  • Continuously educated the ever-changing development team about key aspects such as software security and encryption.

A year ago, a new member of staff joined the company. Claiming to have prior experience in development, he assumed the role of project manager whilst claiming a job title giving him overall responsibility for IT and Operations. It is this individual that I refered to in my previous posts of the Security Moron.

Within a week, he had sent around his former employer’s Development Standards document with a recommendation that we adopt it; not only was this document related to his former employer’s business but it also explicitly ruled out processes and procedures that we had adopted and were actively using, whilst making further recommendations that were nonsensible in our type of business.

Since that time, his input into development, albeit not as a developer but as an operations manager, have increased as his failings as a project manager have became apparent. I have already documented his failings related to security, but when it comes to development he required that certain processes become self-contained modules of work, with little understanding of how these could work in practise or of the downsides associated with them.

His plans for a ‘central audit module’ bore no relation to reality and thus when one was implemented to his requirements it was so non-specific that any output required further work, whilst the ‘security module’ written to his specification actually managed to increase development time considerably and leave code significantly less maintainable that if we had done without.

The one project that he was placed in sole responsibility for from start to finish is generally regarded as a flop; well over budget and currently on the verge of cancellation due to incomplete requirements (that I had been assured many months ago were “100% complete”). Today, we have been given notice by a client that I personally have serviced since my first day that they were taking development in-house after a year of incompetent support under his care.

Furthermore, the company as a whole is following a business model that I specifically recommend against in my previous post ‘Unsupportable Success‘; the managing director is willing to take on any work involving a support contract with no consideration as to who provides the support or even the hours that the contract covers.

A month ago, I was approached by a recruitment agency; a client of theirs were hiring and I may be a good fit for a role they are filling. Persuing this further, it turned out that the client were none other than ABCD (although the agency were unaware of my previous contact, and ABCD themselves had changed so significantly that my offer was a documented, but otherwise unmemorable, blip in their past). The interview went well – so well that, half-way home I received a call from the agency asking me to turn around and return for a second interview that same evening.

As of yesterday, it is now public knowledge within Acme that I have accepted an offer from ABCD. Within an hour, I was excluded from the ‘development team strategy’ meeting, and from now on the development within the company will be pushed forward by the Security Moron.

I had hopes, one day, that when I left Acme I would leave some sort of legacy, in that someone else would take over and push the development team forward in the way I have: my team contains a number of people, each of whom could easily fulfill that role. It is a standing joke within the team that everything the Moron suggests is prefixed with ‘in my old company…’, and the weakness in his technical skills are obvious to all. But with him assuming charge of development, any change will be despite, rather than because, of him.

I no longer have faith that the company will progress. I no longer believe in Acme. I will miss the people here, but I will not miss the company.

Advertisements
Categories: Development Tags: , , , ,
  1. October 21, 2011 at 2:08 pm

    Without wishing to be too girly; I am so sad at this situation. You have left a legacy and those people in your team have learnt under your mentoring and guidance. You could do no more and have bowed out at the right time,

  2. October 21, 2011 at 2:50 pm

    Perhaps when ‘ABCD’ are looking to recruit you could poach a few of your old team from ‘Acme’ and at least give them a chance to join a company with a future?

    Bad management sucks and it’s the number one reason I left my first 2 jobs. The 3rd job was amazing but American head office shut us down as we didn’t fit into their 10 year plan… 😦 The management team were great there – they knew their roles and their personal limitations and that meant silly things like this didn’t happen…

    MaFt

  3. October 21, 2011 at 3:29 pm

    Congratulations on your new job. The Security moron will never last. Sooner or later something will happen and the MD will realise what a waste of space he is. I can emphasise, I’ve seen people like that in the IT company I work in on a massive contract. He botched it up and not only damaged the customer / client relationship but has risked future projects too.

    Best wishes in your new adventures!

  4. October 21, 2011 at 3:34 pm

    Why hasn’t the MD got rid of the Security Moron?!? Good luck in your new role!

  5. Anon
    October 22, 2011 at 10:39 am

    I was going to comment under my twitter username but I don’t want to give away “acme” too obviously.

    But I know you know who I am.

    For others, I was one of the developers in acme when the author came to the company, and was retrained from delphi to VB.NET. It was my first development job out of uni. I left the company in 2005 and have gone on to have a (relatively) successful software development career (I am still with the company I left to move to, progressing over the years through the development roles to lead a team and have a decent input to architecture of my product).

    I’m commenting because I want you to know;

    *I also appreciated you as a mentor and role model, I can imagine how your developers must be feeling as I was once one of them so can easily put myself in their position. But I would also understand your situation, and that you need to do what is best for you. I would say keep in touch (and like MaFt says, perhaps I would be thinking of following)

    *I think the MD is nuts to have let the situation develop to the point of allowing you to leave the company. I’ve followed your frustration on twitter and have been amazed at how you are not properly appreciated. But it doesn’t surprise me. I left because I didn’t feel appreciated, I knew I was a good developer, that good developers are hard to find (after involvement in recruiting developers in the years since I left, GOD are good developers hard to find!), that I wasn’t being fairly paid/ appreciated, the MD didn’t agree so I had to leave- but I didn’t really want to.

    *I can see that it must be very frustrating to see what is happening in the company. You’ve given a lot. But let it go. I hope writing this post has been cathartic and now you can let it go and move on. Embrace the new challenges ahead. Whatever you see happening in acme before you leave, whatever the security moron gets up to, rise above it. It’s no longer something you can influence, so it’s not your concern.

    Guys like me are part of your legacy! Wishing you all the best at ABCD

  1. November 17, 2011 at 11:19 pm
  2. March 22, 2012 at 1:58 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: