I've been thinking about this approach. How do you handle updates on this setup? For example, a status component that goes from "loading" to "success".
Does the LLM go back and modify the previous response, sending deltas to the client? Effectively changing the component from loading to success. Or is something else happening behind the scenes?
I’m a seasoned Full-Stack Software Engineer with a 9+ years of experience creating scalable web applications and leading technical teams. Proficient in JavaScript, AWS, React, Vue, and Three.js, I specialize in building dynamic user interfaces and scalable backend solutions.
Most recently I founded Transfer Thought, a Techstar's company, where I built a web based virtual reality platform that empowered users to create VR applications. This allowed anyone with a browser to build and deploy immersive experiences. I am interested in becoming part of a team of creative developers who are committed to producing exceptional products and pushing the boundaries of technology.
I’m a seasoned Full-Stack Software Engineer with a decade of experience creating scalable web applications and leading technical teams. Proficient in JavaScript, AWS, React, Vue, and Three.js, I specialize in building dynamic user interfaces and scalable backend solutions.
Most recently, I founded a virtual reality company that empowers users to create VR applications, allowing anyone with a browser to build and deploy immersive experiences.
• I architected a scalable backend solution with DynamoDB, Lambda, and S3. • I designed our frontend application with Figma and built it with Vue.js, Three.js, and Aframe.js • I grew a team. Guiding them through project phases, mentoring them to enhance their skills, and encouraging innovation as we pioneered the accessibility of virtual reality.
I’m a seasoned Full-Stack Software Engineer with a decade of experience creating scalable web applications and leading technical teams. Proficient in JavaScript, AWS, React, Vue, and Three.js, I specialize in building dynamic user interfaces and scalable backend solutions.
Most recently, I founded a virtual reality company that empowers users to create VR applications, allowing anyone with a browser to build and deploy immersive experiences.
• I architected a scalable backend solution with DynamoDB, Lambda, and S3.
• I designed our frontend application with Figma and built it with Vue.js, Three.js, and Aframe.js
• I grew a team. Guiding them through project phases, mentoring them to enhance their skills, and encouraging innovation as we pioneered the accessibility of virtual reality.
+1 for Notion. If you are interested, I would also look into a system like "Getting Things Done" or "Zen to Done" for a more bite-sized approach.
219 notes though, sounds like you already have a good habit of capturing your thoughts! Organizing tasks into current contexts has helped me a lot (At Computer, Housework, Wife,...). Best of luck!
I've been thinking about this approach. How do you handle updates on this setup? For example, a status component that goes from "loading" to "success".
Does the LLM go back and modify the previous response, sending deltas to the client? Effectively changing the component from loading to success. Or is something else happening behind the scenes?