• 0 Posts
  • 352 Comments
Joined 9 months ago
cake
Cake day: June 5th, 2024

help-circle
  • When I started in software, my first employer was just phasing out punched cards for programming. One of my jobs was to work out how programming would be done using terminals instead of the old workflow of submitting coding sheets to card-punch operators who would then pass the jobs on to operations. Typically you’d find out if your code compiled the next morning. There was a big basket by the computer hall where they’d deposit your card deck and a massive printout on fanfold paper of the job status and (if it went tits up) the stack dump.

    By that time (late 1970s), cards had sequence numbers (usually numbered 10, 20, 30 so you could interpolate a few cards if need be). If you dropped a deck on the floor, you had to carefully gather them back up (so they wouldn’t get bent or torn), feed them into a card sort machine, and wait until the deck was sorted. You could also run a special batch job to clone a card deck, for example if you wanted to box it up and ship it to another location.

    The big challenge with cardless programming was that computer reliability wasn’t great in those days, so you needed reliable persistent storage of some kind. That was generally magnetic tape. Disk drives were way too expensive, and optical disks hadn’t been widely adopted yet. So to save your work, you used tar or some non-/Unix-OS equivalent. There was version-control software, but it was primitive (rcs, which later had svn built over it).

    On the positive side, you could compile and build without an overnight wait.



  • When I got into the business in the late 1970s, there was strong selective pressure in favor of people being capable and smart. Back then, software didn’t offer a lucrative career path for people with good memories, conformist instincts and a superficial command of MBA jargon. The people who had coding jobs and who didn’t wash out had it in their blood. There were lots of bullshitters, just as there are now, but they failed rapidly and were driven out.

    I’m a bit younger than the OG greybeards (and a lot younger than people like Don Knuth). I’ve been in the business for longer than most coders have been alive. During that time, I’ve reskilled more times than I can count, and I still write code, though it’s mainly prototype and proof-of-concept stuff at this stage in my career, when the development team gets stuck.

    And that’s the thing: I’m not there to block new people from submitting pull requests. I’m there to help get the job done. If you find the whole process opaque and need mentoring, just ask.
















  • The abstraction away of the idea of files and folders is a deliberate user disempowerment strategy by app and mobile OS creators. The underlying concept is that the app owns the data, you don’t. It also conceals the fact that use of standard file formats and directory structure conventions were developed to facilitate interoperability: apps come and go, but the data was meant to live on regardless. Of course, vendors want to break interoperability since doing so enables lock-in. Even when the format of the underlying content is standarized, they’ll still try to fuck you over by imposing a proprietary metadata standard.

    Just another example of enshittification at work.



  • A family member is an audio engineer (now also a producer) who owns a good recording studio, and we’ve A/B tested lossy vs lossless on good equipment. He hears things that I don’t, my ear is somewhat untrained. But at mp3 bitrates below 320, I can hear compression artifacts, especially in percussion instruments and acoustic guitar. But if you’re listening in your car or while wearing Bluetooth earbuds while you’re out walking, you probably won’t notice unless the mp3 bitrate is really dismal.