Ideas Overload

At the moment, I’m a bit swamped on the ideas front. It’s not an unusual occurrence, to be honest – but it means I’m trying to stick with some vague kind of prioritisation (is that a word?) in order to get things done, and to get those ideas out into the real world.

At the same time, there’s also several ongoing projects for clients as well, which makes things slightly more interesting. I’ve been working through those as well (and there’s at least one still waiting that I should have completed a long time ago) because they’re paying jobs, whereas the ideas I’ve got may make money, but certainly won’t do so straight away – if ever, in fact.

I do like getting these ideas out of the way – and indeed, they’re all part of that much-mooted five-year plan I’ve been banging on about for the last two years or so – but I’d be just as happy to only have one idea at a time, rather than the four or five that are currently floating around at any given time. Sometimes, keeping track of them all isn’t exactly easy, although I don’t mind too much in general. I know that writing them down would be counter-productive (as I whittled about last week) so keeping them in my head is the best plan. After all, if I then forget them, the idea probably wasn’t worth that much in the first place.

The really frustrating/sad/geeky part is that when I get these ideas, they come fully equipped with database setups and tables as well. And that is just a sign that I really should be getting out one hell of a lot more…


2 Comments on “Ideas Overload”

  1. Gordon says:

    Ahh you are indeed a geek. We have stuff in our product like that, borne of intellect. Trying to get those chuffers to step back and think about the requirements rather than the DB structure or [clever code bit] is a bloody nightmare at times!

  2. Lyle says:

    Oh, don’t I know it. Although that is the benefit of being one’s own client on that score – the communication channels are remarkably short!

    But yes, I can’t deny, I have issues with writing down a structure according to some kind of plan, only to have to then do it properly in SQL later. I’d rather write it out once, do the job, and then if additional requirements come in, make amendments.

    At the same time though, give me a set of requirements and I’ll happily work towards them.


Leave a Reply

Your email address will not be published. Required fields are marked *