gpt-emacs-macro VS emergency-poncho

I wrote a quick integration to the GPT-3 API to Emacs [0]. Although it's a very simple implementation, it's made many small things I would've previously done manually much quicker (ie - one-off calls to convert a hyperlink in X format to markdown; abbreviate first names of author lists of papers; convert some "text message speak" messages into a paragraph).

[0] https://github.com/samrawal/gpt-emacs-macro

I made something similar for emacs and it unlocks what I think of as “semantic macros” — being able to interface with GPT-3 for actions that are a tiny complexity level above what I usually use kbd macros for (like smart capitalization) easily become possible to automate!

Screenshot - https://twitter.com/samarthrawal/status/1591527892386734081

Code - https://github.com/samrawal/gpt-emacs-macro

Thanks! It's available here -- https://github.com/samrawal/gpt-emacs-macro

I've created a tool for replaying HTTP archives:

https://github.com/Tade0/emergency-poncho

There are many like it, but this one is mine.

Useful when you're a front-end developer and the backend app is not easily deployable locally and the test environment is down.

Also with it you can make a blazing-fast, browsable snapshot of JIRA.

https://github.com/Tade0/emergency-poncho

This is a HTTP mock server for reproducing issues on the front-end using a recorded HTTP archive(.har file).

The gimmick is that for a given endpoint it stores all the responses and serves them in a round-robin sequence.

This way you can simulate situations where e.g. a request has been retried after the JWT expired, or something special happens when an item is added to a list, and the list is refreshed afterwards - basically every case in which you need backend state.

It works... sometimes. Each new project I'm in uncovers new issues.

That being said with the test team giving me both videos and .har files of the bug reproduction I was able to solve a few long standing bugs in one legacy system.