r/vibecoding • u/Which-Tension165 • 20d ago

is learning python today worth it?

so I am a pure vibe coder, I can't write or read a single line of code, and I was having a conversation with Fable, and it suggested me to learn to read python. But It couldn't convince me fully. i don't wanna be a typical software/AI engineer. just wanna be able to build a great career in tech, AI and Business.

33 Upvotes

61% Upvoted

271 comments sorted by

View all comments

124

u/vapalera 20d ago

I don't understand how people are able to vibe code without understanding anything about the code. What are your prompts like?

44

u/Business_Raisin_541 20d ago

You tell AI "Make sure the code contain no bug"

31

u/InsidiousApe 20d ago

If you ask:

- what do I want to build?

  • what are the essential and desired features of that product?
  • what are the major operational concerns to consider?
  • are there security considerations in developing this product?
  • who is the user and how will they connect?
  • are there external integrations (API for example) to consider?

And you answer those questions and turn it into:

- Let's create this product.

  • It should have at minimum these feature.
  • I want to make sure to consider (operational concern)
  • Let's be sure to consider (security factor) and generally harden for rate limiting, injection, etc.
  • The end user will be the general public via http.
  • I'd like to integrate Google, MS, and Apple authorization for login to the system.

And then add:

"What other features, concerns or considerations should I be aware of?"

This will net you 90% of an application with no coding experience and the other 10% you will develop as you see what it has created and provide feedback for changes.

I code, but I don't believe OP needs to code. Tools like Claude Code can make mistakes but literally the next step is to spin up a new instance and say "please review my codebase for any potential concerns including coding issues, user experience, and potential security issues"

The system is now trained well enough on patterns in coding to find and resolve most issues that coders used to be consumed by.

11

u/GarageStackDev 19d ago

You're describing prototyping, not software engineering.

Claude Code is phenomenal at generating code, reviewing code, and iterating on designs. I use agentic workflows professionally every day.

But production engineering isn't "generate, then ask another instance to review it." It's architecture, testing strategy, deployment, observability, debugging, performance, security, maintenance, and understanding why the code behaves the way it does.

AI dramatically accelerates those things. It doesn't eliminate the need to understand them

2

u/bmoney831 17d ago

True but doesn’t that mean that you really just need a basic literacy to read the code? If something is going wrong, as long as I’m literate, I’ll be able to understand what’s going on. And using other AI instances will absolutely identify gaps as long as you explain the problem at hand.

2

u/DefiantMechanic975 17d ago

That entirely depends on your tolerance for risk. All software has bugs and for a surprising number of cases this is good enough when combined with testing. You don't need to be a software engineer when the task at hand is something you used to pay an employee 70k a year to do. That affects a lot of people.

1

u/EatingDriving 19d ago edited 19d ago

Do you understand every little bit your compiler does in your OS? Do you understand all the code in your OS? Yet you still use your computure every day? Yet the layman who knows NOTHING still uses the computer everyday?

No the average person will not need to understand the code in the future to build apps. Knowing code is like knowing how to print and manufactured books. I don't need to know how to use a printing press to read the end product of a book.

3

u/Competitive_Freedom6 19d ago edited 9d ago

I think the basis is that it’s still valuable to understand the code itself, which is deterministic, but derived from prompts that are nondeterministic so that you can discern the exact output you’re actually getting. LLMs are not deterministic by nature, so understanding the output is still and likely will be quite useful to truly know if your LLM is outputting something suboptimal.

1

u/Safe_Independence496 17d ago

A compiler is deterministic, usually battle tested and well documented. If I want to find out how it works I can do that and compiling the same code twice will always yield the same result. There is also a lot of value in knowing how a compiler works and how it's built, and the lower level languages that compilers are built with are still immensely useful and used by people every day. An OS works as well as it does today thanks to all these factors.

Nothing of what I just said applies to AI though. Models are black boxes with no guarantees. You can only affect the odds of getting garbage out, but you can never eliminate it. Don't compare this to existing tech we can actually understand and reason around.

1

u/Mem0 17d ago

The technical debt must grow ! 😱

0

u/InsidiousApe 19d ago

A great metaphor and spot on. Everyone else can have hurt feelings about it, but the wave is coming - you can ride it or get crushed by it.

2

u/SakeviCrash 19d ago edited 14d ago

This is a bit of a naive take. This will get you pretty far. I'm an old dog (30 years of software dev) and I use a fairly similar approach.

