We're creating a network of AI's services and language models to solve this issue
That's the smartest from @OpenAI considering everything still goes through their chat. They're turning into the gatekeeper just like Google in the old days
3 things I noted:
πΈ I've saved a lot of money with #gpt pro, even with the rate limit
πΈ I'm not sure what context size it's been given
πΈ Externalizing knowledge is a smart way to overcome context
12/13
So can you guess what I'll be exploring from now on?
Yep, setting up your own knowledge base and hooking it up to #gpt
And if you're in for the ride, follow me and help me by β€οΈ that first tweet π
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
π 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