HN user

justanotherunit

28 karma
Posts4
Comments27
View on HN
GPT‑Live 14 days ago

Hey! Nice work, been looking into having a conversational modal integrated with my dev workflow.

Are we seeing any conversational layer integrated with codex soon?

Are clients really paying for it? It’s really fascinating actually. Is it because the ”client” built it so they have sentimental value and sold it to themselves before you receive the request?

Fascinating, thanks for responding. If k may ask, what is your monthly (or any other interval) token usage? And are you finding a pi to be a bottleneck in regards of any performance?

Interesting, would you mind sharing your architectural setup? How does your index communicate to your agent server, what is the main agent framework/engine used?

Sounds like a cool concept to speak into your watch/wearable which automatically saves or performs tasks on the fly.

What is the general execution time from:

Prompt received -> final task executed?

So how would you go and explain how an output of tokens can call a function, or even generate an image since that requires a whole different kind of compute? It’s still a layer between the model which acts as a parser to enable these capabilities.

Maybe “business” is a bad term for it, but the actual output of the model still needs to be interpreted.

Maybe I am way out of line here since this is not my field, and I am doing my best to understand these layers. But in your terms you are maybe speaking of the model as an application?

This is great! I’ve been diving deep into local models that can run on this kind of hardware. Been building this exact same thing, but for complete recordings of meetings and such because, why not? I can even run a low-end model with ollama to refine and summaries the transcription. Even combining with smaller embedding models for a modern, semantic search. It has surprised me how well this works, and how fast it actually is locally.

Hopefully we will see even more locally run AI models in the future with a complete package.

Yes, I agree totally. But portfolios served a great purpose to expose what you can and what you know to the world and recruiters. Which would then lead to a opportunity to talk about the projects.

We might be going back to a more oldschool approach where talking directly and presenting themselves would be more of a value again. It have always been an higher value, but now it will be kinda more forced I believe.

Another route would be that portfolios become more blog-based, talking about different solutions and problems for each project, as you are saying.

I agree, that would also require engineers to become more invested into core domain problems, which would then lead to more specialised skills (deeper, not broader). My guess is that not everyone actually likes this, but as for now most of the current state points to that direction.

Whatever makes you feel great.

I am kinda in the same boat (but I do not write articles), spending most of my free time either learning or developing.

Frankly, I love it. It makes me happy, so why change it? If I feel burnt out, I usually switch to something else for a short time, but I can mostly switch between reading/coding/watching tech influencers.

So if you do not feel unhealthy (exercise can always help to take a natural break anyway), keep on learning and developing :)

I actually foreshadowed this about 6 months ago when Lovable was starting to gain heat here in Sweden. It was quite obvious that for a start and prototype, these kind of applications are good. But if you are going full SaaS, hire an engineer to set the app in stone.

This might be a new branch of software developers on the rise. Those that take sloppy AI code and turn them into real applications for customers.

Looks clean and all, but is this “multitask on steroid” actually requested, or is it just another nice demo for how agents can perform tasks etc? I just feel stressed that I have multiple tasks ongoing that I would require to switch context between every time anything needs input or fails to deliver what I fundamentally requested.

Excellent insight, and that explains a lot of your decisions. Your junior example is a prime example of why AI can be such an awesome tool, just used correctly. Just awesome!

Interesting post, but this perspective seems to be the main focus, like all the time. I find this statement to be completely wrong usage of AI:

“This is especially noteworthy because I don’t actually know Python. Yes, with 25+ years of software development experience, I could probably write a few lines of working Python code if pressed — but I don’t truly know the language. I lack the muscle memory and intimate knowledge of its conventions and best practices.”

You should not use AI to just “do” the hard job, since as many have mentioned, it does it poorly and sloppy. Use AI to quickly learn the advantages and disadvantages of the language, then you do not have to navigate through documentation to learn everything, just validate what the AI outputs. All is contextual, and since you know what you want in high level, use AI to help you understand the language.

This costs speed yes, but I have more control and gain knowledge about the language I chose.

This is so on point IMO, I feel like there is no better time than to learn more low level languages than now. Since the hype will in the end resolve around insanely technical people carrying all the major weight.

Where do you host your model? I am looking around on where I can deploy one without ruining me financially.

That’s really interesting, what kind of AI implementation have you decided to work with? I am making a similar project but more of an medieval approach. I went with behavior trees since it felt more appropriate and scalable for such a task

I agree, it feels like coding is starting to become somewhat easier since AI can both explain and generate code snippets okay, and is improving over time. So the good old days of just creating an innovative program without major human interactions has passed.

Taking the customers requests and discussing into an suitable feature, without totally shooting down the idea and trying to explain why it won’t work is some of the harder parts of being a programmer these days, at least in my experience.