#gptusage — Public Fediverse posts on home.social

jjude @[email protected] · 2024-09-14 · 15:08 UTC

Setting up android development tools on Mac (either react-native based or flutter based) is so damn hard.

Be it go or python or even front-end frameworks like #preactjs or #vuejs , they are easy to get started (on Mac).

Getting started with mobile development is so hard on Mac. Why?

I followed instructions on https://reactnative.dev/ / https://docs.flutter.dev/get-started/install still no luck.

I even tried Claude. Nothing worked.

The last error I got related to too many files open. Tried everything in this: https://github.com/facebook/watchman/issues/923 still no luck.

I have developed apps for Palm OS. It wasn't that hard to develop an app and install on your device, even though it was around two decades back.

#devnote #gptusage

#preactjs #vuejs #devnote #gptusage

jjude @[email protected] · 2024-08-28 · 03:25 UTC

I uploaded a screenshot of a login page I liked to #claudeai and asked to write code.

Act as a UI designer. Look at the enclosed image and design the same in plain HTML and CSS. Use Tachyons css for styling. Pick a Google font that resembles the font in the image.

The generated code is not perfect but it is close to the screenshot. It is becoming more and more easy to write code with Claude.

I might use this login page design for @thoughttonote

#devnote #gptusage

#claudeai #devnote #gptusage

jjude @[email protected] · 2024-08-15 · 03:48 UTC

An example of GPTs being rubber-ducks that can reason ...

In an earlier toot, I mentioned that GPTs are rubber-ducks that can reason.

Design a preact component called "settings" that has two fields and a button: name and style. Name is a single line text field. Style is a multi-line text field. Button is "save". When it is displayed, it should load a token from the localstorage (stored with localforge) and call the backend api to fetch these details. When clicking save, it should send the details to backend api to save. If there are any errors it should display the error in red color and stay in the same screen. If there are no errors, it should goto home page.

It went about giving me this code:

class Settings extends Component {
  state = {
    name: '',
    style: '',
    error: null,
    loading: true
  };

  componentDidMount() {
    this.fetchSettings();
  }
...
}

I read through the code before copying. I was wondering if I should use usestate or this form of having component variables. So I asked:

I don't know preact. so this question could be stupid. should you use usestate to manage state or just assigning variables to state variable as you have mentioned in this last code block is ok?

Guess what, Claude responded with this:

Your question isn't stupid at all - it's a great one! The approach to managing state in Preact (and React) has evolved over time, and there are indeed different ways to handle it. Let me explain:
Class Components (what I showed): In the code I provided, I used a class component with this.state. This is an older but still valid way of managing state in Preact/React.
Functional Components with Hooks (modern approach): The more modern and now preferred way is to use functional components with hooks, specifically useState.

It reasons! It teaches. So it is not a dump portal from which I copy code (remember Stackoverflow?). Now I can understand the code I make.

#devnote #gptusage

jjude @[email protected] · 2024-08-15 · 03:42 UTC

GPTs are rubber-ducks that can reason

Every developer has an experience of talking to a rubber-duck to debug. I don't know about you. But rubber-ducks have rescued me from deep shit-holes countless times.

Rubber-duck debugging goes something like this:

• Place rubber duck on desk
• Explain to the duck what your code is supposed to do
• Explain your code line by line
• At some point you will tell the duck what you are doing next and then realize that that is not in fact what you are actually doing
• The duck will sit there serenely, happy in the knowledge that it has helped you on your way.

Since the harmless duck won't judge you, you enjoy going back to it with all your troubles and find a way out as you speak to it.

But ducks don't reason out with you. It is all up to you to figure out what you are doing wrong.

You could use a fellow developer as a duck. But those fleshly brains come with a huge disadvantage: they judge. Yikes. Last thing you want to hear when stuck in a pit is a snarky comment.

Enter GPTs - Claude & ChatGPT.

They are smart rubber-ducks.

You can reason with them. They help you analyze code. And they can teach you a thing or two too.

The more I use these smart rubber-ducks, the more I love them.

What about you?

#gptusage #devnote