Some notes on how to ship fast and why it matters. This is from my perspective as a indie dev and a startup founder, but I think some lessons here for everyone.
When the engineering department of a company is not the major lever in the company's growth this philosophy might be fine. That's the case of many large enterprise and probably many startups too.
When the competitive advantage is not the technology, it is probably smart to make the engineering department dumb.
Clearly that leaves the company exposed to challengers who will outcompete them with technology. But not all markets work like that.
Creating and using virtual environments in Jupyter has always felt a little painful. Now thanks to uv things can be so much better. I've integrated uv into my Jupyter notebook client, Satyrn. It makes quick experiments in a fresh virtual environment so much easier.
Thank you for the advice. I get how this might be better suited for a regular blog post rather than Show HN. I will repost it in a month or so. Hopefully some people might find it interesting.
Great feedback, thank you. I've heard this before. I'm thinking of keeping the default but adding an option in settings to "ask before installation" for users who prefer that behaviour (similar to VS Code).
Maybe the first time it happens you pop up with a confirmation dialog and it has a checkbox that says something like “always ask” (and an option in the settings).
Thanks! I just used the builtin MacOS screenshot tool to take the screenshots. I used Tailwind to style the page. I really like the default shadow that the "selected window" screenshot adds, but since there are also "selected area" screenshots I decided to take them without the default shadow (by holding option) and then add it in using Tailwind.
The logo was done with ChatGPT and my friend editing it with some graphic design software :)
This project is unrelated to those others. I like the branching code idea tho, would love to have something like that. I'd love it if you could rewind your code execution to a point in time and then play it forward differently. I suppose that would be a pretty big memory overhead tho.
Even as a command line power user, I still wish it were easier to install dependencies while working in a notebook. If I'm working on a project I don't want to have to switch to my terminal if I can solve the problem in one command from my notebook.
With a little careful thought into good UX I don't see why it can't be easy for a beginner at the same time useful to a pro user (and still compatible with any virtual environment).
Great, many thanks! And yes, I hope to have something to share in some ~12 months time. The goal ie to be essentially an SQL client that (a) benefits from ducker's excellent performance and flexible SQL language, and (b) has data-science-helpful features, like the ability to filter or reorder columns with the mouse (or keyboard) afeter the data is queries.