tdj

In my experience, I have started to believe ML Engineer is short for "YAML Engineer".

I built a similar app using a Kaldi's nnet3 model running embedded; the thing was so responsive that our demo to an SVP went sideways: when he gave a query, the app responded nearly immediately after the sentence ended. The SVP did not realize it already responded, as the expectation for voice interaction systems was that it takes like 2-5 seconds to get an answer, which made the impression that the system did not work properly.

So, moral of the story, if you do a too good job of making a fast speech engine, especially for multi-turn dialogues, add some delays so it resembles human dialogue more.

Both of the titles you mention were the type of books that I had to put them down and started reading them again later. For different reasons though. Once the world building clicked, they really shine.

The building I live in in Berlin, 1910-ish construction with two more wings in the courtyard, everything accessible through the front gate - it has the same principle implemented with a timer and a button. I thought it's a bit odd, but made some sense after a while.

During the day, the front gate can be opened from the outside with just pushing a button that unlocks the door. At night (from 20 or 21 or so), the button stops working, you need the key. It can be opened at any time from the inside without keys. So it's more or less implementing the same protocol, but electro-mechanically, so there is no need for the trick with pulling the key inward.

My beef with Slack is that everyone in this comments section is pretending it's an async communication tool, but that is only true people that are used to working without context switching and acknowledge that interrupting someone has a cost. For everyone else, there is an expectation of prompt responses, or you are considered untrustworthy if you take too long to respond.

I suspect a lot of frustration fundamentally revolves around trust. If there is a lack of trust, it must get compensated with an increase in visibility. Slack just happens to be a decent tool to provide visibility.

Story time: in a company I worked for, the Most Senior Engineer requested to be exempt from participating on Slack as the only person outside management, and skip the daily stand-ups. He did get a lot more done. I envied him quite a bit - mostly because our stumbles and challenges (just normal development stuff) were very visible and prompted lots of nervouse queries from PMs and sales people via Slack about why our tests are failing and why we needed to refactor code, whereas he only needed to show the end result of his work after a few months. Even if we had both experienced the same amount of 'challenges', his way of working gave him a lot more credibility because he got to control the narrative where his solution emerged working as designed (because any development hurdles he may have had were invisible to our PMs and sales). However, he did have a lot of pre-existing trust with key people to pull this off in the first place.

I hope I get to a point in my career where I can operate like that.

Krško is a Westinghouse design. I've spent quite some time in the area, and nobody really worried about the power plant. The smell of the cellulose plant in the city center on the other hand, ...

Their hypercube covering formalism can be seen as decision tree induction with a specific partitioning rule, and terminating branching only at uniformly labeled leaves. But try are using the tree nodes as kind of an embedding to apply a softmax on. I like the connection between relus and the geometrical representation, makes it easier to think about in spatial terms.

Reading this I got several dejavus to my grad school classes on classical ML stuff. I like the direction but it feels like it could be better if it admitted that it's a variant of decision tree embedding, and built on some of the massive amount of research work in that area. At least in terms of understanding.

I suspect doing a random forest version of this would actually help. Perhaps we will see this as a legit pre-training step.

After interacting with a post about yachting, the ad engine behind Instagram suddenty thought I am a multi-millionaire and I got a ton of ads on fancy watches, McLarens, Bentleys, and of course boats. Felt good for a while.

Not sure how many do this, but you're basically describing my situation, 8 min commute to Mitte, and relatively cheap. Due to the rent control, rents only jump after tenants change. An identical flat to mine, below me, was just now online available for rent for about 20% more than my rent is - and got rented out within a month, so there's demand.

I don't think there's a fear for displacement yet, there's quite a few plots to build up, or abandoned places that are torn down (e.g. Stattbad), and a bunch of new modern apt buildings coming up. But for now, it looks like Neukölln is the more desirable next-hip-thing.

One common pattern I had to frequently use was HSET of the same key on multiple hashmaps and different values. Not quite HMSET, but MHSET was a good name for it.

Actually once you have information on depth (which isbwhat they get from multiple camera perspectives), and your bas image at near-infinite DoF you can pretty much dial your depth of field however you want. Actually your next limit is how accurately you can measure depth, and that is limited by the distances between the individual sensors.. With a longer baseline you could do pretty thin focused slices, and blur the rest.