🔥Telegram İfşa

Just had our biggest month in terms of reviewing and merging PRs on our core team, with team size over the same time period increasing at a much smaller clip. Love to see it.

hey 👋 the “large open source Next.js application” is us 😍🥰

20 years after almost doing aerospace eng and not computer eng, have come to realize a beautiful link between them: balance. Tests Too few - too risky 100% coverage - pedantic Git Chaotic - hard to collab Extra clean - pedantic Planning Little - confusion A lot - rigidity

The infra building has only just begun. What a way to start with Origin UI and Pasquale Vitiello

New blog up about how we'll take learnings from Cal.com and apply them to coss.com engineering. cal.com/blog/engineeri…

Keep the team lean and focused on delivering amazing open-source software and support. 🦾

Our Docker setup has been ported to our main repo calcom/docker -> calcom/cal.com Looking forward to better supporting this moving forward and to seeing amazing updates from our community. github.com/calcom/cal.com…

We got hit with a DDoS of about 10 million requests around an hour ago. Fortunately many were blocked by Cloudflare but the others, although 404s, took up DB resources and crushed our app. Fixes coming soon. Apologies for the disruption.

I get asked a lot "what are the most important skills I need to join cal.com?" As a small engineering team doing the work of a team double its size, technical skills are only a part of the story. You have to grind hard, be humble and love autonomy.

Having a deep dive with our internship cohort: In the age of AI, what does learning mean to you now that much of the process of getting to the final result is done by AI? I think answering this question is incredibly important to properly continue growing.

Don't be afraid to have closed, unmerged PRs on open-source repos if you are exploring. Many times those explorations help you find a better result. I have 119 closed, unmerged PRs on github.com/calcom/cal.com and it's all good.

Someone convince me: Now that LLMs can easily write boiler plate code for DB layer crud + help with harder SQL, why would you choose to use an ORM knowing their side effects in terms of perf?

While everyone is checking their wrapped music, I’m checking wrapped Cal.com eng. 3,283 merged PRs 194 releases 266% increase in perf work 123% increase in refactors 28% total output growth Love our team.

We reached out to all self-hosters directly but if you have been running any version of Cal.com yourself, make sure you are updated to github.com/calcom/cal.com… as it contains the patch for the very dangerous RSC vuln.

Have always been a big fan of underdogs and small teams doing amazing things. If you keep your head down, study hard, work hard and dedicate yourself to your craft, you’ll put yourself in a position for success, regardless of the path you choose to take.