You should be concerned and not excited. This future might be near than we can imagine and we're just accelerating things without thinking about the consequences.
Billionaire CEOs have silenced the informed sources of information. We live in a time that everybody knows the opinion of billionaires in every aspect of society (and it is bad) but science and journalism are seen with mistrust.
Marketing and entertainment are supplanting news and knowledge. I hope that the people that is pushing back succeed.
Yeah, it's hard to maintain physical performance as we are more susceptible to injuries which keeps us away from constant training, but our brain doesn't suffer by injuries, what allow us to go further. I think what makes people to drop at advanced age on "non-physical sports" it's to focus on other aspects of life over the sport because it's exaustive, if not impossible, to focus on both.
I'm not doubting of you or anything, but you just proved point above by saying you have a successful project without even mentioning which project is that.
Good article. Nothing is more frustate than reading a text that I don't even know if the person who "wrote" it, actually read it.
If someone wants to me read a giant text generated by a small and poor prompt, I don't wanna read it
If someone wants to fix that by increasing the effort and do a better prompt and express better the ideas, I rather read that prompt over the llm output
The effort to write shitty code is way less when you are using IA, you can create a 1k lines PR with a single prompt.
This policy is important because no one is saying "we hate AI" but instead advises developers to use it with responsibility. This is coming in time since many people are using it without understanding problems and not being accountable regarding the contributions.
Did people force React? Cloud infrastructure? Microservices? You get it.
I know there are people still using PHP 5 and deploying via FTP, but most people moved on to be better professionals and use better tools. Many people are doing this to AI, too, me included.
The problem is that some big companies and influential people treat AI as a silver bullet and convince investors and customers to think the same way. These people aren't thinking about how much AI can help people be productive. They are just thinking about how much revenue it can give until the bubble pops.
> Did people force React? Cloud infrastructure? Microservices? You get it.
Actually, yes; People forced React (instead of homegrown or different options) because its easier to hire to, than finding js/typescript gurus to build your own stuff.
People forced cloud infrastructure; even today, if your 10-customer startup isn't using cloud at some capacity and/or kubernetes, investors will frown on you; devops will look at you weird (what? Needing to understand inner workings of software products to properly configure them?)
Microservices? Check. 5 years ago, you wouldn't even be hired if you skipped microservices; everyone thinks they're gooogle, and many startups need to burn those aws credits; thats how you get a dozen-machine cluster to run a solution a proper dev would code in a week and could run on a laptop.
Forcing react, cloud infra and microservices makes a lot more sense than forcing certain development tools. One is the common system you work, the other is what you use to essentially edit text.
Its basically the same. It abstracts away a layer of complexity, so you focus on different stuff. The inherent disadvantage of using these shortcuts/abstractions is only obvious if you actually understand their inner workings and their shortcomings - being cloud services or llm-generated code.
Today you have "frontend programmers" that couldn't implement a simple algorithm even if their life depended on it; thats not necessarily bad - it democratizes access to tech and lowers the entry bar. These devs up in arms against ai tools are just gatekeepers - they see how easy is to produce slop and feel threatened by it. AI is a tool; in most cases will improve the speed and quality of your work; in some cases, it wont. Just like everything else.
> If one person writes code only in react and another only in vue, in the same product, you have a mess.
Huh? quick example - a customer-facing platform with a provisioning dashboard, and a user dashboard; they can (and should, for several reasons) be developed as separate applications, and will depend on different APIs. Are you saying having 2 distinct technologies on 2 distinct components of a product is a mess? Without any other details on the product?
A good example on the type of products with these separations are e-commerce systems; payment gateways; cloud-native SaaS solutions, etc etc etc.
I'm sorry to tell you this, but your comment just shows how deep your lack of experience is; any reasonable complex product using frontend technology will have different interfaces with different requirements, different levels of polishing and - frequently - maintained by completely different teams.
reply