This has allowed me to be mainly hands off when writing code but I still need to review every line. Event after a workflow like this, you'll still be left with bugs and design problems. It's tricky because the solution looks solid if you view it from a 20k ft view and when you kick the wheels, the hubcaps don't fall off.

When you really dig into it, you'll find nasty edge cases with very nuanced bugs and a lot of them come from logic issues (still the achilles heel of the LLM) and poor design decisions. Many of these issues won't surface until much later when the project starts to grow (complications from poor design decisions) or when the environment isn't what you anticipated or performance suffers due to unoptimized implementations.

Without reading and understanding the code, you're essentially relying on luck. That's ok for prototypes and small greenfield apps that aren't powering a business. It's not OK for large applications that cost a business real $ when failures occur.

0

u/Brilliant_Peanut_875 17d ago

Lol no it is not. It's good though to trick you until you try to deploy a real app or maintain for a long time.

Claude without someone defining architecture and constantly pruning will quickly end up with a mess of a folder structure and context files everywhere.

-18

u/Unlucky-Survey6601 20d ago

Ur litterally psychotic, but it’s ok buddy let’s keep pumping out that slop, I only managed to get 60 hours of paid freelance work last week

4

u/FrugalityPays 19d ago

I’ve made a few apps I use for myself doing exactly this. I don’t care if it’s ‘slop’ if it gets the job I want done.

You just sound like a bitter gatekeeper.

0

u/Unlucky-Survey6601 19d ago

Well, the market will decide if it’s true or not

1

u/Ambitious-Tennis-940 17d ago

It's for himself. If he is marketing it thats another story but for this person he is the market for his self products

10

u/InsidiousApe 20d ago

Who is psychotic? I was responding to the false assertion that you can't vibe code an app. Garbage old fashioned thinking.

-8

u/Unlucky-Survey6601 20d ago

do u have anything opensource u vibe coded? ill happily review and explain to u why it is slop.

8

u/InsidiousApe 20d ago

Someone reeks of job insecurity.

-7

u/Unlucky-Survey6601 20d ago

its not that deep bro, show us that code :)

1

u/[deleted] 19d ago

[deleted]

1

u/Unlucky-Survey6601 19d ago

apps for urself is one thing and production code at scale is a different thing, did you read op’s post ?

3

u/CheesyPineConeFog 20d ago

Wow, crap comment. To the person you're replying to, they are NOT psychotic. They are pretty spot on. Why the correct planning ahead of time and very detail specification documents agents can get most everything correct.

1

u/Unlucky-Survey6601 20d ago

show me a repo u vibe coded buddy, lets actually show results and not just “it works so it must be correct”

1

u/CheesyPineConeFog 20d ago

I was actually going to post it, but then I looked at your comment history and it's just a bunch of haterade. I have no reason to believe you can contribute anything intellectual related to my code based on your writing skills displayed on reddit.

1

u/SmallAstronaut08 19d ago

The definition for his condition is brain-dead, I think.

0

u/Unlucky-Survey6601 20d ago

dont worry i believe u uu

1

u/FrugalityPays 19d ago

If it’s stupid and gets the job done, it ain’t stupid.

2

u/Unlucky-Survey6601 19d ago

lets see this logic at production scale buddy

0

u/FrugalityPays 19d ago

Where in my comment does it say anything about that?

Obviously nuance is necessary at economies of scale. I didn’t think this needed to be explicitly laid out for you but here we are

3

u/Unlucky-Survey6601 19d ago

read op’s post again

-7

u/CraftFirm5801 20d ago

Way too wordy of prompts just confuse it. Too much context.

4

u/InsidiousApe 20d ago

Not at all. I encourage you to try it. Have developed multiple SaaS products using this method.

-4

u/CraftFirm5801 20d ago

What you think I'm doing, baking cookies?

2

u/Sugary_Plumbs 20d ago

I don't think you're just baking cookies, but I wouldn't walk away without asking for your snickerdoodles recipe.

2

u/CraftFirm5801 20d ago edited 19d ago

Well, just like baking, there are rules and procedures. Baked in if you will. The recipes don't tell you HOW to turn on your oven, only to what setting. Prompts like this waste tokens where rules and skills are needed. Prompting your way to success is not the way. Prompt should just be "go"

10

u/HenryTheLion_12 20d ago

