131–140 of 190 posts
All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.
When there’s a gold rush, sell shovels.
All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.
Talk to people. There are an infinite amount of problems to solve. Deciding whether they’re worth solving is the hard part.
All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.
To summarize: Everyone wants to automate stuff. Most people do not want to touch boring, large problems.
All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.
Steve Jobs used to say every product needs a killer feature AI is a product in search of a killer feature First AGI was anyday going to come. Gpt5 had showed intelligence apparently Then got started adult chat with paying customers
Earlier quoted context omitted.
It is my belief with some exceptions it is almost always easier to teach a domain expert to code than it is to teach a software developer the domain.
For problems that can be solved with only a small amount of simple code that is true. However software can become very complex and the larger/more complex the problem is the more important software developers are. It quickly becomes easier to teach software developers enough of your domain than to teach domain experts software. In a complex project the hard parts about software are harder than the hard parts about th…
Earlier quoted context omitted.
It should be. This is the least friction way to do so as server Linux operating systems still have not agreed on a common application format / package manager.
> It should be. This is the least friction way to do so as server Linux operating systems still have not agreed on a common application format / package manager. Nowhere in your response did you mention security.
Earlier quoted context omitted.
wow, you downvoted me. this is still devops. we use cloud-init to setup the vm. i run the underlying hardware infrastructure and we've automated the provisioning such that we have an api that can start/stop compute at will. even bare metal. the point of this is that the current $/token model is awful, especially if you're using a lot of tokens. it should be $/minute. pay for what you use.
tokens are a rough proxy for usage over time, so I am paying for what I use, less than running a TPU pod myself, required for the models I use, i.e. I don't saturate the compute so it's cheaper to pay-go
Earlier quoted context omitted.
wow, you downvoted me. this is still devops. we use cloud-init to setup the vm. i run the underlying hardware infrastructure and we've automated the provisioning such that we have an api that can start/stop compute at will. even bare metal. the point of this is that the current $/token model is awful, especially if you're using a lot of tokens. it should be $/minute. pay for what you use.
tokens are a rough proxy for usage over time, so I am paying for what I use, less than running a TPU pod myself, required for the models I use, i.e. I don't saturate the compute so it's cheaper to pay-go
Earlier quoted context omitted.
wow, you downvoted me. this is still devops. we use cloud-init to setup the vm. i run the underlying hardware infrastructure and we've automated the provisioning such that we have an api that can start/stop compute at will. even bare metal. the point of this is that the current $/token model is awful, especially if you're using a lot of tokens. it should be $/minute. pay for what you use.
tokens are a rough proxy for usage over time, so I am paying for what I use, less than running a TPU pod myself, required for the models I use, i.e. I don't saturate the compute so it's cheaper to pay-go