jwmcglynn

After using it, I think this is a great start. As I mentioned in the previous comment, I really like the UX, and this is specifically about:

- The Pen tool feels intuitive.

- I like how the Objects panel shows previews of each layer.

- It is nice to see clip-path support integrated well, and features such as converting text to outlines, and boolean operations - these seem like rare features.

Here's some critical feedback after using it:

- Keybindings to switch between tools would be useful, and they should be annotated on the tooltips

- I'd like to see zoom/panning supported with Ctrl +/- and panning when holding space and clicking/dragging.

- When editing groups of shapes, it is hard to select individual shapes in the group. Double-clicking switches to the Nodes tool, which is not exactly what I want. I'd like something where double-clicking a group goes into some sort of "Group Isolation" editing mode.

- When using the Pen tool, I'd like to be able to go back to tweak the previous points, such as adjusting the control points, etc.

- Undo in Pen mode does not undo the insertion of points in the path, instead of Undoes operations from before the shape was started.

- Text support seems limited, for example an embedded @font-face did not render correctly. Similarly for filter support. If the editor doesn't support these features I'd expect them to at least be rendered correctly by the browser, but it seems like SVG rendering here is independent.

It's been a while since I tried Inkscape, but I downloaded it again to give honest feedback.

For context, I got started with Illustrator 9 as a teenager (this is making me feel dated, it was released in 2000), and I'm very familiar with the Illustrator UX and find it intuitive.

When using Inkscape, the UX just feels slightly off, things like:

- Weird keybindings, e.g. pressing Ctrl +/- does not zoom/unzoom

- The golden path feels buggy. When launching the window is for some reason cropped to the top 1/8th of the screen and needs to be resized, and the artboard is tiny.

- Usability issues, such as selecting paths does not show their outline, and the layers window doesn't show a preview of what's in each layer

- Exported SVGs are needlessly verbose. This looks like it has gotten better but is still there. For example, exporting an SVG with two gradients actually puts four gradients in the file (combining with inheritance).

I'm sure that spending more time with it would help, and Inkscape does seem quite powerful, but UX is a big factor when I adopt new tools and Inkscape is lacking there.

I am one of the few people who used the open source version and really liked it, and I'm disappointed by the changes.

The challenge I had with Sourcegraph is that it's out of reach of developers working on personal projects. There isn't a hosted plan, and for my projects I can't easily open source them due to my employer.

I was really excited when the Sourcegraph App was released, since it allowed me to give Sourcegraph a try on my project without going through the complex self-hosted setup. I went as far as getting scip-clang working with my Bazel-based project, and then tried out the docker-compose setup on my home lab.

Now that code search was removed from the app, and this change, I'm concerned that I won't be able to use Sourcegraph for my personal projects in the future.

This is a missed opportunity. I think individual developers using products for personal projects are powerful advocates, since those developers may convince their employer to purchase the product. If I could I'd gladly pay, but I'm just one person and can't justify $5k/year.

For asking basic questions all the time, I still do this as a senior engineer. At large companies, this is due to tribal knowledge, and one of the best things that can be done to reduce tribal knowledge is to take notes and make some simple docs.

If you had to ask someone how to open tickets? Create a short doc or wiki with those instructions.

That's a good way for even a junior engineer to start producing value, for established teams they often have tribal knowledge without realizing it.

+1 to this. As a senior engineer, one of the big things I've learned is asking good questions, finding who to ask, and having the confidence to do so.

Junior engineers aren't expected to do this alone, your senior engineers should be there to help you as you learn to do this yourself.

For me, it's still a bit intimidating asking questions to people 2+ levels above me, but the biggest thing I've learned is that those people want to help me. For more senior engineers, it's their job to help you: You're not wasting their time.