HN user
me and my team have wasted so many hours (days) working on some product features which was "definitely going viral" only to be forgotten after a few weeks
I believe if we had something like this we could go to market early and understand the user behaviour to build a more scalable and robust system once we were sure if it was even of worth
this is where years of experience working with freshers and junior devs helps, AI is smart enough to exactly do if you clearly tell it what to do and how
unless you understand every inch of system and foresee what issues can be created by what kind of change, things will break when using AI
"Coding was never the hard part. Typing syntax into a machine has always been the least interesting part of building a system."
and I think these people are benefitting from it the most, people with expertise, who know their way around and knew what and how to build but did not want to do the grunt work
I believe it is the way it is because it would cost too much otherwise. You can use the live API for continuously monitoring what the user is doing and if they are stuck but that would be expensive.
Opus 4.6 but cheaper
"I once believed I could help the people building A.I. get ahead of the problems it would create. This week confirmed my slow realization that OpenAI seems to have stopped asking the questions I’d joined to help answer."
i see it happening everywhere
I would suggest you to also use English together with local language just like Flightradar
they waited for more than 1.5 years and they did not forgot
its such a fascinating thing that most people just ignore i too wrote (using AI) an article on Branch Prediction after i found out that most of my team members only read this in college but never understood
do you really want to mention "zone" against all the zones in the zone column?
asia-south is working for me
it "should" be elementary but it isn't, I got the idea to publish something on this because I recently had a conversation with a few new hires
Nobody has mentioned that they were reselling the AWS credits they had. We had them as our billing partner with very good discounts. The day it happened, AWS sent us a mail to remove them as our billing partner.
I'd love feedback on the design, user experience, and any feature suggestions before I publicly launch. Happy to answer questions!
Kafka for communication between microservices, and MQTT (VerneMQ) for IOT devices
the link is broken
incentivizing themselves for building a broken system, you can do anything if you have a majority of market share
it is, when the regulating authority is centralised