Dang, that's rough.

> I realize that part of the reason I have not been able to appreciate a work of art before is because my mind tends to anxiously attempt to absorb information, without slowing down to absorb visual work in a linear fashion, rather choosing to keep track of as many details as possible from the image it perceives, then move on.

I would actually recommend not trying to ingest linearly (as in a raster scan) but as a Breadth First Search. Try to unfocus a bit (your eyes or your mind) and not analyze anything at first. The key is to maximize perception. Only after you are able to "feel" the piece should you dive into the details.

> profundity

word of the day?

Are they trying to say some negative outcome in Africa is caused by the Mercator projection?

Idk if "owed" is the right word here, and I disagree that the disparity is from being "smarter". There are plenty of people with high analytical intelligence that are not paid very much. Think about how poorly some very smart academics are often compensated.

Maybe I'm being reductive but it seems more simply that the disparity is based on "how much leverage/influence do you have over those with the money".

This is the one that really got me to giggle. I can tell this is going to stay buried in my brain for a while.

I always find maximalism jarring and this was certainly no exception.

very good way to put it.

I am currently building a piece of very modular software and it has been the hardest-to-design project of my entire career. I would never be allotted this amount of time-effort at any job I have held to make something this robust and clearly defined. Many aspects of this project have taken 3-5 rounds trying-and-trashing to get an abstraction that is uncomplicated.

This is precisely why vibe coding is so successful for building tiny isolated scripts, and so disastrous for anything else. It's just really dang hard to build something large and simple.

https://hank.bond/posts/highlighting-my-code-based-on-how-mu...

It makes sense to me that agents with known tool sets should be able to safely create ad-hoc "tool recipes" that are not arbitrary code execution but are kind of arbitrarily composable from allowlisted functions. After reading thru this thats what this appears to be.

I guess the addition of the json call graph makes this easier to wrap in a durable execution primitive for easy restarts.

> This presents a problem for the typical way that academic papers are written, which is to do all the work in a coffee-fueled fugue in the last few days before the deadline, then stay up all night writing the paper and finding citations for the pro-forma “related work” section which you did last but you know that the reviewers will insist upon

I have zero exposure to academia but chuckled because thats often what I do for blog posts :P

I have never had a "really deep conversation" about my career at a mid/full year review. Often, that's where I get feedback about something that happened months ago I was unaware my manager thought needed improvement.

The in-the-trenches feedback mentioned in the article would be an improvement over the lack-of-any feedback.

All of my favorite roles were actually not ones with the most interesting technical challenges, they were the ones where I felt like I had real leverage I could wield through my manager. If you want to get anything meaningful done, you need buy-in from leadership, and it's very difficult to get that when your manager is not on-board.