bebrws

Other than keeping up to date with how to best use AI/harnesses what else would be most important to stay on top of for retaining a software engineering job these days? Also AI seems generic to me. Could I bother you for a more detailed breakdown on the most important topics/skills you would consider necessary for a software engineer to be knowledgeable of?

I find Claude Chrome's extension to be much more powerful than Cursor's current browser integration. Especially if I need to debug something that requires being logged in to a system that uses SSO for example. This repository will allow you to use Claude's Chrome extension from Cursor against the currently selected tab in your already-open default browser. I created this so that I could take advantage of Claude's Chrome extension from Cursor: Cursor calls a local helper script, the script activates the existing default Chromium browser session, opens the Claude side panel, sends a prompt, reads Claude's final response through macOS Accessibility, and returns that response to Cursor so Cursor can continue coding or editing files.

Handheld, or best on the lap. Has some nice zoom and scroll functionality.

Using whisper.cpp's stream build I used a few keywords to decide when to send what data to chatGPT which is then written back to your terminal. Crazy with the $150 per Interview web application solutions I saw in the past.

It's as simple to use as running a build and run command.

After running a command in the terminal, I often find myself needing to run the same command again, without wanting or being able to easily re-type the command or use the arrow keys (think mobile). This post contains ZSH scripting that keeps track of the last non-empty ZSH command prompt/buffer and runs it whenever I send a few empty lines by pressing the enter key 2 times in a row.

Yes, I know we should all be good enough to not need to ever use console.log statements, or to even iterate for that matter but sometimes I find myself tired and working on a project and just want to double check my data structure is in the correct state. If I use console.log I risk the chance of forgetting that line of code and submitting it to LeetCode which will cause a failure. Using this comment based approach makes logging easier and is "LeetCode safe" in that no console.log statements will ever be executed.

In this blog post, I show how I created a preprocessor that takes any line starting with “// log -” and creates a temporary intermediary file where those lines are replaced with console.log statements to print any expressions following “// log -”. This approach is useful in several ways. It’s easier than using console.log directly, and when run without using the preprocessor, these log lines are simply ignored. The entire setup is straightforward, utilizing a Node.js environment variable/option to run the preprocessor.

Previously, I used a custom bash script to compile repository files into a single context file, but Zed AI’s implementation is far superior, offering a more streamlined and effective solution. But it never hurts to have an alternative method laying around. Like this little shell script..