If you're a dev you should definitely feel concerned by this too
Personally, I think it's great that the barrier to entry is getting lowered, but it also means you should already be trying out the tools to avoid getting left behind
Let's take a turn and work on the Chrome Extension cause I believe I'll be getting it out way before the VSCode one
I'm not waiting for the web to get promptful so I'm taking maters into my own hands
1/11
As always, #gpt4 is setting up and creating everything for me admirably. Although I see some questionable configs in eslint, prettier and tsconfig if it tries to provide them
Oh ๐ฉ !
2/11
I've been keeping the same chat window to keep as much context as possible. But because of this, I now have to deal with resets
I need to be able to get a new chat window up to speed as quickly as possible โฑ
๐ Like a plumber would say, "Let's-a-go" with part 5
This time, I'll focus a bit more on the development side cause that may be why you've come here in the first place ๐
1/13
#chatgpt's been great to pop up new projects (albeit some outdated methods once in a while)
But now that we're getting to the meat of software making, which is actually more than following a gettin' started page, a couple of things are happening
Time for numbering #๏ธโฃ
2/13
1๏ธโฃ I need to provide more context more often
Yep, the large data set it's been trained on is not enough. Now it needs to be aware of local context which means:
๐ธ Reminding it of folder structure
๐ธ Giving files content
๐ธ Giving dependencies content
๐ธ Fetching it doc
Between pricing (I'm cheap as f๐ตk) and rate limiting, I'm now spending half my time writing
Truth is, I quite enjoy it so let's gooooo ๐
1/15
So at least the #GPT4's API is available for prompting.
But I don't like the playground
๐ถ๐ป I need pairprog-webview, nextjs, tailwind to chat with your own API
๐ค Sure thing
๐ต๐ป Wow, this API call looks quite outdated and doesn't work
๐ค ermmm...
In which I make the mistake of continuing my part 1 thread and quickly diverge into some insights about #gpt4 prompting, and the parallels to standards in #leanengineering