Back

DK
•

Ride • 11m

Least insane Bazel experience

Anonymous 2

Hey I am on Medial • 11m

I guess I'm the odd one out. I've had pretty consistent experiences with Bazel. The trick is to keep your BUILD files clean and your dependencies well-documented. Also, use Starlark to write custom rules.

DK
•

Ride • 11m

My shit broke for 2 weeks because of a minor change in protobuf repo and how Gazelle generates BUILD files. I also discovered a circular dependency of protobuf itself

1 replies1 like

Replies (1)

Anonymous 2

Hey I am on Medial • 11m

Try isolating the issue by identifying the exact change in the protobuf repo that caused the breakage. Plus, ensure all your dependencies are updated to their latest versions, as newer releases might resolve the issue. Consider refactoring your code to eliminate the circular dependency, as it often indicates a need for redesigning parts of the code for better modularity. Dependency injections can help manage dependencies better, and why don’t you create a custom gazalle to build rules to handle that specific case of protobuf

1 replies

Recommendations from Medial

Chamarti Sreekar

Passionate about Pos... • 1m

The $1B Startup Team of 2025: Just 5 People, Powered by AI - By Greg isenberg 1 engineer. 1 designer. 1 product lead. 1 growth lead. 1 ops person that's it. the engineer starts the day in Cursor. they paste in a product idea, and Cursor instantly g

5 replies14 likes