I commented not so long ago to people very invested in AI, agents and tokens that are very enthusiast that I would not use an agent for security reasons and loss of control (besides suboptimal output).
It seems I was not wrong.
Not that I do not use AI. I do: fenced, always pasting my snippets and NEVER giving access to my code. Always from the browser. I know what it can do well and which workflows accelerates for me. But I do not want to think that my whole project ends up somewhere else.
> Most people don’t reason their way to conclusions and then feel accordingly. They feel first, then reason backward to justify the feeling.
That is how sales work, if someone is ever interested in increasing sales and one of the pieces of advice that opened my eyes the most. It is like the argument: hey, stop reasoning about features with your potential customer and making them bored: make an impact, something that creates reaction. Good or bad (bad is even better than indifferent sometimes).
Something that provokes emotion. Otherwise they are going to be indifferent.
They are not going to end up buying bc of the features most of the time anyway when there are ten or fifteen similar. They will do it bc you cause some kind of emotional impact, be that trust, authority or something else, though those ones are pretty important.
You cannot blame like this the administration when you make any regulatory mistake such as not knowing a rule or not being able to enforce it in practice.
It is amazing that we have regulations for everything and that when they cannot enforce it, they blame someone else.
Different way of dealing with people depending on who, not what.
When I choose Python for something, it is clearly for its speed.
It is nice to have the speed, always. But in Python, it would be a mistake to do it at the expense of flexibility. Same for typing: it is great to have it. I use it. But Python should be dynamic and the rest and extension that does not compromise everything else.
If a JIT can make Python 2 or 3x faster, or even 10x for some workloads, that is nice. But the language itself should support same idioms, reflection, dynamic typing, etc at the same level.
I am not sure if this is even possible since I have no experience implementing JITs, but maybe it would be a good idea to make it pluggable so that it does not unstabilize other parts of the interpreter in a way that it can continue development?
Not who you asked but I think the meaning is that since intrinsics for simd are different in each platform, being able to have something that is portable and sometimes works faster is something, while writing for Intel, ARM and a zoo of instruction sets is not an option for some.