hegem0n

I've been doing a lot of web dev for the past few years and have used angular, react, and vue in production within the last year.

My recommendations:

- Vue+vuetify is my preference for frontend framework. None of them are perfect but I think Vue is the simplest. Tailwind is nice for prototyping but doesn't scale well , I always end up ditching it after a few weeks

- Typescript on both frontend and backend (to easily share code & interfaces and get nice IDE goodies in VSCode). I like NestJS or just plain express.

- Avoid ORMs, I like Kysely for Postgres

- You can easily spin up a database (RDS), frontend (CloudFront), and backend (Lambda is easiest) within the free tier on AWS.

This is brilliant, but please do MongoDB. It's less intuitive to query and could benefit greatly from GPT

I want to see the evolution of context management tools for coding with GPT.

- implement a function, providing structural context (e.g. model, service, controller) with stubbed modules, but leave out utilities/libraries and database model - drop the structural context, and ask it to expand the stub implementation with some additional context about the database model - drop the database model context, and ask it to refactor the solution with some additional context about utilities/libraries

I think this is doable, if we can build up some utilities for context management and iterative development, GPT should start to be usable on large code bases. It could work similarly to how one person wrote an entire novel using GPT.

I love this. This is the future

I'm a startup CTO, but I've gone deep down the rabbit hole of growth hacking lately. I'm interested in applying some methods I've learned to a new idea.