Same

I didn’t realize you became a designer

It does require active management, but if they have an expertise, I am quite surprised how often I’m learning from them after I give them a problem to solve.

But I higher contractors for a specialize thing (go setup datadog or rebuild our deployment flow) or who is an expert at something (frontend engineer who works only on text editors).

I have had amazing experiences with contractors. I use to think this way and now it’s way more nuanced.

So far, the contractors I worked with have been far the best communicators and very efficient.

Still worth watching!

Then I recommend watching season 4, with Jodie Foster in Alaska.

replace struct with object, and i swear you are writing typescript

Joe Fasano poem--For a Student Who Used AI to Write A Paper

The post is not anti-monorepo, not by any means. but it is truthful about what you are signing up for. And I love the framework to think about this problem, which is you should optimize for fast changes and iteration loops for developers.

"The greatest power and biggest lie of the monorepo is that it is possible to make atomic commits across your entire codebase."

Some gems:

"Any operation over your repository that needs to be fast must be O(change) and not O(repo)."

"Why do you want a monorepo?... You WILL NOT end up with an experience as tight as google31 or fbsource2. You WILL inherit a new set of problems that many-repo setup did not have."

I’m also totally okay with 3 really close friends.