How many times have you had a model start compacting already before getting back to you? Most have 1 million context window. It's happened to me occasionally
I also think it's due to normalization of deviance, people are just used to it..
- You can't build a model, because everything will be changed with the next update, so, even if not consciously, people won't do it, why bother learning something that's not going to be of any use next time you use the application.
- because you basically don't know how anything works, it's a coin toss whether it's actually not working, or you're just "using it wrong".
- most things won't do the thing you expect of them consistently, so you don't expect anything of them.
Last night, I uploaaded some documents to my insurance company => modal:
I think the author mistook the phrase a bit.. and there's nothing to be insulted about either.. "Coding was never the hard part" does not say coding is easy.. but that, in the context where this phrase is used, there are other things that are harder than coding. So, if you have some parts, and must pick THE hard part, then coding is not it.
And honestly, I agree. There are more people who can write code, than who cannot. But among those who can write code, there are fewer that can build large, consistent, well-performing systems, or modify them while keeping them elegant.
There are even fewer that can architect them or comprehend the nuances of that architecture.
So, yes. It may be difficult to write code, but that difficult task often exists in a wider context, where even identifying what to write, and where, is orders of magnitude harder, and, it often requires you to not just be able to write code, but to read code very well, indeed well enough to build an internal model of the system which aligns enough with reality that you can decide where, what and HOW to write the code that must be written. And even harder to find the piece of code to delete instead of writing it, to fix the bug or achieve the desired result.
