Skip to content
Josh Pazmino
ProjectsLinksAboutColophon

Links

software development

39 blocks17 of 39 blocks17 items

excerpt from "Programming is over - quanttype"

quanttype.net⁠

Peter Naur argued in Programming as Theory Building⁠ (1985) that programming is not just about producing program text. Instead, it’s about the programmer developing insights – a theory -about how “certain affairs of the world will be handled by, or supported by, a computer program”.

Mar 12, 202644390494⁠This block isn’t public yet.
Programming as Theory Building - Peter Naur

Programming as Theory Building - Peter Naur

pages.cs.wisc.edu⁠

Programming as Theory Building - Peter Naur

pages.cs.wisc.edu⁠

Feb 15, 2026Nico Chilla⁠43626935⁠
henry@left_padThis block isn’t public yet.
here's @rsnous on the dread of using debuggers: "it's not sufficient to just give people a tool that theoretically does the thing. It has to be integrated in the experience in a way that works emotionally"

ref: x.com/rsnous/status/…⁠
Omar Rizwan@rsnous2020-05-04
… because I dread looking it up
i feel like bash scripting always creates like
bash brain in me
where i write contorted stuff
to avoid having to make conditionals and loops and stuff
Omar Rizwan@rsnous2020-05-04
when I used to TA intro systems programming, kids similarly dreaded using gdb -- they would do almost anything, even if it took way longer and they were completely stuck, to avoid breaking it out
Oct 5, 2020⁠2 replies10 reposts68 likes51165088⁠This block isn’t public yet.
Omar Rizwan@rsnousThis block isn’t public yet.
it's interesting, because I do identify with this (at least more than I identify with the 'computer science is about algorithmic thinking' characterization), but I also know plenty of people who do interesting stuff with code who don't really fit this profile or think this way
Computer Science@CompSciFact2026-06-08
'The psychological profiling [of a programmer] is mostly the ability to shift levels of abstraction, from low level to high level. To see something in the small and to see something in the large.' -- Donald Knuth
Omar Rizwan@rsnous
the idea that you can write a lot of code and/or get the computer to do a lot of stuff without necessarily needing to 'think like a programmer'
Jun 9, 2026⁠1 replies0 reposts14 likes46893125⁠This block isn’t public yet.
Omar Rizwan@rsnousThis block isn’t public yet.
"It's a little frustrating, but I didn't write the algorithm (and honestly don't really understand it); I only ported it."
Oct 5, 2025⁠1 replies0 reposts4 likes40082527⁠This block isn’t public yet.
Linus@thesephistThis block isn’t public yet.
In a well-engineered codebase, writing code is an effective way to plan and design; in such contexts it may be the quickest way to explore a design space.

Said another way, well-written code makes moving around in the program's design space efficient for the programmer.
Linus@thesephist
In this light, it's more useful to evaluate code by how well it circumscribes the space of possible future evolutions of the program, rather than how well it accomplishes its current job alone. Of course, this requires human, organizational, domain context beyond the spec.
Linus@thesephist
A codebase together with a chosen code editor (defined broadly) is thus a user interface for navigating an abstract space of programs. It's much more like a design tool than a word processor in this way.
Linus@thesephist
The job of the modern programmer is adopting and evolving the toolset (the codebase together with the editor) in service of their responsibility to efficiently and confidently guide their users through this complex space. It's about movement and navigation.
Jan 31, 2026⁠3 replies3 reposts62 likes43173258⁠This block isn’t public yet.
Thinking about coding

Thinking about coding

robinsloan.com⁠

Thinking about coding

robinsloan.com⁠

# Thinking about coding

August 31, 2025

In recent years, I have found myself less often in front of the computer, and one result is that I seem to spend as much time thinking about coding as I do actually coding.

I’ve been working on a programming project this summer, one that’s coming together in a really cool way, and its development has been an odd and exciting experience. This week, I had an idea for an important revision; I was superbusy with other work, but/and the plan percolated — on walks, while doing the dishes. Yesterday evening, I had time to tinker, but my laptop stayed shut. Instead, I spent a couple of hours with a notebook. I continued to think about my planned revision as I fell asleep. I dreamed about it — or maybe the loop of thought just kept going, in a way that felt like dreaming.

This morning, I made coffee, finally sat down at my laptop, and … just did it, in one of the more robust, straight-through coding sessions of my life. And the plan that had crystallized in my imagination basically … just worked!

My programming style used to be very much “dive in, start typing, generate errors, learn from them” and I still think that’s the correct approach … but maybe I never realized there was an alternative? More likely, that alternative wasn’t yet available to me, at my level of skill and/or patience.

I’m now convinced that thinking about coding, at a safe distance from the computer, has profound value. I already knew this about writing, about fiction … feels nice to get here with code, too.

