andrewducker (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
andrewducker) wrote2003-06-06 04:22 pm
andrewducker) wrote2003-06-06 04:22 pm
Programming
Well, the subject line has probably gotten rid of most of you, and this next line will almost certainly get rid of the rest.
I'm learning C#.
Right, now I've got this journal to myself (and boy, does it feel spacious without anyone else here), I'll explain why (to myself, obviously).
I've been meaning to get back into programming again, but the little bits of dabbling I've done have largely been hampered by the fact that I've not really had any projects I've been that interested in. Not only that, but I'm very, very bored of doing low level work - writing yet another bit of code to deal with files, or fiddling about with endless calls to do the simplest interaction with the outside world just doesn't interest me any more.
Also, having been programming in COBOL for the last 9 months, and having always been envious of the Visual Studio IDE when I was working in VFP (it's a fantastic IDE and does all sorts of things that are just smooooth), I thought I should work with something in that.
I can't be arsed doing garbage collection, and I wanted something that would allow me to easily write/read web services. Which leaves C#, which (by sheer coincidence) has the nicest IDE of the entire of VS.NET.
I've been working my way through Visual Studio.NET Step by Step, which has so far been very good. I've only spent a few hours on it so far, and am about 40 pages in, but the power of the system is already very apparent. The fact that I can great a GUI interface by dragging and dropping a few textboxes onto a form, then go into the code behind the form, alter the position of the items in the code-based declaration and then go back to the screen to find it's automatically updated itself is something I would have killed for a few years ago.
The XML commenting system, the collapsible procedure view, the fact that the compiler messages are actually useful and the intellisense basically make this the best environment I've ever worked in. Erin's away for the weekend and I have to say I'm looking forward to spending most of it in front of the computer, typing away.
I'm learning C#.
Right, now I've got this journal to myself (and boy, does it feel spacious without anyone else here), I'll explain why (to myself, obviously).
I've been meaning to get back into programming again, but the little bits of dabbling I've done have largely been hampered by the fact that I've not really had any projects I've been that interested in. Not only that, but I'm very, very bored of doing low level work - writing yet another bit of code to deal with files, or fiddling about with endless calls to do the simplest interaction with the outside world just doesn't interest me any more.
Also, having been programming in COBOL for the last 9 months, and having always been envious of the Visual Studio IDE when I was working in VFP (it's a fantastic IDE and does all sorts of things that are just smooooth), I thought I should work with something in that.
I can't be arsed doing garbage collection, and I wanted something that would allow me to easily write/read web services. Which leaves C#, which (by sheer coincidence) has the nicest IDE of the entire of VS.NET.
I've been working my way through Visual Studio.NET Step by Step, which has so far been very good. I've only spent a few hours on it so far, and am about 40 pages in, but the power of the system is already very apparent. The fact that I can great a GUI interface by dragging and dropping a few textboxes onto a form, then go into the code behind the form, alter the position of the items in the code-based declaration and then go back to the screen to find it's automatically updated itself is something I would have killed for a few years ago.
The XML commenting system, the collapsible procedure view, the fact that the compiler messages are actually useful and the intellisense basically make this the best environment I've ever worked in. Erin's away for the weekend and I have to say I'm looking forward to spending most of it in front of the computer, typing away.
no subject
I spend a lot of my working life doing Access apps which are heavily dependant on VBA and uses a very similar environment. All the little things sound silly, but stuff like auto-capitalisation of declared vaiables (easy to spot if you mis-type them) make a big difference to the grind of churning out code. I love coding in Access for much the same reasons you cite for C#. Its just so easy to knock together a simple and powerfull GUI based tool. Ok, the Jet engine sucks as a back end, but you can always code round it or just use another engine.
But then I sold my soul to the MS devil years ago.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
cos i have two for you
You said your self you have never wwanted more bandwidth since using waste, well, means it got your attention?? anyway, as we have seemn waste has a few issues.. so write one, that will recognise a file on many servers, like kazaa, but allows workgroup level sharing like waste, but with throttle ability, so the user can divert the bandwidth to the connected user they choos, not that the software chooses??
would get round the issues we had, and the issues I have with bandwidth, and would fix the issue guy and I had... sure I can think of more.. but I think the hrd bit will be stoping and starting downloads of a file and worse from many machines..
the other, is write the webserver side of the kensington game.. since i'm crap, and havn't started.. I realy want to write the AI bit, that communicates to the web server via a web service, since i need to try this web service thing out.
no subject
HELLO
Delphi did that!
no subject
I really should be doing C# (despite the fact that they have just started doing VB.Net here [not me, though, but peculiarly the dept head. I am not even going to speculate on that one). I know a fair bit about the internals of .net and the frame work but I can't find a book that is for experinced programmers. Well, Deitel&Deitel do one whcih Sean has, but 'experienced' to them appears not to mean experienced in Windows (or indeed even GUI programming of any sort)!
I so seriously need (from a CV point of view) to be doing .Net in my daily work. I will bring this up big style in my next rquarterly review.