glumia

+1 we ended up adding something to our CLAUDE.md specifically to counter it. Something along the lines of "comments should be treated the same as production code, they shouldn't leak the content of conversations and stand the test of time". It doesn't always work, as other people say claude stops following these the more its context window gets filled, but now it's mostly a matter of telling it in a new session to review the changes against the guidance on comments and clean them up.

Hi there!

In the last few weeks I worked on this library that allows you to profile functions or sections of Python code.

I started to work on it as I couldn't find a simple way to use 'external' profilers like py-spy in the context of AWS lambda functions nor was I satisfied with existing profiling libraries like pprofile.

The main idea was to create something that would make it straightforward to profile lambda functions and generate data for flamegraphs, but at the same time would be extensible to be used in other contexts and for other purposes.

It is now in a state I consider stable enough to be used in production and I would like to get some feedback before eventually releasing a v1.0.0 and freezing its API.

Let me know what you think :)

Thanks!

Yeah sorry, I used an instruction (last array element access with the a [-1] syntax) that was added on bash version >= 4.1 and macOS uses by default 3.2. What you described is exactly what happened when you tried to execute the `search_alias` function on the macOS terminal.

Anyway, I just fixed it, check latest release :)

This week I defined some aliases for the commands I use the most at work. Problem is, despite having defined the shortcuts, I continued to use the commands in the old complete form. So I built this tool to help me build the new muscle memory for them!