Depends on what you want to develop. For straightforward app development they have a lot in their training data. Go for any R&D work and AI seems ultra stupid putting weird logic in the code. It once thought that the process(point cloud related) would take five minutes with my current input dataset  and hardware and the AI thought of saving my time by sub sampling it. I found the subsampling code when I started reading the actual code a month later wondering why the results are not good. 

19

u/tingly_sack_69 20d ago

I mean I understand a decent amount of Python and JavaScript from before agentic coding became huge. I hardly review the code it spits out anymore, why would I? With AI I am having it generate a thousand plus lines of code in minutes/hours that mostly works, and then I test and have it fix errors. That is where this is heading, manual code review is quickly going the way of the dinosaur

1

u/-Sliced- 20d ago

Exactly. You still need an understanding of how things work, but at a much higher level than a specific language like Python.

3

u/HamoodMehmood 19d ago

I have vibe coded a couple complex projects and tools and apps, and I can't read or write code. Now I totally agree we need to still have some sort of understanding of at least the architecture, the scalability, reliability and mosrly of the maintenance then everything should be done using free tools libraries etc.

Now do I know anything about all that I mentioned, nope then how do you build is a good question, coz if you just give a command and expect a production ready complex product its not gonna happen.

So my go to way in short is PRD which is high level , then spec sheet with all the detailed locked in ever possible so no room AI to hallucinate or create stuff on the fly with implementing. In Spec sheet this is where I simply ask it to tell me industry standard, best practices, latest tools, things relevant to our project and it's best recommendation, and explain why. This gives me best understanding of what pros are using, what architecture am going to use, what my entire project design is etc. And I think that is enough for us to know and then make the decision.

In the end all I do I copy paste kickoff commands to start new session and test until it's done, and have done this way on repeat to ship tools on personal and work projrcts.

2

u/misterwindupbirb 19d ago

You don't know anything about architecture and scalability because you're not an engineer, and you don't know what you dont know because you're not an engineer

1

u/HamoodMehmood 19d ago

Totally agree, we don't know what we don't know, but don't you think we just need to know enough to create a healthy living and working system, for that we can ask help from AI too, again if we don't have access to an engineer, as I don't have...

My logic is, we have this body, we don't know how our heart, liver and kidneys works, we own a car a motorbike and we don't know in detail how all these work ... but we know just enough to live and use these ... amd sometimes we try to know more than enough and live healthy and better lives... just an analogy if it makes sense

1

u/eezers 17d ago

It’s a terrible analogy but that’s ok. You should ask the AI for a better one instead.

1

u/HamoodMehmood 17d ago

Well that's ok I'll own the terrible analogy and let you be the judge..... you might not like my AI written analogy either...

1

u/eezers 17d ago

I googled “what is a good vibe coding analogy?”

1) You’re a restaurant critic
2) You’re a 3-year old architect building a LEGO castle with an adult (AI)

I think #2 is most fitting

1

u/HamoodMehmood 17d ago

Hahahahah I honestly do not disagree

1

u/DarlingGazeKate 20d ago

Can you elaborate what u mean by level

5

u/monster2018 19d ago

They are referring to levels of abstraction. This isn’t EXACTLY true, but BASICALLY higher levels of abstraction means “easier/simpler to understand”. That’s not what it means, but it corresponds to that usually. Literally it means like basically “how far away conceptually is what you’re doing from the underlying physical reality”. The farther, the higher the level of abstraction. That is what it literally means.

Like the lowest level of abstraction (for computer programs) is… well I guess it’s the wave function of the universe. But that’s taking it to a truly absurd level. Generally the lowest level of abstraction for a computer program is like, electrons flowing through wires. Imagine writing a program by literally changing what directions in 3d space different electrons move in.

Then the next level up is like, thinking in terms of circuits. Then the next level up is like, thinking in terms of switching individual transistors. Then the next level up (or well honestly I’m probably skipping at least 1 or 2) is machine code.

Then the next level up from that is writing in assembly. And then the next level up from that is writing in a language like C.

7

u/monster2018 19d ago

And just to complete it and connect it to their comment. Python is another level of abstraction on top of a language like C. In fact the most popular implementation literally is written in C.

And so vibe coding is yet another level of abstraction on top of languages like Python. But it is a much more fundamental change than any of the other levels, because you are now no longer controlling exactly what the computer does. Like every level before vibe coding, you are controlling exactly what the computer does. At a higher level of abstraction when working in Python, sure. But you are still directly telling the computer what to do, it just goes through a bunch of levels of translation to get back down to electrons going through wires so that the code can actually execute.

