DarkContinent

I was going off this for popularity: https://stackoverflow.blog/2023/01/26/comparing-tag-trends-w...

Is there a relationship between how good a programming language is for coding agents and how popular it is among humans? If so, wouldn't Python be the best language for agents, since it's is the most popular (and hence has the most context available for models)?

Do you pull data from non-HUD sources too?

https://www.realestatesales.gov/

How do you call a library function from a spell? Like something from numpy.

Does your interview process require knowing cloud costs off the top of your head? Because that's hard to track tbh

It's not clear to me from the article how Mantle was porting the build scripts, infrastructure config files, etc across languages. Typically these files don't cleanly translate from one framework to another. Was this considered as part of 20% of project for human engineering effort?

> Batch is just a special case of streaming

No. Designing a system that is always up and running and can process small amounts of data constantly is a completely different problem from designing a system that runs occasionally with a lot of data. For one thing, your output formats are usually different in the latter case (maybe you're creating a PDF for example). Also the high availability requirement just makes things different at the design level.

Finally, the author claims it's not hard to switch between batch and streaming. With a large volume of preexisting data, this is just not true. For example, if you make a REST API call for each document in a DB, it can take days or months to load that. If batching together documents isn't a possibility, how do you move data between stores easily? (This data movement is often required when switching between batch and streaming.)

Re LinkedIn as an example of an economic termite:

It's certainly true that LinkedIn is the go to for white collar professionals seeking to make their resumes visible passively to recruiters. But isn't life still easier with LinkedIn than in the before times, when recruiters would dig deep to get folks' phone numbers and then have to call each of those people individually? (I think the modern equivalent would be email addresses.)

It's true that LinkedIn makes recruiting much easier to scale to a mass market. And it's also true that it has a monopoly on that scaling for professional employees. But is it fair to call them an economic termite when it's still possible to do sourcing in an admittedly clunky and old fashioned way? Just because they have a monopoly on scaled recruiting doesn't mean that they hold all the cards the way Linde (also in the profile) would in the gas market. This is particularly borne out by the existence of Indeed or Stack Overflow as options for posting your resume for recruiting.

Sign in doesn't show an error or log me in on mobile.