?

Log in

No account? Create an account

Previous Web | Next Web

3rd Mar, 2007

-pfft-

My head is broken. Its just not working properly... once upon a time, writing code was easy... at the moment, its a terrible struggle.

See, there are to things I can usually do when my brain is reasonably functional. Firstly, I can "see" a routine or algorithm without having to really *think* about it... it may not be the absolute 100% optimal version, but its usually pretty good... and I usually manage to mould the sub-optimal version to be closer to optimal while I'm implementing it. And secondly, I can keep a reasonable picture of the overall system in my head while I'm working... not a detailed picture of everything it does and so on, but I have, lets call it a 'notional view' of things... this means that I know a change to thing A means I need to modify things B, C and F to take account of the altered behaviour, but things D, E and G will be fine. Alot of this is basically just keeping in mind what entrypoints exist into structures and which of those entrypoints get called from where, what they return, etc...

Problem is that neither of these abilities is currently functioning... and once you're used to working in a way that uses a certain ability, its really hard to work without it...

So, yeah, I'm working on a GUI-driven app in VB, which means that everything is object-oriented...

Remember, this is a language that not much more than a month ago I'd never written a single line in, except through coincidental similarities to other BASIC languages... I'm still finding the limits and quirks of the VB way of doing things... (actually, that isn't 100% accurate; I suppose that, more specifically, its the VB.Net2 way of doing things) which means I keep running into dead-ends between how I've worked something out on paper and how it can actually be done in the language... and I'm spending alot of time wading through the MSDN documentation... which has all *sorts* of stuff in it and isn't particularly targeted at the installed version of Visual Studio... there are notes on VB6 and others in there too... and since VB6 to VB.net scrapped various things (apparently including atleast one thing I wanted to use -grrrr-) this makes it rather hard work to make sense of

Now, I know that OO should wrap everything up inside well defined interfaces and that the changes inside a class shouldn't have any noticeable effects outside of it... and that's fine... if the interfaces aren't what you're having to tweak...

So basically its taking *AGES* to write even tiny bits of code cos I can't just jump from concept to code like I normally would, and then its taking ages *more* to revise changes in class interfaces cos I can't remember everywhere the particular aspect of the interface is in use... and by the time I find it (iow, the compiler has run), I've lost track of exactly how I need to modify things....

If programming were this damn difficult, I'd have never gotten into it!

And yes, this is code that might get me paid... and the above is how its going, and also why its taking so long to finish.... its SO frustrating... if my head were working, I suspect that the whole project would be a few days work... basically the time to type it all in, tweak it, test it and mess around with the installer side of things would probably be about a week.... not a month and more and still counting :-(