Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
6
Likes
32
Comments
Future developers won't need Git, npm, text editors, Docker or terminals
by
Volkan Kaya
https://twitter.com/volkandkaya/status/1526832952071450624
I disagree. I think no code is the equivalent of making music with loops and samples. There will be some one hit wonders and allow more people to get involved. However, knowing how to code will always be an advantage for many obvious reasons! And those tools are essential to being a good coding developer.
Great analogy, samples are not the thing: handling the big pictures to produce something globally coherent that hits emotions is the thing!
Creating code essentially serves a particular business purpose, unlike creating music artistically.
If businesses have an option to do something cheaper or faster, they will use it.
Good points. Connecting any two disparate ideas will never be a perfect metaphor. However, my gut says those with ability to use a technological advantage will always have an edge, in game theory terms that might be large.
I mean, Dreamweaver slice was pretty much no code...that's how I got started 😂 from there I got dragged down the path into actual coding.
How many developers are working on DBs like postgres or languages like Python?
This comment was deleted 4 years ago
Coding is a great skill that is why the name no-code is a huge barrier.
The tools above are just that tools. Built for a different time.
Git is required because you need to sync multiple repos. If you had real time editing you could have a different system that was easier to reason with.
NPM should be handled by a 3rd party for security and ease of use.
Text editors should be in the browser.
Docker should be automated.
Terminals should be automated.
I use Git with team members and it's used to work on different branches on features and then bring them together. Some features need to be siloed. Git is the perfect solution for this and can't see any way round that. I won't go through the rest of the list as I think that one example shows why these tools will probably be here for another generation at least.
That is your workflow.
There are other companies that push changes all the time.
I would rather live in that world.
Fair play :)
This comment was deleted 4 years ago
This is overly simplistic. Over time there will be more developers who can build things without touching these tools directly, but the underlying technologies will still be in use. Developers who are working on moderately complex projects will still use them directly. They definitely aren't going away.
This comment has been voted down. Click to show.
The deeper I get into no-code the clearer it becomes that all these tools are barriers to entry that have marginal gains on productivity.
It seems like most developers will be coding in the browser.
As a developer, all of these tools offer me great flexibility to build exactly what I need in a team. I don’t see them disappearing anytime soon for complex, real-world projects.
The only reason I will be coding in a browser is GitHub Codespaces.
You need flexibility now because of all these tools.
Nope. Frustration with the limitations of no-code tools led me to be a developer in the first place.
This comment was deleted 4 years ago
"Coding" or "No Coding", using terminal or a GUI, eventually it comes down to implementing logic and performing actions (like installing packages).
In my opinion, you are still very much required to implement logic (code or drag & drop) and perform actions (npm, maven, ... or GUI).
100%
But the barriers to creating that logic will be lowered.
Future cyclists won't need bikes, components and equipment. They will use peloton.
That future might come haha.
Look at the matrix. Won't even need a bike.
Certainly. The only question is whether we will see all this.
True
Supposed that AI is the substitute I think that it's not even close. To use this efficiently, you must thoroughly grasp each line of code. You must also be able to type whatever fragment was autocompleted in order to use it.
However, if it works well, it might be a fantastic productivity tool that decreases context switching. On the other side, the time spent reading at documentation lowers your ability to completely comprehend the library, therefore for more sophisticated tasks, not looking at the docs may have damaged you in the long run.
Don't think AI is required for this.
As browser tools become more powerful they will replace the above.
I agree.
While these tools help, they're also creating barriers. I suspect we will see the rise of IDEs or server environments that simply remove the need. ESM is a move in that direction, and I suspect we'll see a lot more happening in the next 2 years.
Seems a bit misleading.
Git, npm or equivalent technologies will still exist but will work under the hood so the developer has less to worry about - maybe through auto configs ( like create-react-app) or through graphical tools ( example - diff tools instead of vim commands for diffing).
Abstraction has always been the trend in software engineering, because it provides convenience and let's the developer focus on core tasks.
Isn't that the same thing I said?
"Future developers won't need"
The tools will be abstracted away and as another commentor said "developers can focus on business logic"
Totally. Now developers have to learn so many tools to create a product. Many of those should be abstracted away.
Got it, my interpretation was a different. Anyway..
I can see how this would help improve adoption of projects, especially those with complex environment setups. That being said, what would replace these tools we're so used to now?
Copied from above
Git, I would look at Figmas branching
NPM should be handled by a 3rd party for security and ease of use.
Text editors should be in the browser.
Docker should be automated.
Terminals should be automated.
This is kind of what Replit is going for, I believe. They're growing a new generation of developers by teaching them to code in the browser in their teens.
Yep, after checking Replit seems we're nearly there.
I think they still need to replace Git (with something automated). Git merging and branches are complex.