MACRO

A new office suite designed for speed and focus. Source-available, Rust. Hiring in NYC. Backed by @a16z.

[MACRO @macrodotcom]

@karrisaarinen @linear Very nice!

[MACRO @macrodotcom]

Macro is now fully open source! This is a big leap for the open source productivity software category.

As a reminder, Macro = "unified system for work". Email, messaging, tasks, docs, calls, files and crm.

All of this in lives one interface, with unified search and agents that can access everything in one context.

Now that Macro is open source, we think this makes even harder to stomach running your company or team on Slack, Notion, HubSpot, Linear, etc.

Vibe coding everything yourself isn't the answer. A proprietary hodgepodge of tools that don't work together isn't the answer. Macro is the answer for what the future of work should look like: humans and agents working together, with all context in one system.

https://t.co/uyIxzElEs1

Please give our repo a ⭐️ and follow our progress!

[Jacob Beckerman @j_becke]

https://t.co/g9SOzyqghw is now fully open source https://t.co/ncCtVZ60Bj.

Please give us a star and follow along!

[MACRO @macrodotcom]

Custom shareable themes in Macro are pretty cool. As long as you don't click flashbang...

[MACRO @macrodotcom]

@jasonlk Datadog has a reason to exist post-AI. HubSpot ... yes ... but less.

[MACRO @macrodotcom]

@pushmatrix This reminds my of PhysX in Borderlands 2.

[Jacob Beckerman @j_becke]

Me: we need to release every day. We're moving too slow.

Teo: we can't just do that.

Me: why not?

Teo: *reasons* *more reasons* *bonus reasons*.

Me: 😡👿

I am urgent founder. Teo is patient CTO. This is me and Teo's relationship.

In this video we discuss "should we release every day"?

I felt we were moving too slow. We were releasing once every few weeks, leaving DEV and PROD in very different states. Every release required a huge QA cycle. I wanted to ship daily.

---

AI is making the first 80% of building anything, very fast.

And as a CEO, you often don't see the last bit, or it seems unimportant. Or maybe you don't understand why we can't ship v1 and make it better later.

It's really hard to know whether your company doesn't have a sense of urgency, or is making up false hesitations to not JUST DO IT, or there are actually blockers going on.

I ended up getting my way. We do release every day now, and we have for the past few months. Things are moving much faster! But we also followed Teo's process to get there. And we never automated the deploys.

---

A team is a balance of dispositions and you need a variety. Teo and me probably trend towards extremes we wouldn't otherwise *actually* hold if we were making the decision ourselves.

[MACRO @macrodotcom]

@rousseaukazi The second group is probably also a lot less anxious.

[Jacob Beckerman @j_becke]

We recently released meetings in Macro it's been pretty cool to have all our standups recorded, vectorized and available to our AI agents.

We're auto-naming the call, storing the transcript and the recording and creating an AI summary. Yes, you could do this with Granola + Meet + Huddles in Slack.

But it's a lot that can go wrong, or permissions can be messed up, some meetings wont get logged (e.g. on mobile).

In Macro, by default, calls are shared with your team and added to team-level memory. You can turn this off for sensitive meetings that shouldn't be shared with the team. But it's an important design decision that this is the default... if it's not, you can bet your calls won't get logged for the most part.

It's super cool! Now I can ask our agents, or check my "What's going on" dashboard and it includes all of the meetings, including summaries of ones I didn't attend.

Here's 3 of my recent meetings:

[MACRO @macrodotcom]

@a16z Now do Slack

[Jacob Beckerman @j_becke]

We're still figuring out what the best way to show replies is. Slack puts everything in a side panel which makes it hard to find things.

Discord makes everything a new message in the main chat. You can "quote" things to link to the original message but there's no "true" threading.

iMessage does the same as Discord, but with a nice long-press UI that shows you the full thread. I think it's good for friend group chats but not deep technical conversations. For that I think Slack's UI is better.

Reddit — which you probably don't think of as chat — does infinite nesting. It's like Slack, but n levels deep not 1 level deep. And instead of a side panel, nesting is displayed by tabbing replies over a bit.

Reddit is the most powerful, obviously. But perhaps too powerful for "chat". But maybe not... I've often felt myself wishing for multiple levels in Slack. I think infinite nesting might be best for detailed technical conversations.

This is kind of a one-way door decision: if we ship infinite nesting then it's impossible to revert without destroying user data or doing something weird. We might ship infinite nesting just for our team and see how it feels.

What do you think?

[MACRO @macrodotcom]

@icanvardar Which is why Rust is the best now. Or whatever is fastest for your use case that AI can competently write and that has a decent ecosystem.

[MACRO @macrodotcom]

@1ssve The best time to do anything is when you have the dopamine to do it.

[MACRO @macrodotcom]

@kannthu1 https://t.co/SGVr396unQ

[MACRO @macrodotcom]

And I bet you nobody was looking that hard. It would be interesting to know how many white hat hackers we're *actually* trying really hard to break @FFmpeg, for example.

Yes, some pen testers from time to time. But how hard did they really try?

I think this might be like self-driving: humans are great drivers when we're alert, we're just mostly not alert.

[MACRO @macrodotcom]

If more people were pro-longevity, the most powerful argument would be "this is the best chance we have at solving aging and disease." But most people don't seem to care enough. It's too abstract, and if you have a disease the timeline is uncertain. If you don't, it's not top of mind.

[MACRO @macrodotcom]

@rob_mcrobberson I wonder if this aura of venerability will apply to video games. It doesn't seem to be happening. But maybe it takes hundreds of years.

[MACRO @macrodotcom]

It probably is, but I think slower than X pundits say it is.

Like your OP tweet for example, it's great. The pacing, lowercase, zeitgeist-fit... this is why people follow you. Because Claude can't do this.

Our landing page. We tried. AI can't do it. Our app ... yes, the code is 90% generated by AI, but still baby steps.

Was interesting in the Dario/Dwarkesh podcast where Dario said 100% of the code is agent-generated yet they're only moving 20% faster. A year ago, I didn't realize this was a possible world state. But here we are.

[MACRO @macrodotcom]

I was thinking about this morning about how it would be if we didn't use our own product (macro) everyday. It's probably $10m in QA, $10m/invaluable feedback we've gotten... it's just so much different when you actually use your own product. There will be a lot more, and a lot better products, because they're built by the users themselves (who definitionally have maximum need and user empathy).

[MACRO @macrodotcom]

@hewarsaber I know Airbnb tried to bring this back, but it doesn't seem like it is, other than maybe glass?

[MACRO @macrodotcom]

@ClementDelangue I am curious about the game theory here. Like, what about the rest of us software projects that don't get access yet. Might it not have been better to give ever corporate customer access? Or just release it broadly but implement some KYC?