When coding was a skill

[d000hg]

Hmm, I've seen plenty of people who somehow managed to learn enough C to pass themselves as coders while being very shoddy. I don't know how they managed it in such an unfriendly language, and they're far more more dangerous than someone hacking in JavaScript

I do absolutely agree with you though that knowing all this low-level crap is a brilliant foundation for a developer - knowing binary & hex, understanding array indexing and what a reference/pointer means are all basic bits of knowledge I use in every language I ever used. I'm very happy that I don't have to manage my own memory C#, but knowing it's still going on underneath makes me write code more in line with how the hardware works.

[suityou01]

Hmm, I've seen plenty of people who somehow managed to learn enough C to pass themselves as coders while being very shoddy. I don't know how they managed it in such an unfriendly language, and they're far more more dangerous than someone hacking in JavaScript

I do absolutely agree with you though that knowing all this low-level crap is a brilliant foundation for a developer - knowing binary & hex, understanding array indexing and what a reference/pointer means are all basic bits of knowledge I use in every language I ever used. I'm very happy that I don't have to manage my own memory C#, but knowing it's still going on underneath makes me write code more in line with how the hardware works.

Preshishely.

[Lockhouse]

In the old days on mainframes you had to do an 18-24 month "apprenticeship" before you became really useful. During that time you learnt how to do things properly - if you didn't things would get screwed. There was nothing available where you could "knock something up in two minutes". In fact I remember on my first contract only being allowed one compile a day due to machine constraints which focuses the mind somewhat - especially when up against a tight deadline. It teaches you to get stuff right first time in a structured way.

That sort of start in IT simply doesn't exist any more and I firmly believe the "training" I recieved then has not only stood me in good stead ever since but explains why there is no younger, fitter generation snapping at my heels like there should be.

[VectraMan]

I do absolutely agree with you though that knowing all this low-level crap is a brilliant foundation for a developer - knowing binary & hex, understanding array indexing and what a reference/pointer means are all basic bits of knowledge I use in every language I ever used. I'm very happy that I don't have to manage my own memory C#, but knowing it's still going on underneath makes me write code more in line with how the hardware works.

Agreed. Scary how many new people don't feel they need to know what a byte is, or a pointer ("my language doesn't have pointers, it has references" ).

Saying "I don't have to manage my own memory C#" is a good example. Whilst that may be true, there are pitfalls. Like for example adding something to a list, and forgetting to remove it, which is effectively a memory leak. The C#/Java programmer doesn't spot this stuff because "memory management is not my problem", whereas a C++ programmer would.

What everybody should have to do is write a compiler. Then you understand what's really going on behind the code you write.

[singhr]

There was a time when I would start a new program with a trip to the stationary cupboard for a new pencil and coding pad and write the words 'IDENTIFICATION DIVISION'........ happy days

[minestrone]

If anyone thinks that knowing about pointers and memory allocation makes them a better programmer these days then they are sadly deluded. Times have moved on and programming is much more than knowing how many objects are floating about on the heap now.

[sasguru]

Yes, yes but unless you are actually creating software for a software house, or writing mission-critical support software, what value are you adding to your client?
That's the question that should be obsessing you if you are a real business and IMHO it's the problem with most techies* - they're always up their own arse about their particular technology, as if it matters in the greater scheme of things

HTH

* I used to be one too.

PS Everyone in IT should be approaching their work from the point of view of the business. Understand the business, then ask how you can use IT to add value to it. The particular technology doesn't matter - attachment to a particular tech is a weakness.

[uky kozak]

I sell code to clients for £1000's and get you to write the code for pennies. Now in my eyes i am the better coder.

[DimPrawn]

Code?

What's wrong with drag and drop?

[sasguru]

Code?

What's wrong with drag and drop?

If it does the job, nothing at all.