One of those silly little issues with inbuilt software that drives me insane is the number of times I’ve had to log back into Apple Music or Spotify (or one of the video services to occupy the kiddo while parked for extended duration).
That’s another one that phones have just solved with the integrated password manager. The friction of providing credentials on my other devices has been reduced, but all of a sudden I need to go hunting through that pwd manager, and hunting and pecking on the infotainment keyboard, to enter a 20+ char unique pwd that modern “best practices” has established. It got bad enough for a bit (swver changes resulting in needing to re-log in) that I stopped using all of these apps for 2-3yr on our Model Y because I got tired of having to do it.
I think what’s become more interesting/impactful for me is why they elect not to support it.
Most firms moving away from it (or who never implemented it) seem determined to either sell additional subscription services to their user base (connectivity) or sell their user base to a third-party (either as data, or eyeballs). And for a product at this price point I find myself very annoyed at the attempted payment extraction.
Either way, I’m with you. Lots of vehicle manufacturers out there that will support it.
Amusingly for the security information processors in the US (which handle US Equity consolidated quote and trade data) the trade feed is still referred to as the tape (one of the two governing bodies is called the Consolidated Tape Association). Securities are still associated by which ‘tape’ their trades print on (really which one of the two SIPs the trades will be found on).
It existed prior to GME as well, which really should tell you that anyone who is using this is going against people who have spent the last decade at least perfecting signals based on this exact same data.
The hope isn’t that you find some unique signal to trade on. The hope is you find some signal that does not scale in a meaningful way, so it is less likely professional firms are going to devote resources to trading it.
If you stumble into a fresh, scalable signal it’s unlikely it will continue to be profitable after six months. Once you scale to any real profitable size the market will notice and either change behavior, or trade the same signal at a faster speed.
And to extend this, low frequency does not mean slow speed. HFT mostly covers how often you are trading. Some low frequency strategies require near instantaneous (sub microsecond) execution capability in order to beat people trading on the same signal.
While true (I 100% agree with you in the distinction), the statement is “Your agent acts before the market does”, which is simply not going to be the case (assuming this is helping run some sort of trend following strategy). Professional traders who are sensitive to alternative public data sources are already taking that data in quickly and their execution is colocated with the venues. You’re still going to be significantly behind the curve (to a financially dangerous extent in my opinion).
I was trying to think of a way to word this exact argument. I think it’s especially easy when your business technology is not your primary means of revenue generation. Having these execs understand how things work is significantly less critical in these scenarios, so it becomes much easier to hire for alternative characteristics (golf game, pedigree, gender, whatever).
Easier to justify monthly costs than big capital asks (even if your infra is depreciated at a normal rate) is where I think many saw (incorrectly) cost savings. It’s also a bit of these execs mortgaging the future, banking on either being out of their role when the real cost comes due or that people will have incredibly short memories (not a wild assumption).
> I've never seen anything like it for a technically optional tool
Cloud had a very similar vibe when it was really running advertising to CIO/CTOs hard. Everything had to be jammed into the cloud, even if it made absolutely no sense for it to be run there.
This seems to come pretty frequently from visionless tech execs. They need to justify their existence to their boss, and thus try to show how innovative and/or cost cutting they can be.
Interestingly the realm in which I have domain experience has similar constraints, but based primarily on physical transport latency and less on bandwidth. There has been a move in some spaces towards hyper-dense deployments, but it’s a very small amount of the total compute capacity due to other limitations.
Still, the world I’m used to operating in is typically 5-10 kVA/rack.
Oh, I have no doubt it is functionally efficient. I'm just amazed given the system deployments I've been party to, and the tiny amount of per rack energy usage comparatively speaking given the functionality of those systems.
Like, what in the good god damn are we using all this energy for?
That is interesting. Never considered trying to throw one or two into a loop together to try to keep it honest. Appreciate the Visor recommendation, I'll give it a look and see if I can make this all 'make sense'.
I think that's the issue I have with using these tools so far (definitely professionally, but even in pet projects for embedded systems). The mental load of having to go back through and make sure all of the lines of code do what the agent claims they do, even with tests, is significantly more than it would take to learn the implementation myself.
I can see the utility in creating very simple web-based tools where there's a monstrous wealth of public resources to build a model off of, but even the most recent models provided by Anthro, OpenAI, or MSFT seem prone to not quite perfection. And every time I find an error I'm left wondering what other bugs I'm not catching.
I know I'm running a bit late to the party here, but maybe someone can provide some color that I (on the slightly older end of the spectrum when it comes to this) don't fully understand.
When people talk about leaving their agents to run overnight, what are those agents actually doing? The limited utility I've had using agent-supported software development requires a significant amount of hand holding, maybe because I'm in an industry with limited externally available examples to build am model off of (though all of the specifications are public, I've yet to see an agent build an appropriate implementation).
So it's much more transactional...I ask, it does something (usually within seconds), I correct, it iterates again...
What sort of tasks are people putting these agents to? How are people running 'multiple' of these agents? What am I missing here?
Can't speak for ML training, but I absolutely love using the OODA loop as a simplification of the decision and operating pattern in competitive industries. Boyd really did put together an easy to understand framework to help describe where an organization/process needs to tighten up.
Yeah, I think the issue has more to do with the curiosity level of the participant rather than whether they are a business domain expert or a software engineering expert.
There’s a requisite curiosity necessary to cross the discomfort boundary into how the sausage is made.
I worked in the Swedish office of a multinational for a couple of years and the one experience I had where Swedes were selling a complex multi-million euro project to Germans was one of the most bureaucratically filled initiatives I’ve ever experienced in my life. Not sure if the project ever really took off, but I’m thankful I was able to avoid it beyond the initial week of discussions.
The issue has less to do with intelligence silliness, and more to do with the fact that the overall geopolitical objectives of the US can not be trusted, and that rift has grown to a point where self-reliance on critical infrastructure may be in Europe’s best interest.
That’s another one that phones have just solved with the integrated password manager. The friction of providing credentials on my other devices has been reduced, but all of a sudden I need to go hunting through that pwd manager, and hunting and pecking on the infotainment keyboard, to enter a 20+ char unique pwd that modern “best practices” has established. It got bad enough for a bit (swver changes resulting in needing to re-log in) that I stopped using all of these apps for 2-3yr on our Model Y because I got tired of having to do it.