CodeSee 2.0

Google Maps for your code workflow

Thank you so much @chrismessina for hunting Codesee! We're super excited to share CodeSee 2.0 with the product hunt community.

If you are interested in trying CodeSee.io you may have some questions or need to convince your boss to let you try it. We’ve put together a template on why you need a Google Map for your code workflow.

Why CodeSee?

CodeSee will help me to rapidly understand the code I’m trying to write because it visualizes the code and its connections. The faster I understand what code is there and how it works the faster I write new code.

Ok but how?

CodeSee’s code visibility platform is 4 parts, explore and prep, code, review, automate. You can explore your code by automatically visualize your services, your code, and you can layer on your architectural knowledge on top of the code. This is a super flex because CodeSee platform is super flexible and we can add features, gotchas, tech debt, plan that refactor we’ve always wanted to do, integrate that open source repo and so much more. This will help me make sure that I don’t miss hidden things in the code. Next you can gather all of this information to help you write code faster.

When you're ready you can throw up a PR and you can visualize your change and it’s impact on the rest of the codebase. Basically do a self review. When you have it just right and you’re ready for reviews from others you can visually walk people through your pr for a super quick code review filled with what and why you made the change the way you did.

Once your code is merged, you can automate everything that you learned. Code Automations help you automate your code knowledge. Do you forget what to do when you do a migration? Need to touch the auth file but always forget what soc 2 requirements need to happen? Need to change the routes file but forget to tag your boss? Code Automations can remember for you and only show up to remind you when you’ve changed the file.

Hmmm but what does it do?

Here’s a quick 2 min video describing it. Once, you watch it, you will see how it fits in with our org priorities. If you don’t either I or CodeSee’s team will be able to elaborate on how it will help us.

Will the installation take me away from my workload?

No. It’s about 10 clicks to install.

Is it secure?

Yes. CodeSee is Soc2 type 2 compliant and adheres to the highest security standards.

How much does it cost?

I can try CodeSee for free but some of the extra security features and Code Automations we may want are just $10 per month. And I think we may want to know where in the code our endpoints are being consumed so we need an Enterprise account to get Service maps. The CodeSee team has already agreed, they’d work within our budget to give us a good price.

Can the rest of the team use it?

Absolutely. But all of CodeSee’s information is synced with GitHub so if other members don’t use it, it’s all good. Does it interfere with the rest of the team’s work flow? CodeSee is integrated into our preexisting workflow like on GitHub and in VS Code. So while CodeSee is available if other team members want to use it, the day-to-day of team members who choose not to use it remains the same.

Got more questions?

If you have any questions, please feel free to check out our FAQ page otherwise me and my team will also be available for any questions or feedback in the comments.