3,665 karma · joined September 13, 2007
This is knowledge that goes back to the beginning of software development - "Plan to throw [version] one away".
I think this could potentially become a good practice. LLMs make it so easy and cheap to just get it working and build that v1. Then you can play around with it and see if works and read the code about what could be better. Throw away the LLM generated version and now this is the part where human expertise comes in. Based on what you've learned from the v1, now guide the LLM more closely about how to write the thing and help guide it so that making small PRs that are easily reviewable and understandable are the output.
Hosted services are only great for setup and scaling. You're not going to need scaling. Infra setup can now be done easily with AI and terraform.
https://mattmccormick.ca/we-re-all-managers-now-my-journey-i...
But just to add on for comparison, the NHL has 1312 regular season games. Plus 4 rounds of best-of-7 playoff series with 16 teams making the playoffs. Let's say an average of 5.75 games per round, that's 86 playoff games bringing us to ~1400 games per year.
Over 4 years, that's 5600 games. The FIFA World Cup had 104 games this year. It's actually pretty impressive that the WC can even make 40% while hosting < 2% of the games that the NHL has. Or put another way, 1 WC game is equivalent to 54 NHL games - 2/3 of one team's full regular season.
One of the names in the byline matches his HN username so it's likely this.
"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
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.
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.
We've already seen the effects of social media algorithms that route people into isolated bubbles. This is going to exaggerate it.