This reminds me of my GCSE Systems and Control. I opted to make an electric violin! Essentially it consisted of me foolishly sanding a piece of wood for 2 years until right near the end my uncle swooped in and helped me make a fully working electric violin out of an old park bench. It turned out to be an excellent project. I think I still have the basic shape of the violin somewhere. I'll have to get it out and post it at sometime. I am sure there could be money made in custom making them to order...
This happens regularly to me (and from my anecdotal investigation everyone involved in large / old projects). We need a new piece of functionality. I write it, it's beautiful and I win the internet. I have estimated 8 days (or 22.23 lol-points depending on how you live) and it's only taken 4 days. Ah, but then a very small; mostly ignored and very unimportant detail rears it's cruel head. You need to make it work with the code that exists already. This is normally in the form of saving to some pre-existing entities. Oh dear. You save everything through the various management / service classes that exist already and nothing works. So begins the next couple of days of horror. You find that you didn't set the work = true . Most of my woes in this area are caused by modifications at layer further down (or the stored procedure it finally ends up in) changing the object that I was trying to save or not saving part of the object because of some rule. So many errors
Comments