• nimis (unregistered) in reply to Norman Diamond
    Norman Diamond:
    WTF? There was NO SUCH THING as a text editor when FORTRAN was invented.
    He didn't say there was, he said that he used a text editor to write FORTRAN, which could easily have been several years after the language was invented. TRWTF = you.
  • (cs) in reply to Jibble
    Jibble:
    Lower case only became practical when IBM started using
    When reading that sentence, i wondered what
  • RockyMountainCoder (unregistered)

    Has anyone here NOT been there?

    I worked a job once when "Web Services" was all new and scary, and I calmed an IT admin by making my app get a "phone directory" (of sorts) from an XML document he could keep on his main web site.

    He insisted on using Notepad to edit the file. Three times a week I'd get the call, "It's broken." And every single time, I'd find his new entry with a lower case opening tag and a title case closing tag. <every><single><time></Time></Single></Every>

  • gngeal (unregistered) in reply to Peter
    Peter:
    I worked with a experienced engineer, who felt that Word 2.0 was the best way to write CPLD code. He'd write the code in one color, the comments in another and the compiler directives in a third color.

    That's approximately how colorForth works. (Note that this is the official name of the language.)

  • Norman Diamond (unregistered) in reply to Jibble
    Jibble:
    Real men don't need debuggers, right?
    Real men, women, girls, and boys added more PRINT statements to programs. Sometimes we remembered to take them out after we fixed the bugs.
  • anonymous (unregistered) in reply to Norman Diamond
    Norman Diamond:
    Jibble:
    Real men don't need debuggers, right?
    Real men, women, girls, and boys added more PRINT statements to programs. Sometimes we remembered to take them out after we fixed the bugs.
    Pff. Real men send the debug output to the RS-232 port and never take out the debug code. You never know when you may need it.
  • OP (unregistered) in reply to ObiWayneKenobi

    All code was written in word then copied and pasted. Never compiled... as he did not know how. I was a replacement for his team member, who, I found out had been doing all of the debugging and compiling.

  • (cs) in reply to Jim the Tool
    Jim the Tool:
    2) whether they are stuck in the 1990s and don't use a distributed version control system (like bzr or hg).
    So, bzr or hg let me check out just a part of a tree that's bordering on 1TB? Because, last time I checked, subversion is where it's at for such trees. Think CAD documents.
  • (cs) in reply to dubbreak
    dubbreak:
    Have you used a DVCS? If so, do you actually know how to use it?

    For me sane merging makes it a must have for all projects (even solo ones).[...]Sometimes we'd have around 8 branches (since forking off to work on a feature in isolation is trivial) and we never had an issue merging changes.

    I don't know how the heck do people use subversion, but I've been using branches for every feature and bugfix since time immaterial, and I've never had any real issues merging stuff. It works just like it should, and merge conflicts are exactly where I'd like them to be - really when you need a human to intervene to make a proper decision.

    I either have a production trunk or branch, and merge bugfixes there and to feature development/refactoring branches, and it's all quite sensible. I'm also using git and hg, and I just don't see what the big deal people have about subversion. Merging works there, as it works in git and hg.

    In my repos, the ratio of the number of branches to the number of revisions is about 1:20 at least, there are stretches where it climbs over 1:10.

  • jammi (unregistered)

    I actually used WriteNow! to write code back when syntax highlighting wasn't a thing. The data fork contained plain text and all the formatting and images were in the resource fork.

    The code was literally self-documented with diagrams and everything.

    It'd actually be quite awesome if file metadata would be an universal feature, version control systems would support it and editors would be savvy enough to use it for things like that.

  • anonymous (unregistered) in reply to jammi
    jammi:
    I actually used WriteNow! to write code back when syntax highlighting wasn't a thing. The data fork contained plain text and all the formatting and images were in the resource fork.

    The code was literally self-documented with diagrams and everything.

    It'd actually be quite awesome if file metadata would be an universal feature, version control systems would support it and editors would be savvy enough to use it for things like that.

    Wait... without the resource fork, it had no way of telling the difference between code and comments? Or were the comments only contained in the resource fork?

  • Simon (unregistered)

    Reminds me of a project many years ago. One of the developers used some text editor instead of Eclipse.

    Then just before they checked in (cvs command line) they ran a small program that removed all the CR/LF and converted tabs to a single " ".

    His reasoning was "to save space", but I suspect it was more to annoy the people who were maintaining it (as it was being outsourced eventually).

    He never realised that as soon as someone needed to edit that file they would press CTRL-SHIFT-F (format code) and check it back in with "Fixing .... stupid coding format" prior to making any changes.

  • . (unregistered) in reply to EuroGuy

    That's very reasonable if you're using laTex. I wrote my thesis in Geany and/or Kile which are laTex aware but if you just like the hot-keys in Turbo Pascal's IDE and don't want to relearn them, it's not that import to use a syntax aware editor.

  • (cs)

    Last featured comment:

    http://thedailywtf.com/Articles/Waiting-to-Excel-.aspx

  • eric bloedow (unregistered)

    the appearance of "clippy" made me think of this video: https://www.youtube.com/watch?v=PCtr04cnx5A

  • baba66 (unregistered)

    hey

  • kiri87 (unregistered)

    hey!

Leave a comment on “An IDE Impostor”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article