![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
Yesterday doing a search using vim for a class that shared a lot of characters at the front with many other classes: /Bas.*Some I could have done a more precise search with better regex, but this was quick, easy, and worked.
Yesterday doing a search using vim for a class that shared a lot of characters at the front with many other classes: /Bas.*Some I could have done a more precise search with better regex, but this was quick, easy, and worked.
Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn’t be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.
It’s still useful when it’s wrong because it can give you the jist of what should be done. If it uses a library or function that doesn’t exist, you’ll still be informed as to what it was intending for the process at that point. I’ve often gone and just replaced the made-up code with custom code that does the same thing.
I expected “Started new project”
It’s surprising how useful ChatGpt is in these situations. Honestly, it’s a great general purpose search engine.
I would agree. Only if the performance is extremely similar but the readability (for some reason) is significantly better for the recursive solution would I choose that.
Cursorless. It’s a spoken-language programming interface that allows the programmer (of basically any language) to use specific words to target existing text, move the underlying cursor/selection relative to that target, and then run a specific modification. Think of VIM but for voice. It runs in VSCode atm as a couple extensions along with an install of the audio tool Talon. https://www.cursorless.org/
My current favorite is mostly Rust-based with the tide crate, tide-jsx crate, vanilla JS, postgres crate, and Postgres in Docker. Super easy, super fast (to develop and run), but I haven’t made any large web projects with this stack yet, just small stuff.
As someone who learned a lot from C++ and that now loves Rust, this annoys me.
I love how the solution didn’t involve changing the prefix to “mcaffee_”. Now users don’t know who to blame. Great. That’s so nice of them.