Inebas
Joined 15 years ago
Joined 15 years ago
EDIT 1: I then simplify the question and set it to expert mode. I ask ``` given some text after it was scraped by beautiful soup. write a python code that cleans this so it's easier for a machine learning model to handle ```.
I then copy and paste the output into the additional context section.
The code it gave me was how to use beautiful soup and to remove unnecessary white spaces. ChatGPT gave a more thorough answer which is to use some regex to clean the text.
EDIT 2: Got it to work better by setting it to expert mode and copy pasting the whole thing. It truncates a lot of the text and missed the question at the bottom. Then, after it gives some generic answer. I asked the question on using python to cleans this so it's easier for a machine learning model to handle. It gave me a much better answer and with the links on where it got it from.
Very cool tech. I'll be trying it a lot. Thank you.
finally, i do think it will change again because the structure for theme app extensions have changed and now i'm not even sure if my project will work if i update that section.
the migration documents are very bad and they remove old documents. for example, it used to be that you need to add a folder called `theme-app-extensions` and it's very different, and there is no migration docs for that. they just want you to use cli 3 out of the blue.
Some comments say that using UI will eventually restrict you. That might be true and I can totally see that. However, at that time, it is a good idea to step back and look at the overall design and figure out if you over design something. I like functional apps that work with little effort. It does not mean that it have to look ugly but you can customize and beautify the UI within the constraints of Apple's framework. Yes, there will be limits but is it worth the extra complexity of rolling it out on your own?
I have not tried storyboard but I would like to try it out soon.
In general, my philosophy has changed to use good, solid, reliable frameworks and keep the design (UI) and features (code) simpler. You will be able to get 90% of what you really want with less work (coding and maintaining).
What I would do is to code the way I would and then go over it with him via teamviewer or something and we chat over skype. For me, the difficult part is creating the right classes and refactoring, making unit tests and making code scale. I also have design questions. Perhaps I'll make a post when I have more feedback.