Imo, the term “buy” for all goods should pass some sort of litmus test. Eg:

does the product being sold have the same properties as a brick?

• can the product be resold privately?
• can the product be lent to another user temporarily?
• would the product still perform its function when the manufacturer stops supporting it?
• would the product still perform its function if the manufacturer ceased to exist.

if the product does not pass all these tests, the customer is not buying. Consider using terms such as ‘rent’ or ‘lease’ or ‘subscription’

Because that’s the way the legal system works.

“Oops, had some harmful/illegal content on there? Nobody was /really/ hurt, or at least, we weren’t directly causing harm. I’ll take it down and eat a small fine.

Vs

“Oh I’m sorry, I’ll take down the 30s clip of your 90s movie. it has caused you 3million in damages? I’m so sorry, here’s some tools that will automate detection and removal of your property. I’m so sorry”

Is “The Algorithm” just “we stuffed all our GPT responses into a Lucene index and look for 80% matches”?

Because that’s what I’d do.

I used to love ‘the cloud’. Rather, a specific slice of it.

I worked almost exclusively on AppEngine, it was simple. You uploaded a zip of your code to appengine and it ran it at near infinite scale. They gave you a queue, a database, a volatile cache, and some other gizmos. It was so simple you’d struggle to fuck it up really.

It was easy, it was simple, and it worked for my clients who had 10 DAU, and my clients who had 5 million DAU. Costs scaled nearly linearly, and for my hobby projects that had 0 DAU, the costs were comparable.

Then something happened and it slowly became complicated. The rest of the GCP cloud crept in and after spending a term with a client who didn’t use “the cloud” I came back to it and had to relearn nearly everything.

Pretty much all of the companies I’ve worked for could be run on early AppEngine. Nobody has needed anything more than it, and I’m confident the only reason they had more was because tech is like water. You need to put it in a bucket or it goes everywhere.

Give me my AppEngine back. It allowed me to focus on my (or my clients) problems. Not the ones that come with the platform.

Could a hypothetical attacker not just get you to visit a webpage, or an image embedded in another, or even a speculatively loaded URL by your browser. Then from the v6 address of the connection, directly attack that address hoping for a misconfiguration of your router (which is probable, as most of them are in the dumbest ways)

Vs v4, where the attacker just sees either your routers IP address (and then has to hope the router has a vulnerability or a port forward) or increasingly gets the IP address of the CGNAT block which might have another 1000 routers behind it.

Unless you’re aggressively rotating through your v6 address space, you’ve now given advertisers and data brokers a pretty accurate unique identifier of you. A much more prevalent “attack” vector.

If you still do the sizing (it’s not entirely wasted as it’s a reasonably effective tool to gauge understanding across the team), This can still be done without the artificial time boxing.

“How much work have we done in the last two weeks?” Just look at all the stories closed in the last two weeks. Easy.

“When will X be delivered?” Look at X and all its dependencies, add up all the points, and guesstimate the time equivalence.

Kanban isn’t a free for all, you still need structure and some planning. But you take most of that away from the do-ers and let them do what they do best… do.

They were first to market with a decent GPGPU toolkit (CUDA) which built them a pretty sizeable userbase.

Then when competitors caught up, they made it as hard as possible to transition away from their ecosystem.

Like Apple, but worse.

I guess they learned from their Gaming heyday that not controlling the abstraction layer (eg OpenGL, DirectX, etc) means they can’t do lock in.

While suing everyone else that makes shovel handles that work with your shovel heads.

I’m old, I have other shit to do, and I don’t have the time. If I’m writing code, I’m doing it because there is a problem that needs a solution. Either solving someone else’s ‘problems’ for $$$, or an actual problem at home.

If it’s a short term problem like “reorganising some folders” I’m not going to (re)learn another language. I’m going to smash it out in 30mins with whatever will get the job done the quickest, then get back to doing something more important.

If it’s an ongoing problem, I’m going to solve it in the most sustainable way possible. I might fix the problem now but 100% someone’s going to drop support or change an API in 2 years time and it’ll break. Sure, doing it in Chicken would be fun. But the odds are, I won’t remember half the shit I learned 2 years later. It’ll be unmaintainable. A forever grind of learning, fixing, forgetting.

So without a commercial driver to actively invest in Lisps, there’s no point. It’s not profitable and It doesn’t solve any problems other tools can. Without the freedom youth brings, I don’t have the time to do it “for fun”.

I love lisp. Well, scheme and less so clojure. I don’t know why. Is it macros? Is it the simplicity? Or is it just nostalgia from learning it during a time in my life.

But I just can’t find a place for it in my life.

It’s not job material, effectively nobody uses it. It doesn’t solve basic problems with ease like Python does.

And because of this, anything I do in it is nothing more than a toy. As soon as i put it down, I have no hope of picking it up or maintaining it in 6,12,24 months later.

A toy I spend 2 weeks in absolute joy, but as soon as life gets in the way it is dead.

Move to NZ. It’s nearly all c# here.

This is too close to home.

I used to use ANSI, but then moved to England and bought a laptop and returned it because of the “weird” ISO keyboard, then forever bought dell because I could customise it.

Moved back to ANSIland, but will still probably just buy dell.