Marcelo Sousa

@Jobvo @sqs Totally agree with Job on this one !

@sqs No. Take the train to AMS and rent a bike there. You can do it, but it’s not a nice ride from the airport to AMS.

I'm going to AMS for 2 nights. It sounds like a fun idea to rent a bicycle at the airport and ride to/from my hotel (~16km, arrival around 5:30pm). Is this actually a good idea?

@sqs @sourcegraph Congrats!

Congrats to our @sourcegraph team on a great quarter! We smashed our ARR goals for both self-serve and enterprise, and we shipped Cody Enterprise GA, the leading code AI (on context, LLM choice, and scale). Highlights: - Hit 188% of our Cody Pro (self-serve) DAU and revenue goal - Beat enterprise ARR by so much that we're already ahead of our entire H1 plan - 67% of customers deployed on Sourcegraph Cloud - Earned our 20th+ customer paying us $500k+ ARR Thank you to our customers and team! And if you want to join our mission to make it so everyone codes, we're hiring.

As a mertonian, this was hard to watch. It wouldn’t take much to get this right Masters of the Air!

Super excited about the next phase for Reviewpad and the team. A big thank you to everyone involved in this journey!

Code, commit, celebrate! We're excited to announce that @reviewpad is joining @snyksec to help developers stay secure without slowing down! 🏃 💻 Check out the announcement blog for more info. 👇 snyk.co/uf61s

@FreddyMallet dives deep into three checks of our newly launched Reviewpad Check. Discover how these can help you and your team be more productive! Read the blog post here: reviewpad.com/blog/reduce-fr…

You can understand that GitHub Universe is coming by the number of recent incidents on @github.

Exciting news: we just launched @reviewpad check, a pull request linter that spots and automatically fixes issues.

@dependabot and @renovatebot are pretty useful to update dependencies but can lead to a huge number of open PRs. Check out how you can use @reviewpad to supercharge those PRs 🚀🚀🚀🚀 In only 41 LOC of our DSL, you can: - Specify when a PR only touches dependencies with file extension groups; - Specify when a PR touches high risk dependencies through queries over the diff; - Automatically merge PRs that only update low-risk dependencies if the build passes; - Automatically assign the right developers to PRs if the build fails. Crush those open PRs! youtu.be/GDwH5GbpckE?si…

🤯

Wake-up call: just read some comments from a code review that I wrote about 4 years ago and they seem unnecessarily harsh. Not cool old me.

Erroneous string manipulation is the main source of security vulnerabilities. I saw it in js eval, sql injections and now we have a new culprit in prompt injection.

@reviewpad It would be awesome if @github supported comment streaming. IMO, that's a huge UX limitation nowadays when you're plugging LLMs into it.

GPT-4 based AI agents capabilities on code explainability are incredibly useful for pull requests. Here's an example on a @reviewpad PR. For someone that has been doing static analysis for a long time, these are really exciting times!

Pull request debt is real. I’ve seen it in countless teams over the past years. A long list of open pull requests which will never be merged. Reminds me of the old cars in the dealership that are just becoming more and more of a liability.

Changed my profile photo and it requires manual verification on the blue status. It’s been days… shouldn’t AI quickly this verified?..

Weekly reminder that pull request experience on vanilla @github still sucks. Lots of talk about improving developer experience but very little to show for. If we spent the amount of resources on reducing CI times by 10% on it, the impact would be tremendous.

Very relevant thread on understanding the ROI of LLM capabilities that require a lot more expensive training

I've seen a lot of teams using checklists on pull requests without a way of enforcing them. Here's a demo where I use @reviewpad to protect merges from happening when the checklists are not completed: youtube.com/watch?v=NAhBzD…