brettgriffin
also, are you using a tool to collect those metrics? what is it?
I'm following this trend on Twitter. It's shown a few abhorrent ones, for sure. But mostly just benign interactions with people who have to do this ten times a day, every day.
This does not mean that R is on the only cost (T-R grows over the life of the company). It does not mean that, even if R were 0, you could launch a product. But R is a real cost.
This (correct) thesis should illicit an interesting question about the future of SaaS markets: What happens to the SaaS markets when the cost of code approaches zero?
Coincidentally, the company that authored this post is a perfect case study.
Few people truly grasp how hard bringing a software product to market is. The feature density required to even begin selling your product often requires more human capital than early stage investors are willing to underwrite. Some founders have the background to command those terms, but most have to wedge into a market with some very small insight.
I was at a dinner with the CEO of Greenhouse in 2021 and vividly recall him explaining just how deep the feature set of a new ATS needs to be to even enter the consideration set of a buyer.
One serendipitous way companies could enter these markets is by being founded in one market, and pivoting into another. Ashby didn't start as an ATS. They were originally targeting a mid-market ERP (a hot thesis at the time). Ashby is a prime example of a company that likely could not have entered their current market because of the sheer engineering resources required to break through (and kudos to them for doing it!)
But as the cost of code approaches zero, the deterrents of entering the market also drop to zero. The next Ashby could just pursue ATS from day one. In a sense, this is the entire story of humanity and especially software (consider the cost of building an ATS in 2012 when Lever was founded vs the cost Ashby faced in 2019).
But the slope of this change is unlike anything before it.
ATS, like many other markets, has a handful of big players and a long tail of smaller offerings. No matter how many long tail providers there are, the economics of entering a market suppressed that number compared to what can and will exist tomorrow. The cost of building an ATS a decade ago was literally orders of magnitude more than it is today.
In 2016 I heard a A16Z partner describe a future where every software market would have offerings in virtually every little niche one could imagine. Years before the LLM renaissance, this sounded insane. How could the market afford to build and sustain each offering?
I don't think companies are going to start building their ATS in house, but I do believe that cost of producing code is approaching to zero, and that means hundreds or even thousands of offerings will exist in every shape, way and form we can imagine.
I learned a lot about Craig Venter after reading My Life Decoded in college. Truly an amazing person.
It looks like they paused hiring for some number of weeks after the law was passed, probably because someone forgot to update the job listings and run interference on the salaries.
That's what you're upset about?
[0]https://www.businessinsider.com/digitalocean-pauses-hiring-i...
Your priorities are completely wrong. You need to redirect the time and energy you're spending on this project towards getting back to stable ground, starting with utilizing the safety nets that your government and community make available to you. You need to find psychiatric care and shelter immediately, and eventually, gainful employment of any kind.
The critical piece here is the anecdotal (but true) insight that engineering orgs have been flattening over the last few years.
There are a lot of factors, but rarely discussed is the realization that senior engineers are completely capable and often willing of managing other engineers directly. The definitive text on this subject is literally called "Herding Cats" :facepalm:
In reality, senior engineers often have strong communication skills (albeit different than the styles of other management and leadership positions), very good time management, and likely can perform many of these 'soft skills' that engineering management is doing out-of-band from the teams directly responsible for shipping software.
The engineering manager role feels like it was borne out of a very west-coast ideology from another era responsible for removing agency from people based on dated stereotypes. There was a self-fulfilling prophecy wherein we said engineers aren't capable or willing to have agency to work across teams, manage resources, or communicate about career goals or blockers, and then plugged someone in the middle to take these activities away from engineers.
I'm exposed to a lot of teams with high-aptitude/techincal people that are not software engineers and almost never do you do see the equivalent of a traditional software engineering manager.
I wouldn't be surprised to see a continued and dramatic compression of these roles going forward.
What top are you referring to?
We're in a thread about a US company announcing its new $30B fundraise from a group of elite US growth investment funds arguing about whether this company will be able to overthrow the $4T US tech behemoth and suggesting that all the other US tech behemoths are actually stifling progress.
Also, that writing tone is obnoxious.
Probably not. A vast majority of families in the US raise children without a nanny. If the "only" preclusion is 'I don't have enough money to hire a nanny' but becomes satisfied, the requirements will likely evolve to something greater and continue indefinitely.
Empirically, that group exists, but they're often the minority to the "I just don't want kids" and "focus on other things" groups[0].
As others have pointed out, the world's population grew dramatically in most other times in history when the world around us was more harsh and less certain.
[0]https://www.axios.com/2024/07/25/adults-no-children-why-pew-...
The world is better today in every conceivable way for more people, than it was at any point in history. But it isn't good enough for enough people, and the people who remind you of that are usually doing the least to improve anything, for anybody.
I don't really understand why. It seems fall under this larger victimization umbrella. The best answers I've seen for it are that it is either some cathartic response to just how good things have gotten, or that the complaint itself represents some marginal effort, enough to elicit a dopamine response.
I was born in the 80s and have vivid memories of the 90s. I absolutely loved everything as it was at that point in time. But to look at the world around us today and to think anything before was the peak is just incomprehensible to me.
They will wait and see if there's any deal heat.
Are you talking to other funds? You need to talk to as many funds as possible in a 2-3 week period to create leverage. Do not talk to a single or small number of funds in a process[0]. Best case they will snake the round at a discount, worst case you'll give up a ton of leverage and kill the process.
[0] unless you have close relationships with a stable of funds. you do not.
It's sort of surreal to feel the change in the software development lifecycle over the last 24 months - what you are describing will very likely become the norm amongst most developers.
> Cursor is happily charging me something like $100 a day. If anyone from Cursor is reading this – is there a “solo dev building absurdly large systems” discount tier I’m missing?
I'm also paying a similar bill (but honestly I think it's incredible value). I'm curious about this comment though - I picture LLM pricing as consumption rather than per-seat (token in/token out) - would it really make sense to offer volume discounts on a single seat versus total volume? These platforms shouldn't really care about how many developers are consuming the tokens, just the total consumption, right?
You may not need to use an ORM, but hand writing SQL, especially CRUD, should be a terminable offense. You _cannot_ write it better than a process that generates it.
Rather, users traverse that through that object graph, narrowing a range of keys of interest.
This hacker news article was given a surrogate key, 46272487. From that, you can determine what it links to, the name/date/author of the submission, comments, etc.
46272487 means absolutely nothing to anybody involved. But if you wanted to see submissions from user pil0u, or submissions submissions on 2025-12-15, or submissions pertaining to UUID, 46272487 would in that in that result set. Once 46272487 joins out to all of its other tables, you can populate a list that includes their user name, title, domain, etc.
Do not encode identifying information in unique identifiers! The entire world of software is built on surrogate keys and they work wonderfully.
The surrogate key's purpose isn't to directly store the natural key's information, rather, it's to provide an index to it.
> The solution is not to come up with yet another artificial identifier but to come up with better means of identification taking into account the fact that things change.
There isn't 'another' - there's just one. The surrogate key. The other pieces of information you're describing are not the means of indexing the data. They are the pieces of data you wish to retrieve.
I don't follow the benchmarks closely, but I know quality and speed when I see it. ChatGPT feels like its from another generation compared to the others.
But that does open the door to a very interesting question (far outside of the scope of this discussion): would people change their habits of brushing their teeth if that hazard didn't exist, e.g. your dental repairs were free? D:
Asking for the same reason I asked OP my question. I was just in Berlin and, second only to Tokyo, I've never* seen such conscientious group of people, including teens.
* I'd actually place two other cities from that trip into the same #2 position: Zurich and Vienna.