I recall a similar quote from Elton John that I'll paraphrase:
"I've had a lot of hits so you'd think I'd know in advance which ones will become hits. Songs that I was sure would become hits went nowhere and some songs that I didn't think anything of became my biggest hits"
> I built a SaaS in a few hours. It does its job better than tools people pay real money for.
It's easy to build something for yourself that solves your own use case. You know how you work and what's important to you. Most of the effort in software goes into understand people other than you and building guardrails for them.
> Whatever niche tool you’re sketching this week, a thousand people can prompt a working version by Sunday night
A lot of people on HN are naturally builders. For them it's fun to play around with AI and see what can be built. Not everyone is like that.
For individuals, how many people actually want to spend their weekends building a niche tool for themselves vs just paying a few dollars a month to access something that does the job even though it may not be perfect?
For businesses, the buy vs. build tradeoff does now have some new compelling evidence in favour of "buy" but there's still maintenance needed for the service internally, there will be people with feature requests for it. Before you know it, the company is diverting resources away from their core business for a support tool that doesn't really drive impact.
I think we'll see more options in the marketplace as individuals will be able to get started more easily but SaaS is far from dead.
Reading and understanding documentation and producing clear, written requirements will be more critical than it is today. We've always known documentation is important but it's frequently glossed over in many projects and not taken as seriously as code reviews. With AI though, it's going to be much more important that all requirements are written down clearly and captured.
Even the CEO's "apology" is pretty bad. He still finds a way to take shots at the original poster saying his original message was inflammatory (could also be read as how I'm justified in my response), that "he started it" and that the team was "spoken down to or treated dismissively" which they weren't. All the original feedback was about the project and was not directed at specific individuals.
Wow, you sound exactly like me - except I have a bit less years of experience. Let me know if you want to connect to help keep stay motivated (email in profile)
Bezos' parents lent him $250k to start Amazon. The point is that by the time Bezos started Amazon they were wealthy and could provide him this safety net. Not many middle class families would be able to loan their kid that much money.
Reminds me of a blog post I once read from a manager writing about all the qualities of being a good manager. I read it nodding along that they all seemed like good traits. Then in the comment section there was a post from someone saying something like "You were my manager at one point and honestly you were one of the worst managers I've had in my career. I didn't see many of these behaviours from you". The author responded with something like "I don't disagree. There's sometimes a gap between knowing and doing"
The same principle holds for quality management. You don't need to inspect every single product. However, if you inspect a small number of products at random, you'll detect a large percentage of the quality issues.
While leaders can't know everyone they should make it a priority to have those random connections outside their inner circle. If they don't, they become in danger of hearing only the info that their inner circle wants them to hear.
> Sycophancy, in which chatbots agree with and excessively praise users, is a trait they’ve manifested partly because their training involves human beings rating their responses. “Users tend to like the models telling them that they’re great and so it’s quite easy to go too far in that direction”
We've already seen the effects of social media algorithms that route people into isolated bubbles. This is going to exaggerate it.
The missing context here is that their company looks to be a very small team - 5 employees according to LinkedIn.
Any process or methodology, or lack of, will work for a small sized company. At that size you get things done by just talking with each other. That doesn't scale to companies with hundreds or thousands of employees where multiple teams that you've never interacted with before may be involved in a project. These "throw out the processes and methodologies" articles are always written by people at small companies. Once they grow, they'll implement the same processes that everyone else uses to solve the problem of becoming too chaotic.
"I've had a lot of hits so you'd think I'd know in advance which ones will become hits. Songs that I was sure would become hits went nowhere and some songs that I didn't think anything of became my biggest hits"
It's been a long time since I heard this so I'm probably mangling it. A quick search shows that he probably did say something like this though https://www.birminghammail.co.uk/news/showbiz-tv/sir-elton-j...
The lesson is - just put it out there and see what happens