ColdFenix

I was just in that cave a week ago! I did the Tour that goes about 1km in and it was such a unique and amazing experience that I will probably go back at some point to do a longer tour.

I think it was the renaissance sculptors that did that, not the romans.

They are good for some drinks but not great for others in my experience. They do get soggy after a few hours and start to dissolve a bit into the drink so if you use them at home and refill a few times over an evening they aren't great. They also react with some fizzy drinks and cause them to bubble over.

And it sucked, fov of the augmented area was tiny, the projected images were see-through and you still couldn't really see the persons eyes because of the tinted glass. Vr headsets with cameras are currently by far the best way to do AR.

What ChatGPT actually comes up with in about 3 mins.

Right now it's a good but limited tool if you know how to use it. But it can't really do anything a professional in a given field can't do already. Alhough it may be a bit quicker at certain task there is always a risk of errors sneaking in that can become a headache later.

So right now I don't think it's a necessary tool. In the future I think it will become necessary, but at that point I don't think it will require much skill to use anymore as it will be much better at both understanding and actually accomplishing what you want. Right now the skill in using GPT4 is mostly in being able to work around it's limitations.

Speculation time!

I don't think the point where it will be both necessary and easy to use will be far of tbh. I'm not talking about AGI or anything close to that, but I think all that is necessary for it to reach that point is a version of GPT4 that is consistent over long code generation, is able to better plan out it's work and then follow that plan for a long time.

The trick is to split the code into smaller parts.

This is how I code using ChatGPT:

1. Have it analyze how to structure the program and then give me the code for the outline with not yet implemented methods and functions.
2. Have it implement the methods and functions one by one with tests for each one.
3. I copy the code and test for each method and function before moving on to the next one So that I always have working code.
4. Despair because my code is working and I have no idea how it works and I have become a machine that just copies code without an original thought of my own.

This works pretty well for me as long as I don't work with obscure frameworks or in large codebases.