Slashdot Mirror


The Technologies Changing What It Means To Be a Programmer

snydeq writes Modern programming bears little resemblance to the days of assembly code and toggles. Worse, or perhaps better, it markedly differs from what it meant to be a programmer just five years ago. While the technologies and tools underlying this transformation can make development work more powerful and efficient, they also make developers increasingly responsible for facets of computing beyond their traditional domain, thereby concentrating a wider range of roles and responsibilities into leaner, more overworked staff.

6 of 294 comments (clear)

  1. Not changed much by jmyers · · Score: 5, Insightful

    I don't see many changes. Vendors, managers, and salespeople change the buzz words every few years and talk of great paradigm shifts. Programmers continue to write code and produce actual results. In a perfect world the programmers get to choose their own tools. In the real world we have to use whatever buzz word compliant tools are thrown in the mix each year. They never actually live up to the hype and you have to dig in and find the code buried within and build stuff that works. I remember when the salespeople were touting dBase II and how programming would be completely changed. Right.

  2. COBOL was better than JavaScript. by Anonymous Coward · · Score: 5, Insightful

    As a former COBOL programmer way back when during the mainframe era, and as somebody who has had to develop and maintain JavaScript code over the past several years, I can say without a doubt that I much preferred using COBOL.

    Although COBOL is a verbose language and not always the easiest to use, at least it isn't shit-for-brains stupid like JavaScript so often is. When I use JavaScript, I often sit there wondering, "What the fuck was Eich thinking when he came up with this stupidity?" and then I wonder, "Why the fuck hasn't the JavaScript community fixed these fucking stupid misfeatures?"

    So many things about JavaScript are just so stupidly broken, and there's absolutely no reason why they should be like that. They're so idiotically wrong that it's totally worth breaking compatiblity with existing code if it means fixing these problems. COBOL, while not the best language, was never anywhere near as fucking moronic as JavaScript usually is.

  3. Re:Some of us do still assemble, even now by khasim · · Score: 5, Insightful

    What's not modern about using assembler where it's appropriate to do so?

    Because it is InfoWorld. Seriously.

    Here's item # 3.

    Developer tool No. 3: Libraries

    Do you remember the first time you used a library? But they're new because programmers 5 years ago did not have libraries.

    It gets better:

    Developer tool No. 4: APIs

    Yeah. That's a radical new concept there.

    Fuck it.

    Developer tool No. 6: Browsers

    Tonight we're gonna party like it's 1995.

    And, finally:

    The work involved in telling computers what to do is markedly different than it was even five years ago, and it's quite possible that any Rip Van Winkle-like developer who slept through the past 10 years would be unable to function in the today's computing world.

    No it is not. Not they would not. Windows XP was released in 2001 and there are still people using it. That's 13 years ago.

    InfoWorld sucks.

  4. what a load of utter bullshit by sribe · · Score: 5, Insightful

    I've been doing this full-time since 1985, and the most distressing part is how little real change there has been in all that time!

  5. No retarded like clickbait retarded by 0xdeadbeef · · Score: 5, Insightful

    The work involved in telling computers what to do is markedly different than it was even five years ago, and it's quite possible that any Rip Van Winkle-like developer who slept through the past 10 years would be unable to function in the today's computing world.

    This is quite possibly the stupidest article ever posted to Slashdot.

    Ok, this month.

  6. Re:We only use JS now? by machineghost · · Score: 5, Insightful

    Yeah, it only runs the front end of EVERY WEBSITE IN EXISTENCE (which includes tons of "serious" SaS applications, and more and more "thick client" sites where the bulk of the code is in JS and the server is just used for database work). But yeah, other than that nothing mission critical at all.