(There’s a satisfying thread of connection to programming’s history, the time before interactive terminals, when there wasn’t even the option to “dive in”: only to think, and write your program — the whole thing — and turn in your punchcards, and wait your turn in the queue, and, finally, see the result … !)

Sep 3, 202539262706⁠This block isn’t public yet.
🌷🐰 sonya serendipitously 🐇🎀@sonyasupposedly·Nov 12, 2026
Something on my mind lately: opportunity cost. When you can build ANYTHING, the implicit cost of any given thing is very high
6 replies1 reposts75 likes
Colton Dillion@cadillion·Nov 12, 2026
On the other hand, waiting to build any given thing compounds your opportunity cost

The point of optionality is to exercise it
1 replies1 reposts5 likes
henry@left_pad·Nov 13, 2026
exactly! always love this essay around this, the point of it all is commitment, life requires risk despite ambiguity, leads into ultimately, faith

thecrimson.com/article/2017/5…⁠
0 replies0 reposts2 likes
yen is building stuff@weiyen.netThis block isn’t public yet.
As an experienced software engineer, one hard part of using LLM agents well is unlearning all the learned helplessness.

A lot of things are now feasible to do, I just need to train my mind to understand that.
Jun 23, 2026⁠3 replies2 reposts82 likes47285639⁠This block isn’t public yet.
Tyler Angert@tylerangertThis block isn’t public yet.
I miss repls and the feeling of running a script and seeing it print out
Sep 22, 2026⁠3 replies2 reposts48 likes50682855⁠This block isn’t public yet.
😇@turtlekioskThis block isn’t public yet.
i hold a simple but it seems uncommon opinion which is that writing software is often a creative practice but also that the discipline is changing a lot and you can't stop it but the way to reckon with that isnt dismissal of its creative potential but acceptance of change
Nov 12, 2026⁠1 replies1 reposts21 likes52722688⁠This block isn’t public yet.
😈@turtlekioskThis block isn’t public yet.
when people port enterprise software that aren't games completely straight they're inheriting a code structure that is a reflection of a corporate structure that doesn't apply to them. software isn't just solutions to problems, it's social embeddings of organizations
😈@turtlekiosk
it's extremely obvious when you look at a google product and there are 3 different places for 3 different "settings". they're each the purview of a different team with its own power structure. when you make your own version of this software, you need to collapse those
Oct 13, 2026⁠5 replies4 reposts72 likes51378037⁠This block isn’t public yet.
😈@turtlekioskThis block isn’t public yet.
the exact way that software engineering isn't real engineering also allows them to spend a lot of time building information technology tools
amy@amypretzel2026-07-11
software engineers get github, stack overflow, and open source. mechanical engineers get a 40 year old PDF of machinery's handbook and vibes
Jul 11, 2026⁠1 replies1 reposts26 likes47791953⁠This block isn’t public yet.
thebes@voooooogelThis block isn’t public yet.
one thing learning programming by modding minecraft did for me is inculcate a deep love for runtime reflection and monkeypatching. the telos of software is to have a hard shell and a gooey and malleable interior. like an oyster or lobster
Feb 9, 2026⁠9 replies13 reposts327 likes43452300⁠This block isn’t public yet.
サメQCU@sameQCUThis block isn’t public yet.
maybe it's timeline bubble but i feel like access to the frontier models is making the people vibecoding more interested in mathematics, physics, programming in general, yada yada yada.
サメQCU@sameQCUSep 7, 2026
working with materials and tools you don't understand is the primordial infancy from which all mastery and awareness must begin.
obviously there are more ethical and less ethical modes-of-being-infant-towards the exterior world, and we can strive to be laudatory in our infancy.
Sep 6, 2026⁠2 replies2 reposts50 likes50191763⁠This block isn’t public yet.
Learning to code is still worthwhile

Learning to code is still worthwhile

stevekrouse.com⁠

Learning to code is still worthwhile

stevekrouse.com⁠

July 6, 2026

Jul 6, 202647641924⁠This block isn’t public yet.
Steve Krouse@stevekrouseThis block isn’t public yet.
the problem with "spec driven development" is that most software can't be spec'd up front

software is a creative act, where you figure out what you're building as you build it

you need to get your hands dirty in the details, and react to incremental versions

it's telling that all the examples of spec driven development are sorting a list or porting thoroughly tested code (like a js runtime or browser engine), which are the exception, not the rule. the vast majority of software doesn't have a spec – or if it does, the spec was created *after*
Jul 12, 2026⁠202 replies134 reposts1,838 likes47816684⁠This block isn’t public yet.
previouscodegennextthermal printing
Are.na⁠Bluesky⁠Twitter⁠GitHub⁠LinkedIn⁠Email⁠