316 karma · joined November 11, 2010
Look into some examples of the section 2.4 "Derivatives of Matrices, Vectors and Scalar Forms"
- the overregulation narrative conflates two different problems
- and that you minimized too much the consumer benefits of EU legislation
I think the overregulation problem olis less that we have 200 EU regulations and we need to hack and slash 100 of them and more that we have 100 national regulations 25 are exact transcriptions of EU directives, 25 are transcriptions with tweaks and the other 50 are national scoped regulations and what we need to do is to make them uniform so that companies don't have to deal with 27x75 problems.
I'm a bit burned by politicians using the overregulation narrative and then not specifying a single example of a meaningfull rule that they would get rid of. Usually what is left in the air is that worker rights and consumer rights should be cut.
In any case where I live fans are not a meaningfull stopgap measure.
What is failling to see the overall picture? I hate this overall picture mysticism. I bet that if people where given the same role and information as the CEO they would be able to see the overall picture.
If you have huge salaries, yeah sure 500 dollars its okay even if you only get 5 10% more productive.
I have a hard time believe their time is worth less than $75/hr or so.
In many places in Europe it is.- The AI researcher might be working for a lab or company with much less funds than the top dogs. Are they likely to discover something that is worth it before a bigger model becomes more capable?
In a sense they don't seem very exciting because all of this required generality.
What I'm facing right now is a 10 year monolith modularized with applications. Like a sibling comment already discussed these applications are not reusable application so almost all advantages of having that are moot.
Now, the consequence of having this structure is that we now have complex dependencies between the migrations of these apps i.e. cyclic dependencies, dependecy constrains that are underspecified. Thousands of migrations that now take a significant amount of CI time. We would like to squash them but it requires a lot of review and manual work and if we keep using multiple apps we are going to ave the same problem in the future.
The only meaningfull gain we had with multiple apps is that we have less migration conflicts when people create migrations concurrently.
Is that advantage worth the pain? I don't think so.
Instead of apps you can just split your components inside a single app using regular python modules.
- Django apps are an anitipattern for large internal / single purpose products due to migration overhead as FKs cross application boundaries
Totally agree with this. Now we have thousands of unsquashable migrations that require a ton of work to fix.