Ask HN: What will programming look like in 2030?

9 points by hungle9 4 years ago | 11 comments

mikewarot 4 years ago |

I hope it will be popular to write code that is elegant and easy to read. Code that anyone, including the author, can pick up decades later and understand what's going on right away.

Personally, I'd like to be programming in Pascal, with some new features added

  Heaps, Lists, Stacks, Queues, Dictionaries, and S-expressions all as first class objects.

  A new *magical assignment operator*  ::==  (or something like it) that does reactive assignment... if anything on the right changes, the left gets updated every single time after that point.  (Like assignment in a spreadsheet)

It would be nice if we can finally get capability based security, so we can stop blaming the users, and put the fun back in computing.

muzani 4 years ago |

I'd expect Codex style AI generated code to be everywhere. You think about what you want to do, define it, define the tests it needs to pass.

More effort would be focused into understanding the actual project requirements and dealing with architecture. There will likely be no more tasks that need less than an hour, because these can be solved instantly by AI. You're left with the hard problems or the problems that need design decisions and/or meetings to resolve.

AI will likely still have trouble doing more than a screen though, e.g. the entire flow of an app or site.

Programmers will resemble architects/PMs more. They're there to explain whether a job is doable, or what changes need to be made and how long it would take.

draxil 4 years ago |

Less different than you'd think I'd say. All my career people think programming is on the verge of some major shift to managers just drawing diagrams or something.. But of course that never happens.

I think the most important change in the last twenty years has been the full acceptance of TDD. Maybe we'll get to everyone recognising continuous delivery or something like that as essential..

I'm sure there'll be a new "it" language threatening to displace the by-then majority use of go and rust. Meanwhile some carefully maintained C will still be keeping the lights on, and some poor (but well paid) individual will still be keeping some COBOL running.

rtcoms 4 years ago | |

If a new language/framework comes which can generate factorues and test cases, that may be game changing.

That will basically introduce a decent coding practices for even a junior developer, something like Rails convention over Configuration.

Major difference is quality of work I see is the amount of test coverage, because a good test coverage helps you to change code much mode confidently.

ranguski 4 years ago |

1 We are gonna get more stackoverflow questions about AI 2. Typesystems will reach a breaking point, since more dynamic Data types will be introduced. 3. Functional programming is gonna be space language. 4. Compiler AI are gonna happen. 5. Storage would devastate performance. 6. Earth is gonna be represented in 2D as flat earth.

high_byte 4 years ago | |

memory already devastates performance. I've got 50 browser processes, and few more electron processes with their own forked processes. but maybe one day RAM will be persistent/storage fast as RAM. then both our memories will be screwed

toast0 4 years ago |

One terminal with your editor, one terminal with a shell running Make, maybe one more terminal to manually test/inspect the result.

Same as it's been since two terminals for a developer was affordable.

Raed667 4 years ago |

I think building cross-platform apps will get much more accessible with better tooling and frameworks. Something in the intersection of Web, Electron and React Native.

throw_this_one 4 years ago |

Java will take over everything.

giantg2 4 years ago |

Hopefully it won't involve me working in the field.

ofou 4 years ago |

Python for BCIs

Heaps, Lists, Stacks, Queues, Dictionaries, and S-expressions all as first class objects. A new *magical assignment operator* ::== (or something like it) that does reactive assignment... if anything on the right changes, the left gets updated every single time after that point. (Like assignment in a spreadsheet)