4 ms·

Lots of golang kubernetes work these days. Stackoverflow is used when im stuck and searching around for an answer. Its not attempting to do the work for me. At

Lots of golang kubernetes work these days. Stackoverflow is used when im stuck and searching around for an answer. Its not attempting to do the work for me. At a code level I almost never copy paste from stackoverflow. I also utilize claud and 4o at the same time while attempting to solve a problem but they are rarely able to help.

kamaal 2y ago
Kubernetes, AWS, Cloudformation and Terraform etc sort of work is still not good with AI. The current AI code rocket ship is VSCcode + Perl/Python/Node+ReactJS + Co-Pilot. This is basically a killer combination. Mostly because large amounts of Open source code is available out there for training models. Im guessing there will be an industry wide standardisation, and Python use will see a further mad rise. On the longer run some AI first programming language and tooling will be available which will have first class integration with the whole workflow. For now, forget about golang. Just use Python for turbo charged productivity.
- acedTrex 2y ago
  > For now, forget about golang I write kubernetes controllers. Golang is here to stay. > Just use Python for turbo charged productivity This is my problem with all the "AI" bros. They seem to consistently push the idea that quickly writing code is the end all of "productivity" its akin to "just shovel more shit faster its great" Speed != productivity
  - kamaal 2y ago
    I have seen several rounds of this over decades. Google will make bad programmers, Perl is a write only language, Node is cancer, Eclipse is slow etc etc. Eventually you realise you just can't win against better things. These are juggernauts, fighting them is pointless. Because it doesn't matter when you use it or not. Most people will, and make great progress. You will either be out of the industry or be forced to use it one way or the other.
everforward 2y ago
K8s is probably particularly bad because their package convention basically requires vanity imports, and I would wager the vanity names people choose are wildly inconsistent. It also doesn’t help that many packages have 3+ “versions” of themselves, so a vanity import named “core” could be v1alpha1, v1beta1 or v1.

kamaal 2y ago

Kubernetes, AWS, Cloudformation and Terraform etc sort of work is still not good with AI. The current AI code rocket ship is VSCcode + Perl/Python/Node+ReactJS + Co-Pilot. This is basically a killer combination. Mostly because large amounts of Open source code is available out there for training models. Im guessing there will be an industry wide standardisation, and Python use will see a further mad rise. On the longer run some AI first programming language and tooling will be available which will have first class integration with the whole workflow. For now, forget about golang. Just use Python for turbo charged productivity.

acedTrex 2y ago
> For now, forget about golang I write kubernetes controllers. Golang is here to stay. > Just use Python for turbo charged productivity This is my problem with all the "AI" bros. They seem to consistently push the idea that quickly writing code is the end all of "productivity" its akin to "just shovel more shit faster its great" Speed != productivity
- kamaal 2y ago
  I have seen several rounds of this over decades. Google will make bad programmers, Perl is a write only language, Node is cancer, Eclipse is slow etc etc. Eventually you realise you just can't win against better things. These are juggernauts, fighting them is pointless. Because it doesn't matter when you use it or not. Most people will, and make great progress. You will either be out of the industry or be forced to use it one way or the other.

everforward 2y ago

K8s is probably particularly bad because their package convention basically requires vanity imports, and I would wager the vanity names people choose are wildly inconsistent. It also doesn’t help that many packages have 3+ “versions” of themselves, so a vanity import named “core” could be v1alpha1, v1beta1 or v1.