Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: My first full stack project

plotnotes.ai

Post reply on HN
Print view View original

1–10 of 29 posts

Show HN: My first full stack project

#1

Post by NoahECampbell »

Just finished my second year at college studying Computer Science, and wanted to try and gain experience as a full stack dev this summer, so I made a website that allows users to create stories using openai's API, using embeddings for custom terms users can define, and create short stories and chapters alike. I'm mainly just looking for some feedback on how I can improve it or make it more presentable, so any help/feedback is welcome and appreciated!

Show HN: My first full stack project
plotnotes.ai

Re: Show HN: My first full stack project

#3

Post by jamisonbryant »

Many on HN (and elsewhere) will lament the fact that there is no way to read about or test-drive your project without signing up (aside from going to GitHub). Many of us guard our emails/logins quite jealously, myself included. Please consider adding some of what you included in the description of this post on your site. Right now, it looks no different to me than a random login form I encountered on the Internet.

That being said, I caved and set up an account with a temp email and the password 'password' (might wanna check on those password security rules) just to play with it so I could give some constructive feedback. Unfortunately, generating a story isn't working (the spinner is spinning infinitely) and I see a few errors and warnings in the Developer Console. I'm not sure what the Short Stories page is supposed to show, either, but it also appears to be malfunctioning.

I don't mean to eviscerate your project - it is always exciting and scary to share something with the world. This needs a little more work before it's ready for show-and-tell, though, IMO. I'm not even sure what I would use this for. Best of luck.

Re: Show HN: My first full stack project

#4

Post by NoahECampbell »

jamisonbryant wrote: post #3

Many on HN (and elsewhere) will lament the fact that there is no way to read about or test-drive your project without signing up (aside from going to GitHub). Many of us guard our emails/logins quite jealously, myself included. Please consider adding some of what you included in the description of this post on your site. Right now, it looks no different to me than a random login form I encountered on the Internet. Th…

Eviscerate it all you like, thats the point of me doing this so no hard feelings. As for the email bit, all it is used for is to store the email and make it feel safe since google auth seemed like a rather secure option in my limited experience. The short stories and chapter pages are meant to show short stories and chapters generated on the prompt endpoint. I was thinking about adding some help page to describe it in more detail since I know its much easier for me to know what does what as I have all the context for the project in my head

Re: Show HN: My first full stack project

#5

Post by graypegg »

NoahECampbell wrote: post #4
jamisonbryant wrote: post #3

Many on HN (and elsewhere) will lament the fact that there is no way to read about or test-drive your project without signing up (aside from going to GitHub). Many of us guard our emails/logins quite jealously, myself included. Please consider adding some of what you included in the description of this post on your site. Right now, it looks no different to me than a random login form I encountered on the Internet. Th…

Eviscerate it all you like, thats the point of me doing this so no hard feelings. As for the email bit, all it is used for is to store the email and make it feel safe since google auth seemed like a rather secure option in my limited experience. The short stories and chapter pages are meant to show short stories and chapters generated on the prompt endpoint. I was thinking about adding some help page to describe it i…

I think even just some screenshots and a blurb about what it is would be helpful on the home page. Your logged out UI should operate as the pitch for the product normally.

Like jamisonbryant said, people want some assurance about what they’re getting in exchange for their personal info and a direct line to their email.

Re: Show HN: My first full stack project

#6

Post by NoahECampbell »

graypegg wrote: post #5
NoahECampbell wrote: post #4

Earlier quoted context omitted.

Eviscerate it all you like, thats the point of me doing this so no hard feelings. As for the email bit, all it is used for is to store the email and make it feel safe since google auth seemed like a rather secure option in my limited experience. The short stories and chapter pages are meant to show short stories and chapters generated on the prompt endpoint. I was thinking about adding some help page to describe it i…

I think even just some screenshots and a blurb about what it is would be helpful on the home page. Your logged out UI should operate as the pitch for the product normally. Like jamisonbryant said, people want some assurance about what they’re getting in exchange for their personal info and a direct line to their email.

Totally understandable, Ill do that here then, which is what you're suggesting right? Or do you mean just explain it on the login page?

Re: Show HN: My first full stack project

#7

Post by 0xbeefcab »

Hi there,

Visually it looks pretty good. However like what jamisonbryant said, people on this website aren't fans of when they have to sign in to test something. I made a test account to try it out, and unfortunately submitting my prompt resulted in a Error status 504 on the request with message

"An error occurred with your deployment

FUNCTION_INVOCATION_TIMEOUT"

This is probably because you are waiting for the external openAI API's response before responding to the user's request. You might want to return a response immediately and asynchronously process the openAI part of things and notify the user when its ready somehow.

Re: Show HN: My first full stack project

#8

Post by NoahECampbell »

0xbeefcab wrote: post #7

Hi there, Visually it looks pretty good. However like what jamisonbryant said, people on this website aren't fans of when they have to sign in to test something. I made a test account to try it out, and unfortunately submitting my prompt resulted in a Error status 504 on the request with message "An error occurred with your deployment FUNCTION_INVOCATION_TIMEOUT" This is probably because you are waiting for the exter…

That was something I had wanted to do but couldnt figure out how to do right away so went with this slightly worse approach as a temporary thing to just get something out there, but that totally makes sense and would definitely improve the UX

Re: Show HN: My first full stack project

#9

Post by pacerier »

NoahECampbell wrote: post #4
jamisonbryant wrote: post #3

Many on HN (and elsewhere) will lament the fact that there is no way to read about or test-drive your project without signing up (aside from going to GitHub). Many of us guard our emails/logins quite jealously, myself included. Please consider adding some of what you included in the description of this post on your site. Right now, it looks no different to me than a random login form I encountered on the Internet. Th…

Eviscerate it all you like, thats the point of me doing this so no hard feelings. As for the email bit, all it is used for is to store the email and make it feel safe since google auth seemed like a rather secure option in my limited experience. The short stories and chapter pages are meant to show short stories and chapters generated on the prompt endpoint. I was thinking about adding some help page to describe it i…

re "" make it "feel safe" ""; Accwalling is one of those things in an app that need full rationales, seldom done in 2 words.

Re: Show HN: My first full stack project

#10

Post by 0xbeefcab »

NoahECampbell wrote: post #8
0xbeefcab wrote: post #7

Hi there, Visually it looks pretty good. However like what jamisonbryant said, people on this website aren't fans of when they have to sign in to test something. I made a test account to try it out, and unfortunately submitting my prompt resulted in a Error status 504 on the request with message "An error occurred with your deployment FUNCTION_INVOCATION_TIMEOUT" This is probably because you are waiting for the exter…

That was something I had wanted to do but couldnt figure out how to do right away so went with this slightly worse approach as a temporary thing to just get something out there, but that totally makes sense and would definitely improve the UX

I have very little webdev experience so my advice might be completely useless, but some google searches show either long polling or websockets as a solution to this problem. Either way, good job
Post reply on HN