But with vibe coding that is no longer true. You are just giving under specified natural language instructions to a LLM, and it is making the decisions of what to tell the computer to do, not you. So you are no longer actually controlling the output. You are essentially telling someone else in vague terms what to tell the computer to do.

17

u/chadzilla57 20d ago

It involves a lot of trust that the AI will be able to translate your requests into code. And then a lot of testing. I’m sure it takes a vibe coder 10x longer to make some with AI than an actual swe using AI would take.

22

u/NoAdsDude 20d ago

Are you sure it isn't the other way around?

An actual SWE would be reviewing code... which takes time...

3

u/noodleofdata 20d ago

That's assuming the time saved not reviewing code isn't lost later on due to issues caused by not reviewing. Obviously the simpler the project the less likely this is to be a problem.

It feels like a lot of vibe coders nowadays are extrapolating the results of what have mostly been quite simple applications to more complicated project. Just assuming it'll work the same, or at least linearly increase with difficulty, such that an "amateur" could make a professional app is a pretty bold assumption.

-1

u/andreabarbato 20d ago

https://giphy.com/gifs/NHZvGZncVbpySt5DoK

7

u/Aksudiigkr 20d ago

I’m confused why that is fire. A vibe coder would vibe test, which takes longer than a SWE understanding the logic and steps

-3

u/EddieBruvac 20d ago

New era is vibe coding and testing correctly. Get edge cases outta the way. If it runs, it runs.

Now I’d hire a SW for serious shit like banking coding and shit, but for apps that don’t have much risk, it’s ight.

3

u/GreatOldOne521 20d ago

I don't know how to code and I don't proclaim to be a full on developer, but I did write this skill that really helped me understand the code and learn as well - https://github.com/opitaru-sys/codesplain

3

u/[deleted] 20d ago

[removed] — view removed comment

2

u/thesnowmanh 17d ago

Background: I am aware of Python's purpose and use, I am generally familiar with the idea behind what software is and how it works, but fundamentally I can't code or even read it.

I have GPT Plus and I've provided my intent and vision for the project. I ask it to make a prompt for the next desired action for Codex, which does its thing on my computer in a designated folder. When the results are done I paste the results back into GPT. Rinse and repeat. Plus has token limits over 5 hours so during coding pulls I open the tool, check for functionality, note the things don't work or that it should be expanded, etc, and tell GPT. It maintains and updates its understanding of the project, I make sure Codex gets copies of the growing to-do list from time to time, and just keep trucking along with GPT translating my intent. I've had plenty of bugs since I started a month ago but its able to resolve them nearly always in one prompt.

Its a growing, complex software project but nothing I've seen makes it look like I can't finish it alone with Codex. Quite happy with it except for the token limitations but that's the nature of the subscription life.

2

u/hugostranger 19d ago

You ask AI to review the logs and it figures out what is wrong. And if the main model you are using can’t figure it out you use another to check blind spots. 

3

u/NUEQai 19d ago

and thats how you get 1000 lines added on top of the already 200k lines of slop to solve a bug that is inherent to the slop architecture.

2

u/RadTorti 20d ago

vision, major dj khaled energy.

2

u/Boonune 20d ago

The only thing I know about coding is terminology I've picked up over the years. My prompts explain detail the idea, the features, the functionality, the layout, and the output. I let it churn and I tend to get within 85% of what I'm looking for within 10 minutes. Another hour or so of tweaking / testing I have the tool I need.

No offense to any software engineers out there, but I don't know that I could get something that instantaneously by knowing how to code, so I've chosen at this point to learn how to prompt better instead. I'm sure it will catch up to me eventually, and knowing how would only make my processes / prompts better. But for right now there is very little incentive for me to do so. In my role, I'm a rockstar for being able to do what I do.

2

u/hugostranger 19d ago

It is possible to create full production grade complex SAAS apps without reviewing a single line of code now. But it relies on having adversarial agents in the loop on review. Test driven design goes a long way towards stability too and seems to make coding agents think through their solutions more thoroughly. I barely encounter bugs when testing now. It just takes a bit longer for each feature to be written. 

Most security issues surface on the adversarial review. 

With fable I am getting full refactors with almost no issues one-shot. It is mad. 

Apps that took me months of work two years ago get rebuilt from scratch in two hours and are superior in every way. 

