I do see a world where every corporation would use agents-friendly platform to create their own accounts, crm, hr software. The insurance will come from the platforms vendor support.

>Read the Sqlite file in this directory and create an UX that would visualize and manage the data. The application should be responsive (so it can be use on mobiles) and should have some graphs when appropiate.

|> it inspired me to create this small game.

It was inspiration, not a simulation nor it claimed to be realistic. This is the type of artistic license that game designers have always had at their disposal.

I am a developer and I do my personal budgeting on a spreadsheet. It was easier to setup and maintain, and follows my process better than the personal finance software I have used before. Could I have made a little program for this? Sure, but it would be time consuming and I have better projects to spend my time on.

Wouldn't that account for the other 10%? To me it sounds like the quote is not too far off when you consider that he said "of what matters today". There are many other things missing from that list that might become more relevant tomorrow.

With so many smoke and mirrors demos out there, I am not super excited at those videos. I would play with it, but it seems like it is not available in a free tier (I stopped paying OpenAI a while ago after realizing that open models are more than enough for me)

I guess it depends on what you mean by serious. Pre-training a competitive LLM with current methods and consumer hardware is prohibitive for sure. Solving a classification problem could be totally doable depending on the domain.

>might make you a better programmer, it won't make you a better software engineer

I think it is a short-sighted definition of SE but in any case, there are not any mention anywhere in the article claiming that this was aimed to software engineers.

Also, although I appreciate the concerns of "Not Invented Here" doctrine, we also have the other side of the spectrum, where we don't know how to do a left-pad anymore [1], and introduce dependencies everywhere.

The third point is that I don't think that having more knowledge on how things works contributes with the "Not Invented Here" mindset. I would argue is the opposite. When engineers are hungry on learning, they find excuses to make address that appetite at work, but once they know the tradeoffs and amount of effort to make it work, they will think twice before starting anything from scratch.

[1] https://qz.com/646467/how-one-programmer-broke-the-internet-...

That's a reductionist way of looking at it, but an alternative way would have been what Daniel said on that letter; They were "more productive and less efficient and they needed to be both".

From my ivory tower I do see some things that could have been done differently, such as adding only one new offering (maybe just podcasting), or rely more in contractors than employees and set the temporary expectation of the roles up front.

[1] https://www.amazon.ca/Revolution-Valley-Paperback-Insanely-G...

From Wikipedia: In 1974, Liskov and S. Zilles defined a strongly-typed language as one in which "whenever an object is passed from a calling function to a called function, its type must be compatible with the type declared in the called function."

Note that the definition refers to type declaration, both being optional in Python and Common Lisp, so I wouldn’t use either as an example of strongly type languages.

To be honest, this is a matter of styles, coming from a dynamic type background I don’t appreciate strongly typed systems as an advantage.

Well the singular use of "They" is actually pretty old [1]. I don't think it is confusing readers as they did mention a name.

> I just can't help rolling my eyes at this nonsense.

I get the frustration if you are not used to the usage of the pronoun in its singular form, but it is actually sensible

[1] https://www.scu.edu/media/offices/provost/writing-center/res...