Fork me on GitHub
#solo-full-stack2023-09-13
>
Chip16:09:48

Here’s the https://clojurians.slack.com/canvas/C05SVE3P116. It can be opened in a separate window. It’s certainly easier on the eyes that way.

seancorfield16:09:32

@two.stewards Are you going to invite the logging bots or do you want to keep this "private" to some degree?

gratitude-thank-you 1
Zed18:09:19

The great thing about being full-stack is that when I get bored I can do something else. Tired of futzing with CSS? Maybe I'll be a database analyst for the day

😁 1
Chip18:09:31

I hope to be bored at some point. I feel like I’m climbing a mountain in flip-flops.

Chip19:09:37

And thanks for being here.

👋 1
Chip19:09:10

This is a https://www.youtube.com/watch?v=SUfgKiTI8nE&t=521s by @chris_johnson. I was https://clojurians.slack.com/archives/C03RZMDSH/p1694473908839849 to it in #datomic. Even though it’s from Clojure Conj 2018, it’s a nice look inside a full-stack app. Amplify had just been introduced back then. For me, what’s in between the lines is just as important. Chris is a superstar. He’s not shy about saying where his skills are thin. I hope to learn as much as he forgets over a weekend. datomic:appsync: :amplify:

Chip20:09:01

The sentiment Chris expresses at the end hits home for me.

Chip20:09:39

Anyone have experience with payment integration? I haven’t run into it yet.

seancorfield21:09:49

I'm somewhat familiar with Braintree for payments. I hear a lot of solo/small company developers speak positively about Stripe (but I have no experience with it).

seancorfield21:09:50

Do you have a sense of what types of payment you want to support? Are you thinking about mobile apps, or just web apps?

Chip21:09:40

Web first. Mobile later. I’m fantasizing about something that integrates with Cognito.

Chip21:09:10

You’d think Amazon would want part of that pie

Chip22:09:58

It’s a subscription model.

Jacob O'Bryant01:09:19

I've done subscriptions with stripe. pretty straightforward. no idea about cognito integration though.

gratitude-thank-you 1
Chip21:09:12

This kind of thing gives me authentication nightmares: https://clojurians.slack.com/archives/C03S1KBA2/p1694637594335929

Chip22:09:04

So, the core UI of Phase I of my app is a chatbot. @pithyless suggested skipping a custom UI for now, implementing a chatbot API, and using an existing client. I’m game. I’m off shopping for a GraphQL standard and a client to match. Any thoughts would be deeply appreciated.

Chip22:09:44

He mentioned Matrix.

Martynas Maciulevičius06:09:52

Skip GraphQL too :thinking_face: Do it without GraphQL if you'll not have more than 1 developer any time soon

Chip09:09:24

Thanks for the feedback. How can I use an existing chatbot client without publishing an interface it understands?

Martynas Maciulevičius10:09:51

If you really need one API endpoint then do one. But not GraphQL. When you'll have 50 developers then you'll do graphql. You'll hire somebody to do it.