• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "When coding was a skill"

Collapse

  • NotAllThere
    replied
    Originally posted by d000hg View Post
    A good developer is still 10X more productive than a poor one.
    50x

    Originally posted by Cliphead View Post
    I used to write Clipper code does that count?
    I wrote some libraries in Modula-2 to interface with dBase, so that I could rewrite the clipper code from something that took a few hours, to something that produced the same results in a few minutes.

    A recent comment on a forum that I moderate, with many contributers from the outsourcing community. "Just cut and paste the code you need, changing that one line to have the new value. Putting it into a subroutine is just cosmetic."

    Leave a comment:


  • lukemg
    replied
    Happening in all areas, there is a financial incentive for code to be generated quicker and cheaper. This creates demand and the supply follows. You only have to look at support to see how this has had every possible complication removed to turn it into a basic box-shifting job.
    Coding can be outsourced, hardware is cheap and can be chucked at the problem and automation is biting chunks out of the skills required.
    Plan B needed I fear...

    Leave a comment:


  • worzelGummidge
    replied
    I remember writing programs which had a week, yes one week turn around for the results. You made sure that you error checked then!

    Leave a comment:


  • minestrone
    replied
    Originally posted by swamp View Post
    I've seen this too.

    There is a lot of myth and misunderstanding around the Java Virtual Machine (and many other VMs). I got asked in an interview recently to explain the danger of circular references in Java. I explained there was no danger because the VM would easily detect them. The interviewer went a bit quiet after that.

    Worked on a totally crap trading system for a while where at the end of every method they would set every object to null and the comment was // hint to GC, at various places they would try and call the GC. I could have shot the fecker who wrote it, I was tempted to write a critique of his crappy code and send it to him but he had been made a VP so I would have been walked out the office. Too many people still think the VM works like it did in version 1.1, totally ignorant of hotspot.

    Leave a comment:


  • BrilloPad
    replied
    It was far better when you had to use punch cards for everything.....

    Leave a comment:


  • swamp
    replied
    Originally posted by minestrone View Post
    Java programs written by old C and C++ developers is always a pile of mince, they are always setting objects to null thinking they can somehow control the memory management.
    I've seen this too.

    There is a lot of myth and misunderstanding around the Java Virtual Machine (and many other VMs). I got asked in an interview recently to explain the danger of circular references in Java. I explained there was no danger because the VM would easily detect them. The interviewer went a bit quiet after that.

    Leave a comment:


  • suityou01
    replied
    Originally posted by scotspine View Post
    i think dp is trying to obfuscate the thread.
    I wonder how short he actually is.

    Leave a comment:


  • leeperry
    replied
    Originally posted by suityou01 View Post
    Remember? Compilng, linking, checking for memory leaks? Good mans coding. Those with this background can code, and appreciate how much things have been dumbed down. These are the chaps that would know to use a short instead of an int. Now any dimbo can churn out script and class themselves a programmer. Only today someone at work said that IT jobs were becoming more akin to being a hairdresser or mechanic.
    It's not the tools though, You can write good script and bad C (and I've seen some bad C )

    I'll quite happily use VBA or whatever tool fits the job.

    Leave a comment:


  • scotspine
    replied
    i think dp is trying to obfuscate the thread.

    Leave a comment:


  • suityou01
    replied
    Originally posted by DimPrawn View Post
    My last bit of C# code:

    Code:
    using O111; using O111.l1000; using System; using System.Collections; using
    System.l1001; using System.l1010; using System.Text; public class l1011 {
    public string l1100; public int l1101; public l1011(string l1011) { l1100 =
    O1110(l1011); } public int O1111 { get { if (l1101 == 0) return 1; if (l1101
    == 1 && l1100 == "v\u006F\u0069\u0064") return 012; return 3; } } public bool
    O10000 { get { return l1101 == 0 && l1100 == "\u0076oid"; } } public string
    O10001(int O10010, bool O10011, bool l10100) { if (l1101 == 0) return l1100;
    if (O10010 == 0) return l1100+l10101(l10100 ? '\u0050' : '\u002A'); if (l1101
    > 1 || O10011 || O10010 == 1) return "\u0049n\u0074\u0050\u0074\u0072"; if (
    l1100 == "\u0076o\u0069d") switch (O10010) { case 2 : return "b\u0079\u0074\
    u0065[\u005D"; case 3 : return "sbyte\u005B]"; case 4 : return "\u0073\u0068\
    u006Fr\u0074[]"; case 5 : return "\u0075\u0073h\u006Fr\u0074\u005B]"; case
    6 : return "\u0069\u006E\u0074[\u005D"; case 7 : return "\u0075int[]"; case
    8 : return "\u0066\u006C\u006Fa\u0074[]"; case 011 : return "d\u006Fu\u0062\
    u006C\u0065\u005B]"; } return l1100+"\u005B]"; } string l10101(char O10110) {
    l10111 O11000 = new l10111(); for (int O11001 = 0; O11001 < l1101;
    O11001++ )O11000.l11010(O10110); return O11000.O10001(); } public bool O11011 {
    get { return l1101 > 0; } } public int O11100 { get { switch (l1100) { case "
    v\u006Fid" : return 0; case "b\u0079\u0074\u0065" : case "\u0073b\u0079te" :
    return 1; case "s\u0068o\u0072\u0074" : case "\u0075\u0073h\u006Fr\u0074" :
    return 2; case "i\u006Et" : case "u\u0069nt" : return 4; case "\u0066loat" :
    return 4; case "\u0064\u006F\u0075b\u006Ce" : return 8; default : throw new
    l11101("unkno\u0077\u006E \u0062\u0061se\u0020\u0074ype"); } } } static
    O11110 l11111; public static string O1110(string l1011) { if (l11111 == null)
    l11111 = O100000(); string l100001 = (string)l11111[l1011]; if (l100001 ==
    null) { l100010.l100011.l100100("\u0077a\u0072\u006Ei\u006Eg:\u0020u\u006Ekno\
    u0077\u006E\u0020\u0074\u0079\u0070\u0065\u0020\u0022"+l1011+"\u0022\
    u0020use \u0061\u0073 \u0069\u0073."); l11111[l1011] = l1011; l100001 =
    l1011; } return l100001; } static O11110 O100000() { O11110 l100001 = new
    O11110(); l100001["v\u006Fid"] = "\u0076o\u0069\u0064"; l100001["\u0047L\
    u0076oid"] = "v\u006F\u0069\u0064"; l100001["G\u004Cenum"] = "u\u0069n\
    u0074"; l100001["G\u004Cby\u0074\u0065"] = "\u0062\u0079t\u0065"; l100001["\
    u0047\u004C\u0073h\u006F\u0072\u0074"] = "\u0073hort"; l100001["\u0047Lint"]
    = "\u0069\u006E\u0074"; l100001["\u0047Lsizei"] = "i\u006Et"; l100001["\
    u0047L\u0075\u0062yt\u0065"] = "b\u0079t\u0065"; l100001["\u0047\u004C\u0075\
    u0069n\u0074"] = "\u0075int"; l100001["G\u004Cfloat"] = "\u0066l\u006F\
    u0061t"; l100001["\u0047L\u0075short"] = "ushor\u0074"; l100001["G\u004Cclamp\
    u0066"] = "f\u006Coat"; l100001["\u0047Ldouble"] = "d\u006Fuble"; l100001["\
    u0047L\u0063lampd"] = "\u0064ouble"; l100001["G\u004Cbo\u006F\u006C\u0065\
    u0061n"] = "\u0062yte"; l100001["\u0047\u004C\u0062i\u0074\u0066iel\u0064"]
    = "\u0075int"; return l100001; } }
    Seems the permies can't maintain it so I always get extended.
    System.l1001; ??
    Public class variables??

    Leave a comment:


  • minestrone
    replied
    Java programs written by old C and C++ developers is always a pile of mince, they are always setting objects to null thinking they can somehow control the memory management.

    Leave a comment:


  • DimPrawn
    replied
    My last bit of C# code:

    Code:
    using O111; using O111.l1000; using System; using System.Collections; using
    System.l1001; using System.l1010; using System.Text; public class l1011 {
    public string l1100; public int l1101; public l1011(string l1011) { l1100 =
    O1110(l1011); } public int O1111 { get { if (l1101 == 0) return 1; if (l1101
    == 1 && l1100 == "v\u006F\u0069\u0064") return 012; return 3; } } public bool
    O10000 { get { return l1101 == 0 && l1100 == "\u0076oid"; } } public string
    O10001(int O10010, bool O10011, bool l10100) { if (l1101 == 0) return l1100;
    if (O10010 == 0) return l1100+l10101(l10100 ? '\u0050' : '\u002A'); if (l1101
    > 1 || O10011 || O10010 == 1) return "\u0049n\u0074\u0050\u0074\u0072"; if (
    l1100 == "\u0076o\u0069d") switch (O10010) { case 2 : return "b\u0079\u0074\
    u0065[\u005D"; case 3 : return "sbyte\u005B]"; case 4 : return "\u0073\u0068\
    u006Fr\u0074[]"; case 5 : return "\u0075\u0073h\u006Fr\u0074\u005B]"; case
    6 : return "\u0069\u006E\u0074[\u005D"; case 7 : return "\u0075int[]"; case
    8 : return "\u0066\u006C\u006Fa\u0074[]"; case 011 : return "d\u006Fu\u0062\
    u006C\u0065\u005B]"; } return l1100+"\u005B]"; } string l10101(char O10110) {
    l10111 O11000 = new l10111(); for (int O11001 = 0; O11001 < l1101;
    O11001++ )O11000.l11010(O10110); return O11000.O10001(); } public bool O11011 {
    get { return l1101 > 0; } } public int O11100 { get { switch (l1100) { case "
    v\u006Fid" : return 0; case "b\u0079\u0074\u0065" : case "\u0073b\u0079te" :
    return 1; case "s\u0068o\u0072\u0074" : case "\u0075\u0073h\u006Fr\u0074" :
    return 2; case "i\u006Et" : case "u\u0069nt" : return 4; case "\u0066loat" :
    return 4; case "\u0064\u006F\u0075b\u006Ce" : return 8; default : throw new
    l11101("unkno\u0077\u006E \u0062\u0061se\u0020\u0074ype"); } } } static
    O11110 l11111; public static string O1110(string l1011) { if (l11111 == null)
    l11111 = O100000(); string l100001 = (string)l11111[l1011]; if (l100001 ==
    null) { l100010.l100011.l100100("\u0077a\u0072\u006Ei\u006Eg:\u0020u\u006Ekno\
    u0077\u006E\u0020\u0074\u0079\u0070\u0065\u0020\u0022"+l1011+"\u0022\
    u0020use \u0061\u0073 \u0069\u0073."); l11111[l1011] = l1011; l100001 =
    l1011; } return l100001; } static O11110 O100000() { O11110 l100001 = new
    O11110(); l100001["v\u006Fid"] = "\u0076o\u0069\u0064"; l100001["\u0047L\
    u0076oid"] = "v\u006F\u0069\u0064"; l100001["G\u004Cenum"] = "u\u0069n\
    u0074"; l100001["G\u004Cby\u0074\u0065"] = "\u0062\u0079t\u0065"; l100001["\
    u0047\u004C\u0073h\u006F\u0072\u0074"] = "\u0073hort"; l100001["\u0047Lint"]
    = "\u0069\u006E\u0074"; l100001["\u0047Lsizei"] = "i\u006Et"; l100001["\
    u0047L\u0075\u0062yt\u0065"] = "b\u0079t\u0065"; l100001["\u0047\u004C\u0075\
    u0069n\u0074"] = "\u0075int"; l100001["G\u004Cfloat"] = "\u0066l\u006F\
    u0061t"; l100001["\u0047L\u0075short"] = "ushor\u0074"; l100001["G\u004Cclamp\
    u0066"] = "f\u006Coat"; l100001["\u0047Ldouble"] = "d\u006Fuble"; l100001["\
    u0047L\u0063lampd"] = "\u0064ouble"; l100001["G\u004Cbo\u006F\u006C\u0065\
    u0061n"] = "\u0062yte"; l100001["\u0047\u004C\u0062i\u0074\u0066iel\u0064"]
    = "\u0075int"; return l100001; } }
    Seems the permies can't maintain it so I always get extended.

    Leave a comment:


  • Platypus
    replied
    Originally posted by Andy2 View Post
    DBA looks down on programmers
    Er, wrong way round, everyone looks down on the DBA

    Leave a comment:


  • Andy2
    replied
    Originally posted by d000hg View Post
    C coders look down on C++ programmers. Both look down on Java/.net. Everybody looks down on VB coders. Except PHP devs.
    DBA looks down on programmers

    Leave a comment:


  • d000hg
    replied
    Originally posted by suityou01 View Post
    I still am a code snob though.
    It's very easy to do, whenever some tool comes around that automates something you spent time and sweat learning to do.
    C coders look down on C++ programmers. Both look down on Java/.net. Everybody looks down on VB coders. Except PHP devs.

    Leave a comment:

Working...
X