Thread about the languages ( another one ? )
Re: Thread about the languages ( another one ? )
That's why the lord gave us cnc simulation engines that tell you if your tool path is going to destroy the machine and/or sample. Some former colleagues of mine used to do that kind of thing. They were all mathy and weird 
Re: Thread about the languages ( another one ? )
just having a chuckle at this one
http://www.reed.co.uk/jobs/digital-grap ... int%20shop
sounds like the recruiter had a load of stuff read to them down the phone...
http://www.reed.co.uk/jobs/digital-grap ... int%20shop
sounds like the recruiter had a load of stuff read to them down the phone...
Re: Thread about the languages ( another one ? )
I think I got some J pegs with one of my tents 
- gilesgoat
- Sheepie Whore

- Posts: 27259
- Joined: Wed Sep 03, 2003 7:54 am 0
- Location: Monfalcone, Italy
- Contact:
Re: Thread about the languages ( another one ? )
*SOB* .. I broken one of my tungsten carbide drill bits .. that's another 3 pounds and something gone 
Giles the billy goat
"Baa"
"Baa"
- teamonkey
- Sheepie Whore

- Posts: 12082
- Joined: Thu Jun 13, 2002 1:07 am 0
- XBL Gamertag: itsthetaste
- PSN: teamonkey_ca
- Contact:
Re: Thread about the languages ( another one ? )
Counter-intuitively, programming in Scala takes longer than in Java but runs faster.
http://www.neverworkintheory.org/?p=375
(However the test subjects knew Java but had no knowledge of Scala before the test)
http://www.neverworkintheory.org/?p=375
(However the test subjects knew Java but had no knowledge of Scala before the test)
Re: Thread about the languages ( another one ? )
That would seem to make it a worthless test, at least on the dev speed side.
If you stuck me in front of a computer and gave me some tasks I would get them done faster in python than FORTRAN, even if FORTRAN was the tool for the job.
What would be interesting is to see how well someone competent in both does the test.
If you stuck me in front of a computer and gave me some tasks I would get them done faster in python than FORTRAN, even if FORTRAN was the tool for the job.
What would be interesting is to see how well someone competent in both does the test.
Re: Thread about the languages ( another one ? )
My path so far (1980-2012):
Sinclair BASIC
CBM BASIC V2
6502 ASM
BBC BASIC
Fast BASIC
68000 ASM
COBOL
Rexx
Model204 U/L
BAL (IBM ASM)
VB 4/5/6
C#
Objective-C
This is a mix of my private and professional language exposure, and omits the stuff I used for a single brief project and then never again (e.g. Pascal, C++, Forth, Modula-2, 8086 ASM, Java...).
My 'home' language is, if I'm honest, BASIC. It's the first thing I learned, back in 1980, and will never fade in my mind. After that, 6502 and C# are the two I use day-to-day - the former for fun, the latter for work and fun.
What counts for more than anything, I think, is not which language you choose to produce a solution, but that you understand what's going-on behind the screen. I have genuinely lost count of the number of hotshot coders I've met over the last 10-12 years who know the current hot language and can cite esoteric syntax constructs until they're blue in the face, but don't know how many bits are in a byte.
Sinclair BASIC
CBM BASIC V2
6502 ASM
BBC BASIC
Fast BASIC
68000 ASM
COBOL
Rexx
Model204 U/L
BAL (IBM ASM)
VB 4/5/6
C#
Objective-C
This is a mix of my private and professional language exposure, and omits the stuff I used for a single brief project and then never again (e.g. Pascal, C++, Forth, Modula-2, 8086 ASM, Java...).
My 'home' language is, if I'm honest, BASIC. It's the first thing I learned, back in 1980, and will never fade in my mind. After that, 6502 and C# are the two I use day-to-day - the former for fun, the latter for work and fun.
What counts for more than anything, I think, is not which language you choose to produce a solution, but that you understand what's going-on behind the screen. I have genuinely lost count of the number of hotshot coders I've met over the last 10-12 years who know the current hot language and can cite esoteric syntax constructs until they're blue in the face, but don't know how many bits are in a byte.
Re: Thread about the languages ( another one ? )
Not sure I know that myself.
I'm sure it's 7 (ASCII), or is it 8 (EBCDIC), or maybe 9, or was it 36?
I suppose you know that in modern C and C++ it will always be at least 8.
I'm sure it's 7 (ASCII), or is it 8 (EBCDIC), or maybe 9, or was it 36?
I suppose you know that in modern C and C++ it will always be at least 8.
Re: Thread about the languages ( another one ? )
As far as 7, 8 or 9 is concerned, you're confusing the hardware representation with software encoding and error-checking - ASCII and EBCDIC are just two of a variety of different ways of representing character codes within the 8 bits of a byte.
ASCII was originally 7 bits with a parity bit for paper/punch/comms error checking, but with the demise of optomechanical storage a variety of 8-bit variants emerged. EBCDIC emerged from a 6-bit encoding mechanism originating (and largely confined to) IBM et al mainframe-class hardware, using all 8 bits of the byte to permit two 4-bit BCD fields to be 'packed' into a single byte.
There are (or have been) other variations of the number of bits to a byte on various platforms, notably DEC and Honeywell in the 60s. However, 8 bits has been an ISO standard since the late 70s (and an unofficial standard since the System/360 days) so you actually have to look quite hard to find a hardware architecture in use today which uses something other than that.
Other favourite questions when conducting interviews where we've already established that the candidate hasn't a clue include "what does CPU stand for?", "why are powers of two significant in software engineering?", "what is a processor cycle?", and "is it time to go home yet?".
ASCII was originally 7 bits with a parity bit for paper/punch/comms error checking, but with the demise of optomechanical storage a variety of 8-bit variants emerged. EBCDIC emerged from a 6-bit encoding mechanism originating (and largely confined to) IBM et al mainframe-class hardware, using all 8 bits of the byte to permit two 4-bit BCD fields to be 'packed' into a single byte.
There are (or have been) other variations of the number of bits to a byte on various platforms, notably DEC and Honeywell in the 60s. However, 8 bits has been an ISO standard since the late 70s (and an unofficial standard since the System/360 days) so you actually have to look quite hard to find a hardware architecture in use today which uses something other than that.
Other favourite questions when conducting interviews where we've already established that the candidate hasn't a clue include "what does CPU stand for?", "why are powers of two significant in software engineering?", "what is a processor cycle?", and "is it time to go home yet?".
- gilesgoat
- Sheepie Whore

