This week, I’ve made many updates to Stenography after having some great conversations with developers. I’ve made the API 2x as fast, and have improved the UX of the VSC integration by adding easy commit to file functions for the AI to write docstring comments.
As Stenography wanes out of the development phase and into the management and growth phase, I’ve had more time to step back and examine what I’ve learned along the way. The piece below examines systems, why they’re important, and what it means to be productive in a post-AI world.
The goal of copying code is to find stable code blocks. Stable code blocks have low entropy, will last through many updates, and work on systems with different levels of computational power at their disposal.
Intuitively, a programmer understands this fact. An expert programmer can look at a block of code and determine how error prone it is, where it will fail, and how long it will take to run on average with a quick O(n) analysis.
Once we stumble upon or meticulously edit a code block until its just right, we need a place to put it.
Read it here: https://www.bramadams.dev/slip-box/A+System+to+Copy+More+Code%2C+and+Write+Less+Code
ars longa, vita brevis
Bram
P.S. a personal shout out to https://www.gued.is/ for helping me set up my Obsidian in my personal domain. More power!!1!
Create your profile
Only paid subscribers can comment on this post
Check your email
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to sign in.