shinkim0914

Eraser | https://eraser.io/ | Full-time | San Mateo, CA | ONSITE | Software Engineer

At Eraser, we're building the copilot for technical design. We're the leader in AI-powered diagramming and have built a platform that includes proprietary diagram-as-code implementation, a free-form infinite canvas, and a markdown-compatible document editor used by hundreds of thousands of users every month.

Interested? We'd love to hear from you. Please send your resume or LinkedIn and a brief explanation of why you're excited about this role to [email protected].

I'm the founder of a startup that makes a diagramming software for engineering team called Eraser.

If you want a codified set of rules that you can mechanically apply, I would look at UML and C4. However, I'd argue that the frameworks are overkill for the vast majority of engineering diagram use cases.

For the general scenario where you're just trying to communicate a technical concept clearly without spinning your wheels a lot, here are a few tactical things I'd recommend:

1. Pick the right diagram type for the job. Sequence diagrams are great for API documentation, ERDs are great for database schemas, flow charts are great for user flows, data flows and logical flows.

2. Use icons where possible. A database icon, a S3 bucket icon, a cylinder shape are all a lot more expressive and easier to grok than a rectangle with text inside that says "database".

3. Focus on the nodes, groupings, and connections. That's really all there is to a diagram if you break it down. If you just make a list of nodes, groups, and connections that you want to represent, the diagram will almost just draw itself.

4. If you're looking for a quick way to start jump start a diagram or looking for inspiration, try AI tools to see how far they can get you.

> Generate DDL directly generate SQL statements to create your database tables.

Looks like it's capable of turning a diagram to SQL too? That's neat!

For those that are interested in an GPT-powered tool, we have a project that can generate diagrams from code of any language or natural language: https://eraser.io/diagramgpt

Hi HN - Excited to share DiagramGPT. Diagrams are helpful to have but painful to draw. What if you could generate diagrams from what you already have? Like code or project descriptions?

• Code → Diagrams

• Natural language → Diagrams

Would love to get feedback and happy to answer any questions.

https://eraser.io/diagramgpt

I do foresee pricing pressure ahead for them as a lot of competitors seem to arising.

Why doesn’t that happen elsewhere?

Yes, it’s still risky. But at least you’re still understood because of the pervasive startup culture in SV. Everyone in SV can relate to startups. I think what’s tough outside of SV is that people don’t relate to startups. People might think you’re just weird.

There is no place like Silicon Valley where taking a career risk to quit a job and start a company is normalized, understood, and encouraged.

If this sets them on a self-sustaining path without having to rely on running highly conspicuous donation campaigns on Wikipedia, I think that's a wonderful thing.

Raw data here if anyone is interested https://docs.google.com/spreadsheets/d/1nqBLGT6PnhAJqBa3ZAkO...

Accounting tables often do this. This is not the perfect example, but here's a flavor of that. (last page of PDF) https://s23.q4cdn.com/574569502/files/doc_financials/2021/q4...

Timing is everything :) Would appreciate feedback!

Thank you!!

Thank you, let me know how it goes :)

Hi HN,

This is Shin and I'm working on Eraser.

Visual ideation and brainstorming is tough via Zoom. During WFH, I wished there was a lightweight whiteboard that didn't have 30 buttons on it (looking at you, Miro). For things like visualizing half-formed ideas, on-the-fly architecture discussions, and sketching lo-fi wireframes.

Eraser is a canvas for visual collaboration. It's built on Excalidraw – the awesome open-source drawing tool with a hand-drawn feel. On top of it, we've added a file system, team-based access control, as well as a Quill-based text editor for meeting agendas and notes.

Here's the app (https://www.tryeraser.com) and the marketing website for use case inspirations (https://www.tryeraser.com/home).

It's still very early, but would love your feedback on Eraser!

This is why remote mature companies like Gitlab emphasize transparent communication and highly discourage private channels / DMs. Otherwise it is much easier for individuals to become silo-ed in a remote company than in a onsite company. Remote teams need to overemphasize transparent and public communication.

Agreed, weather cannot be the only reason. What drives the population decline in Chicago despite the low CoL?

I've also noticed in the job post data that remote-mature companies prefer employees with remote work experience. I'm guessing it's partially due to this problem of difficulty of getting juniors up to speed remotely.

The cost of living in Chicago is amazing for a Top 3 metro. My theory has always been that the winter weather discount is baked into the CoL.

To clarify, your company didn't stop hiring remote, it just stopped making a cost-of-living adjustment to salary offers to remote candidates? Did management also increase salary for existing employees who lived in ow CoL areas?