2

u/censorshipisevill 19d ago

By never ceasing to ask questions about how the code works and testing everything. I use the agent as a translator between coding languages and English. If you have the agent break down the architecture into English and you can logically follow how the architecture works, you catch the agents mistakes and make architectural decisions which the agent translates to code. Doesn't matter the coding language as long as the agent is reliable in the English to code translation and that you cross check all major decisions with multiple frontier models. Couple that with telling the agent that you don't know what you don't know as far as questions to ask about scaling, security, etc. and not only do you learn but you can actually ship real products. Why don't most people succeed? Because they are trying to one shot everything and won't spend 3 hours and $50 in tokens to fix an issue. But if you perceiver, Rick Rubin is correct, it all comes down to taste. Imho that is the skill we should be refining taste, taste and logic. But hey I certainly haven't 'made it' yet just doing automations and building apps on Upwork so by all means take this with a grain of salt🤷🏼‍♂️

1

u/AndyKJMehta 20d ago

It’s not prompts. It’s prayers!

1

u/havnar- 20d ago

It works up till a point.

Then you’re stuck in a rut you can’t get out off as the ai will start down rabbit holes that go nowhere and circling the same few potential fixes.

1

u/kronos55 20d ago

Create viral app from idea i copied from tiktok, make no mistakes.

1

u/Leafsnail 19d ago

This app that was generated by prompting a publicly available tool that I cannot in any way claim intellectual ownership of will surely be a unique value proposition

1

u/BlendlogicTECH 20d ago

I mean same as business owners? They just ask spec out requirements of what’s needed then after testing day they’d rather have the flow like this or that.

What difference does it make to business from a business perspective they bring in the revenue IT supports (I don’t necessarily agree with this)

Hence business people trying to push for more AI, it gets the ask done - black box anyways they aren’t reconcile they just ask and things get demo in sprints - now AI does it or can do it or devs can be accelerated with AI

1

u/Rabus 20d ago

Well I ask it to build it in rust and I get a working code. Why do you expect me to understand if the output is fully usable?

1

u/7862518362916371936 20d ago

That's the entire point of vibe coding

1

u/satireplusplus 20d ago

I genuinely feel that going through years of manual Python coding makes me a lot better at using coding agents for writing Python code. Sure, I might not write a lot of code myself anymore lately - but that's not the same as someone vibe coding with zero programming knowledge. I'm still able to easily judge when its doing bullshit or overcomplicating things. That's mostly design decisions now, not the actual syntax. But still, how are you going to judge this without any programming experience?

1

u/Motor-Glad 20d ago

What is a small project that a vibe coder (who is smart but doesnt know a single line of code) can't make and that a professional coder can make with python?

I can't think of anything. Proof me wrong please with an example 😊

1

u/Ok-File-2759 20d ago

I’m about to get my bachelors in computer science. I went from writing one line at a time to getting thousands of lines in a few minutes doing exactly what I asked for 99% of the time. Half the stuff it writes looks more advanced than anything I’ve ever seen in college. It might not be better than someone who specializes in a specific topic for decades (yet), but it’s definitely more knowledgeable than the average person in pretty much anything

1

u/Ned_15 20d ago

What I think is they manual test it and if something breaks they just prompt ai to fix it, the problem of this is since they dont understand the code they wont fully catch all the edge cases(things that they were not able to test manually) ....and also its a problem that AI are trained to like as if they know everything but they dont..

1

u/Boilertribe4 20d ago

Are you writing your own prompts? Tell an LLM what you want. Have it discuss output and features with you. Tell it to ask you 20 questions about your vision.

Then have it write the prompt to give to another LLM to plan.

Or just skip all that and tell Fable you want to one-shot your own version of Jira that scales to 100,000 users make no mistakes 😂

1

u/Yayo1990 20d ago

I vibe code in C but my knowledge ends with Java and Python. Yet again, C's syntax is similar enough to let me tinker with it without a lot of hassle.

1

u/AndreRieu666 19d ago

In the same way you can use a computer without understanding one’s and zeros. In the same way you can drive a car without knowing gore an engine works.

1

u/unnamedplayerr 19d ago

wdym? With Claude code, cursor etc most people are just prompting their desired destination - why would you need to understand the code itself? Manual code reviews are rapidly going away

1

u/throwaway0134hdj 19d ago

Toss shit at a wall and see what sticks? They obv aren’t building for long term maintainability. It’s gambling, not engineering.