- Posts: 27259
- Joined: Wed Sep 03, 2003 7:54 am 0
- Location: Monfalcone, Italy
- Contact:
Re: Thread about the languages ( another one ? )
I think a "byte" as definition has and always had 8 bits, do not confuse "byte" with "cpu word" ( i.e. better to say the word the CPU fetches as a single instruction - even this definition could be lightly wrong ) that could range from 4 bits, as in a 4004 CPU to 8, 10, 11, 12, 16 mainframes had various different sizes during time.
That's why in RFCs normally you'll hear about "octect" not "byte" to be even more sure we are talking about 8 bits and nothing else.
@Istar : that's been various exotic or less exotic HW using not 8 bits as they 'native unit' but I still believe that "Byte" ALWAYS meant '8 bits'.
@Istar2 : mind you those last 3 questions you say could be almost 'completely irrelevant' depending on what kind of coder/job you are hiring a person for ( i.e. I meant "completely useless" ), if you'd have to hire someone to write some Web application maybe involving databases and such or else I don't think "it could give less than a shit" to those questions.
That's why in RFCs normally you'll hear about "octect" not "byte" to be even more sure we are talking about 8 bits and nothing else.
@Istar : that's been various exotic or less exotic HW using not 8 bits as they 'native unit' but I still believe that "Byte" ALWAYS meant '8 bits'.
@Istar2 : mind you those last 3 questions you say could be almost 'completely irrelevant' depending on what kind of coder/job you are hiring a person for ( i.e. I meant "completely useless" ), if you'd have to hire someone to write some Web application maybe involving databases and such or else I don't think "it could give less than a shit" to those questions.
Giles the billy goat
"Baa"
"Baa"
Re: Thread about the languages ( another one ? )
AMOS Basic (I had a VIC-20 and C-64 before but only really started programming on the Amiga)
C (started learning this on an Amiga without a hard drive – compiling anything needed numerous disk swaps – then moved on to DJGPP when I got a PC in 1999)
QuickBasic (only for a short while)
Delphi (started with Delphi 3)
6502 assembly (still learning because I love oldskool demos; made a few very simple intros for the C-64 and VIC-20)
My favourite is definitely Delphi, and I currently use Delphi 2010 for both work and personal projects.
C (started learning this on an Amiga without a hard drive – compiling anything needed numerous disk swaps – then moved on to DJGPP when I got a PC in 1999)
QuickBasic (only for a short while)
Delphi (started with Delphi 3)
6502 assembly (still learning because I love oldskool demos; made a few very simple intros for the C-64 and VIC-20)
My favourite is definitely Delphi, and I currently use Delphi 2010 for both work and personal projects.
Signature
Re: Thread about the languages ( another one ? )
No, it's varied over the years usually being the amount of bits to represent a single character. The first usage of the term was for a machine that had a variable amount of bits for each byte.gilesgoat wrote:I think a "byte" as definition has and always had 8 bits, do not confuse "byte" with "cpu word" ( i.e. better to say the word the CPU fetches as a single instruction - even this definition could be lightly wrong ) that could range from 4 bits, as in a 4004 CPU to 8, 10, 11, 12, 16 mainframes had various different sizes during time.
Re: Thread about the languages ( another one ? )
Those who don't understand history may one day be forced to port to it '-)
Historically bytes have been all over the place, although I have only been unfortunate enough to use 1 machine that didn't have 8 bit bytes myself. Some sort of ancient unisys box IIRC.
Historically bytes have been all over the place, although I have only been unfortunate enough to use 1 machine that didn't have 8 bit bytes myself. Some sort of ancient unisys box IIRC.
Re: Thread about the languages ( another one ? )
1. The word 'byte' describes a collection of bits - as I mentioned, this has not always been constant at eight, but was industry-standardised by IBM as such and then later ratified by ISO.gilesgoat wrote:I think a "byte" as definition has and always had 8 bits, do not confuse "byte" with "cpu word" ( i.e. better to say the word the CPU fetches as a single instruction - even this definition could be lightly wrong ) that could range from 4 bits, as in a 4004 CPU to 8, 10, 11, 12, 16 mainframes had various different sizes during time.
That's why in RFCs normally you'll hear about "octect" not "byte" to be even more sure we are talking about 8 bits and nothing else.
@Istar : that's been various exotic or less exotic HW using not 8 bits as they 'native unit' but I still believe that "Byte" ALWAYS meant '8 bits'.
@Istar2 : mind you those last 3 questions you say could be almost 'completely irrelevant' depending on what kind of coder/job you are hiring a person for ( i.e. I meant "completely useless" ), if you'd have to hire someone to write some Web application maybe involving databases and such or else I don't think "it could give less than a shit" to those questions.
2. Do not confuse 'word' with 'byte' - a word is two bytes. A longword is four bytes. A verylongword is eight bytes. Reciprocally, a nybble is half-a-byte, and a slyce is half-a-nybble.
3. As I stipulated, in an interview when we have already established that the candidate is not suited to the role, it can be interesting to discover whether they have any foundation knowledge at all. My original point was that language skills are fine but too many candidates don't know the fundamentals of how computers work. It doesn't matter if the role is web-developer or systems-engineer.


