pipingdog

> So, you start out with a system that’s very plastic but not very efficient, and that turns into a system that’s very efficient and not very plastic and flexible.

> It’s interesting that that isn’t an architecture that’s typically been used in AI.

No? That sounds exactly like training a model, then applying the trained model.

I scream when I eat glass

In most birds vocalizations serve an evolutionary purpose, such as maintaining territory. Why could this not be autonomous?

I've started answering the question "What do you do?" With "I study primate behavior."

> Jammu and Kashmir, an area of 12.5 million people that is claimed by both India and Pakistan

It would seem that India has the more practically demonstrable claim.

The most important part of a fast car is good brakes.

As a BBS user in the 80s I believe you. It was a common feature, usually referred to as the twit bit.

Reminder: Beresheet means In The Beginning and is the title of the book of Genesis in Hebrew.

If you are an interrupter, learn to raise your hand. If you get interrupted, immediately raise your hand. If you notice someone try to say something and get clobbered, raise your hand, then cede to them. If you see a hand go up, think about how to tie off your point, then call on someone with a hand up.

I will be 53 this year. I am, strictly speaking, an IC. A leaf node.

The company where I work administers a survey of all tech employees every year, then publishes the results as a series of graphs, which can be broken down at any branch in the org chart. The very first question is "how many years of industry experience do you have?" The graph for my team is, shall we say, bimodal. There's a bell curve between 1-4 years, and a spike at 30 years.

I've been building things for a long time, and I try to impress upon the other developers on my team (or in my org) that I've never, ever, had an opportunity to build at the scale that they're being asked to build at in their first gig out of school. If I come off as negative, it's only because I can say with surety that X won't work because it didn't work in the past. I expect to learn, with my team, whether we can make things work at now scale.

There are times that I miss hours and hours of uninterrupted coding, and being inventive at small scale. My leadership would take me out to the loading dock and kick the shit out of me if I tried to contribute at that level.

My job is, essentially, to educate, and slap the team off of local optima. To impress upon them that their customers are king, and that their customer base includes themselves and their teammates, paged out of bed at 3am. And to impress upon their management and the business that we really to need to focus on improving operations, rather than add features from time to time. It is also to observe the progress of, and advocate for the developers on my team.

I feel (at the time of writing... Talk to me on Monday afternoon) like I'm lucky that my employer points senior engineers at problems like this.

A study by the University of Sussex found that multitasking (specifically, consuming multiple media sources at the same time) is _associated_ with reduced density in the grey matter of the part of the brain associated with empathy, cognitive control and control over emotions.

The study doesn't say whether one thing causes the other.

http://sro.sussex.ac.uk/50361/

I don't work for Google, but in my shop, my code has to have 2 ship-its or I can't even get it into the build stage of the pipeline.