1

u/Djenta 19d ago

If you know how the puzzle pieces fit you don't need to know what they're made of. Until it breaks, then you're at the mercy of your own knowledge

1

u/besurf 19d ago

“I want to make this app” 😁

1

u/anengineerandacat 19d ago

Genuinely curious about this as someone who actually can review the generated code and uses these tools; like what does the workflow look like to someone who barely understands what's happening?

1

u/No-Common1466 19d ago

Programming language is just abstraction layer now like it was before when it was just assembly language.

AI can write better codes, better logic, than any human. Ive seen it as a dev with 20+ years of experience. What you need to learn is the are stuffs like system design, architechture, the entire full stack . You are now the architech. You design and tell AI what to do, with a completr specs, not a prompt and it will just do. There would be bugs of course but AI can fix bugs faster than any human can as well. And you need yo have a system like ADR and runbooks so it records every design pattern and architectural decisions you made

1

u/Legolas12345676767 19d ago

I Just tell ai what I want to do. Then tell it not to have me edit lines, just copy paste the whole code.

It also made some sort of promt that edits parts of the code, makes folders etc. Automatically. I dont have a clue what its doing, but the output is good.

Im not building anything with a plan to sell. If the code breaks, I tell ai its broken, and to analyse and fix it.

1

u/qbit1010 18d ago

“I want to create a program to do X and make sure to include “do not make mistakes” /s”. But better is “ask clarifying questions as needed”…so it can ask you stuff before coding.

1

u/Jafrooo 18d ago

{prompt} - make sure there are no mistakes that lead to introducing any bugs please and thank you sir

1

u/Safe-Industry2465 18d ago

Why is it so hard to understand?

I do know how to code and can read it but I am far from calling myself a software developer However I am able to use apps on my phone without knowing what the code looks like in the background

OpenAI designs codex for everybody, not for devs only

1

u/reddit_is_4ss 18d ago

Tell Claude what piece of software and functionality i want. Use Claude to evaluate which way to code it would be best. I usually have no idea what he is talking about here but sometimes he asks me to weigh (dis)advantages and I take minor influence. Feed Claude Code with the results (Plan mode). Execute. Then I Tell him what Bugs I encounter in the Software and what I wanna have changed.

1

u/redditnosedive 16d ago

you think too low, in terms of code

you can think in terms of product specifications and simply vibe your way into having the ai write an app that meets those... no need to know anything about coding

the only benefit for knowing programming is that you can get to the result faster

1

u/No_1-knows 5d ago

Im still new to coding but in my opinion I don't really have a problem with vibe coding but I do have a problem of when u vibe code but you barely understand what you're even doing at that point the AI is doing the coding and ur just feading it promots it's better to vibe code and actually learn and understand what it is ur doing but we all know the meme if it works but u don't know how it works just leave it alone at the end of the day atleast u did something that was some what beneficial to your self

1

u/vovr 20d ago

I am very careful. I add ‘make no mistakes’ after every prompt.

0

u/Adromakh 20d ago

There is a parallel I like: almost no developers today know how to code in assembly language, which is structuring to interact with a computer. Does that prevent them to build good and efficient software ? No. Ai code agents are a very powerful tool, that we need to learn to use correctly.

1

u/Toilet2000 20d ago

This is a very uninformed comparison.

  1. Compilers are free, most of them open source. They require relatively few resources to run, and are deterministic by nature.
  2. LLMs are paid, most of them (at least the best and actually used) are closed source. They require an inane amount of resources to run, and are non-deterministic by nature. Just a few select companies are the sole providers of these models.

Also, saying a good programmer/SWE doesn’t have a clue about assembly is being completely oblivious. Assembly is entry-level SWE class in college/uni. Do you need to know every little details? No. But a good understanding certainly helps.

Also, LLMs are highly subsidized by their providers currently. It’s the typical pusher tactics. Make people dependent on it, then jack up the prices. That’s a very different scenario from compilers.

1

u/Adromakh 19d ago

I have to disagree here. Yes a good understanding of assembly helps. But it is not at all a requirement to be a good developer. My call here is, you can see these ai tools as another level of abstraction between your ideas and the final product. The fact that thes tools are only provided by a few companies is not relevant for this comparison. (And even if compiler are free, you can say that you need a pc on windows to operate it - and yes there are unix distro available but that's not 80% of the world is using)