Tricky Dicky
New member
Bit of RPG
Wish I'd done some RPG - only for the reason that they're my initials !
Bit of RPG
I can understand why you'd say that but have to say that I disagree. I'd say the main advantage of compiling in C++ is the processing speed, and the control you have of memory management which, say, the Java garbage collector otherwise handles for you, sometimes with unpredictable results.Anyone that programs in C++ is a professional in my book.
I can understand why you'd say that but have to say that I disagree. I'd say the main advantage of compiling in C++ is the processing speed, and the control you have of memory management which, say, the Java garbage collector otherwise handles for you, sometimes with unpredictable results.
However, I really do think these benefits can actually mask a crap programmer. For example, what good is it saving nanoseconds in processing if you can't write a decent database query (this is often where you want your speed!) or if your app falls over all the time?
I find that most of the main languages (All the "C" languages, VB, Java, Perl, Python, etc) these days are so similar that once you have a good knowledge of general programming techniques and a comprehensive grasp of one language, then you can pick up and run with code from any of the others after just a little bit of studying the syntax. Much of the true "art" in programming has been removed since my early days of writing raw machine code back in the late 80s/early 90s.
Last point, I detest the number of people who think they can program, either because they can read and maybe alter slightly someone elses code, yet haven't got a clue about code structure, creating re-useable code in library functions, coding standards, etc. Just because someone can copy/paste an example from the web and get something which 'sort of works', that doesn't make them a programmer. There are far too many amateurs posing as 'IT Professionals' IMO.
I'd like to make a point, I detest the number of people who think they can program, either because they can read and maybe alter slightly someone elses code, but they haven't got a clue about code structure, creating re-useable code in library functions, coding standards, etc. Anyone can copy/paste an example from the web and get something which 'kind of works', but that doesn't make them a programmer. I think there are far too many amateurs posing as 'IT Professionals'
has no one ever used Fortran?
Not a traditional language as such, but I'm fascinated with XLST.
Me too - XSLT has provided me with hours of fun (how sad!). I had to learn XSLT for work - using it to transform XML to HTML for a on-screen checklists for a Workflow system.
Now with a little easy training, anybody can create new checklists with simple XML which incorporate CSS, regular expressions and Javascript without having to know anything other than a few simple rules.
She got about didn't she.Played around with perl a bit, ten years ago, then got sidetracked again
Cheeky. Did she like it? Did it effect her singing?I dipped my toe in to Perl
Purists will argue that the latter two are scripting languages, not programming languages per se...
an odd thing for "purists" (snobs?) to say, as both Perl and Python are full featured programming languages. scripting defines a use case for which these langauges are particularly suited.
The problem I have most is with "business analysts" who don't understand the development process. They may argue "they don't have to" - but I massively disagree.
tell me about it. i was on ISEB course and in a room full of project managers and business analyst and there was only one other technical person. i recall most struggled with the ERDs and one lady didnt have any concept of a database. what i learnt most from the course is that business analysts are taught *not* to think about possible implementation and solutions, just thinking about business requirements and process. i've concluded the solution design is for systems analysts, a distinction i was never able to quiet make before so it was usful. of course the problem is many projects dont get both types of people involved, so either the requirements or the solution gets borked...