If AI seriously improves your productivity now you probably should have been laid off a decade ago. I could have scripted your position out of existence.
If AI seriously improves your productivity now you probably should have been laid off a decade ago. I could have scripted your position out of existence.
Well not yet..but so far it's best use case is in creating code makin a coder 10x more productive...I'm also able to track job wages on boards...no one knows the future, but certainly not you either. Also the crowd hyping crowd- is that the trillions going into chips and AI venture globally? or people like me on substack
Anybody who thinks that AI can write code is asking to lose their job. Even at the simplest level of consideration--producing code without bugs--something like ChatGPT will produce stuff that is just wrong or buggy.
As for the tech world it runs on hype. A few years ago it was Big Data. After that it was the Cloud. Those innovations have actually had a major impact on industry but nowhere near the "world changing" ramifications that sales departments hyperventilated over.
Another commenter wrote this: тАЬThat's so much faster than we starting with a blank page and endless googling specific things on StackOverflow and getting cross just because I made a typo.тАЭ
IтАЩve been writing software for 23 years (c, c++, Perl mostly). I keep hearing similar stories like this. How AI replaces endless googles of stackoverflow to then copy paste code.
I donтАЩt write software that way. I take that blank page and just write code that does what I need it to do.
IтАЩm starting to think the people who rave about AI helping them write software maybe arenтАЩt very good at writing code, especially if writing code means endless googling for examples of how to do something so you can copy paste it.
In my experience it is very typical for beginners to focus on the code itself (syntax) rather than on what the code is supposed to do (architecture).
But of course that gets it exactly wrong. What makes a good coder a good coder is that code is easy while architecture is hard and he or she excels at the latter.
If AI seriously improves your productivity now you probably should have been laid off a decade ago. I could have scripted your position out of existence.
If you are scripting ie coding then your first in line buddy
That level of ignorance is pretty typical for the crowd hyping AI.
Well not yet..but so far it's best use case is in creating code makin a coder 10x more productive...I'm also able to track job wages on boards...no one knows the future, but certainly not you either. Also the crowd hyping crowd- is that the trillions going into chips and AI venture globally? or people like me on substack
Anybody who thinks that AI can write code is asking to lose their job. Even at the simplest level of consideration--producing code without bugs--something like ChatGPT will produce stuff that is just wrong or buggy.
As for the tech world it runs on hype. A few years ago it was Big Data. After that it was the Cloud. Those innovations have actually had a major impact on industry but nowhere near the "world changing" ramifications that sales departments hyperventilated over.
Another commenter wrote this: тАЬThat's so much faster than we starting with a blank page and endless googling specific things on StackOverflow and getting cross just because I made a typo.тАЭ
IтАЩve been writing software for 23 years (c, c++, Perl mostly). I keep hearing similar stories like this. How AI replaces endless googles of stackoverflow to then copy paste code.
I donтАЩt write software that way. I take that blank page and just write code that does what I need it to do.
IтАЩm starting to think the people who rave about AI helping them write software maybe arenтАЩt very good at writing code, especially if writing code means endless googling for examples of how to do something so you can copy paste it.
In my experience it is very typical for beginners to focus on the code itself (syntax) rather than on what the code is supposed to do (architecture).
But of course that gets it exactly wrong. What makes a good coder a good coder is that code is easy while architecture is hard and he or she excels at the latter.
Exactly right, imo.