Jim Nielsen’s Notes

Quoting others & adding my 2¢ — a link blog by me.

Bio: Mikkel Malmberg

githubnext.com

I like this description from Mikkel Malmberg, Staff Research Engineer at GitHub Next:

I approach problems from the user perspective. Sometimes that means making the button prettier, sometimes it means optimizing database queries in background jobs. A full stack engineer by necessity.

I identify with that.

how to enter side doors

substack.com

Quite enjoyed this take from Maja.

a job is not really a thing. A job is a bundle of problems someone wants solved badly enough to pay another person to solve them.

A company is a group of people trying to make something happen in the world. They have problems and bottlenecks. They have things they know they need but have not scoped. They have things they do not yet know they need because no one has shown them. They have obvious jobs, which become job posts, and illegible jobs, which hover around the edges as unsolved tension.

The point is to create proof that you are already in relationship with the problems you want to be hired to solve.

via Steve Krouse’s Legibility

Oh, and loved the line about how things like blog posts, side projects, open source work, etc., can be “small ambassadors for your mind”.

The Open Secret Buried in Anthropic’s 300-Page I.P.O. Filing

nytimes.com

Paul Ford:

As much as I love computers, democracy is the more important technology.

Writing to me with AI

cassidoo.co

Cassidy Williams:

I really dislike this vibe on the internet right now. It feels like I’m constantly having to avoid being “tricked.” It makes me sad when I open an email and I’m like “ooh yay, someone enjoys my newsletter… oh wait” or when I see that I have a bunch of notifications that end up all being the exact same spammy format.

Yeah, I feel this.

Vale has an interesting workaround for this — I might have to try it.

Fortune Telling and Speculative Design

maggieappleton.com

Maggie Appleton:

I don’t think design engineering means making fancy micro-interactions and posting them on Twitter

Dayum — shots fired! But also: agree 1000%!!

Wait, so what is a “design engineer” exactly?

My preferred definition is a designer deeply involved in the technical craft and material of software. You’re a designer, but you help make decisions about functionality and architecture in code.

Also, lol for this great take on San Fran:

When I go to San Francisco – which I officially hate – everyone has theories. You go to a party and people tell you their theories, though often they’re all the same one.

How long have we got before the agent output is enshittified?

rachsmith.com

Rach Smith, quoting my post, gets at things more succinctly than I did:

I remember when Google Search gave great results, when Facebook and Instagram genuinely kept me connected to my friends' lives, and when Twitter was a fun place to network and make connections in the industry. Every single one turned to shit in pursuit of profit.

Yes, exactly! How long?

How long until the incentives begin changing? What company can resist the ability to print money from other companies eager to influence generative output? (And how transparent will that be?)

“We should be more ambitious with the software we build”

danluu.com

Dan Luu nails one aspect of our current moment in the software industry:

people are out there shoveling out huge piles of crap and calling it gold

Bill Gates Talks the AI Future on “Decoder”

theverge.com

Bill Gates:

We may need to develop the taste to actually not use technology to its maximum.

Everyone’s talking about how important “taste” is in making software nowadays.

What about the taste to not make software?

We have had groups — not large groups, but like the Amish — who don’t live at the technology frontier. A lot of humanity may choose not to live at the technological frontier because of things we get from helping each other

Now those are two ideas I can get behind:

  1. Maybe we shouldn’t saturate every aspect of our lives with tech.
  2. Maybe we could learn a thing or two from the Amish.

“Oral Tradition in Software Engineering”

youtube.com

Bryan Cantrill talking about a video he recorded at Google Tech Talks in 2007

If you think I am candid now, you should’ve heard me when the video cameras weren’t rolling, it was something else. When no one could live-tweet what I said, it was more candid.

It is interesting to think about how much technology shapes our conversations with each other.

When everybody can consume everybody else’s conversations, what does that mean for what we say to each other?

(For example, what a speaker says at a conference might be very different if that talk is not recorded, vs. if they know that talk will be recorded, broadcast, and archived on the web for the rest of their lives.)

Oh, and I liked this part too where Bryan talks about why companies should write down what they do:

Record things you don’t otherwise record. In comments (where appropriate), in videos (where appropriate), record these things, not just for future generations but also because it allows a sourcespace to project its values. “Here’s what we’re about.” When people want to come work at Joyent, I have them go watch a couple of videos so they know what they’re getting in to. I tell people, “I have a couple videos […] if you watch them, you will want to work here more or less but you will not want to work here the same.” By doing that, you allow people to opt-in to your traditions and your values. It leads to more success in hiring, you get a more diverse team […] because the values you have transcend the traditional ways you hire people.

You can totally see this ethos being lived at Bryan’s company Oxide, like in their RFDs.

Religious Scholars Met With Anthropic. What They Heard Stunned Them

nytimes.com

Elizabeth Dias:

The company argued that how people treated Claude could affect how Claude treated people.

I think that’s the golden rule, isn’t it?

“Do unto your tools as you would have them do unto you.”

View all notes