aurumque

I suppose I am just happy that these things are being talked about more. I can't visualize anything, feel a memory, re-experience the past, or even remember much at all about my own life. A day after arriving home from a trip I can't even be sure I went anywhere unless I check my calendar and my inbox for details about flights and hotels. It is very distancing and alienating, and friends often seem to think you are just too caught up in your own world to remember they exist, when really it's just the opposite and you aren't even sure that you exist.

Much like the 'discovery' of aphantasia has dramatically changed the narrative of subjective experience, I hope that further inquiry into SDAM/HDAM will help others understand, in time, that some of us exist entirely outside of time and place but are doing our best. And for those who experience the world this way as well, the message should be that happiness is achievable, but certainly looks and feels differently for some, and even moreso for those who live their lives at the edges of the bell curve.

I enjoyed this read, the energy, and the detailed positive outlook. However, what am I supposed to take away from "5 weeks / 35 people / no new recurring friends"? Every time I go out I feel this personally, and I never understood why so many people have such thick shells to crack.

Similarly, I made an agent that lets Claude puppet OpenSCAD, generate screen shots, change the camera angle, etc. In general Claude seems to have a pretty good vision model that can create usable designs. It's also fun to let it make up new models of its own and then try to 3D print them.

I would think that building a environment which can be managed by a game engine is the first pass. In a few years when we are able to render more than 60 seconds it could very well replace the game engine entirely by just rendering everything in realtime based on user interactions. The final phase is just prompts which turn directly into interactive games, maybe even multiplayer. When I see the progress we've made on things like DOOM, where it can infer the proper rendering of actions like firing weapons and even updating scores on hits and such it doesn't feel like we're very far off, a few years at most. For a game studio that could mean cutting out almost everything between keyboard and display, but for now just replacing the asset pipeline is huge.

S3 also gives you multipart parallel uploads. Each part gets stored and then when you're done the concatenation is performed close to the storage layer.

Did you know that software specifications used to be almost entirely flow charts? There is something to be said for that and waterfall.

Golang is one of the only languages with a more or less working library. I built with it and using some hacks got it hooked up to AWS API Gateway with Lambda. Reading the room, the lack of language support does make it pretty suspect in 2026, even if the client support is still pretty good. Recently I have abandoned in favor of AWS Mountpoint (rust S3 mounting) and combined with Lambda object get and list functions have achieved most of the same functionality. The downside being that you lose the ability to talk to the many varied clients like an old HP printer which (obviously) can't use FUSE.

In a circuitous way, you can rather successfully have one agent write a specification and another one execute the code changes. Claude code has a planning mode that lets you work with the model to create a robust specification that can then be executed, asking the sort of leading questions for which it already seems to know it could make an incorrect assumption. I say 'agent' but I'm really just talking about separate model contexts, nothing fancy.

I wonder if it could still be usurped by another standard that is somehow more popular. If adoption of that leapfrogs over IPV6 then maybe it will have just been a waypoint along the way.

This kind of writing goes deeper than LLM's, and reflects a decline in both reading ability, patience, and attention. Without passing judgement, there are just more people now who benefit from repetition and summarization embedded directly in the article. The reader isn't 'stupid', just burdened.

Having been affected by this personally, I don't think Marriott cares about their brand at this point as they have achieved relative monopoly status. There are plenty of other horrible things they've accomplished in the last few years besides this. It makes me want to watch out for CitizenM similarly, because it's increasingly unclear what Marriott's actual role in your stay even is anymore.

This holiday season, consider giving the gift of a well-researched gift list, and then letting them decide if they want to buy it or not. Most people don't want more stuff, they just want to know you understand them and care about them.

There is a related set of experiences that articles like this tend to conflate.

* presence of internal monologue

* ability for visualization

* ability for audiation

* affective memory (remembering feelings)

* SDAM (weak autobiographical memory)

It speaks to the larger questions around the human experience, and that we are only now discovering the many ways it differs for each individual.

Azure goes down all the time. On Friday we had an entire regional service down all day. Two weeks ago same thing different region. You only hear about it when it's something everyone uses like the portal, because in general nobody uses Azure unless they're held hostage.

For those of us who have been using AWS for almost 20 years now, I can't imagine why anyone would willingly choose us-east-1 for anything. It is the oldest, highest traffic, most critical path region and is subject to turbulence.

Right. Try building thousands of transistors without rigorous EDA and basic checking in VHDL. This article is such a bad take.

This has always been my takeaway with Go. An imperfect language for imperfect developers, chosen for organizations (not people) to ensure a baseline usefulness of their engineers from junior to senior. Do I like it? No. Would I ever choose it willingly? No. But when the options at the time were Javascript or untyped Python, it may have seemed like a more attractive option. Python was also dealing with a nasty 2-to-3 upgrade at the time that looks foolish in comparison to Golang's automatic formatting and upgrade mechanisms.

I congratulate you. This is a clever extension of a great framework.

Let's not forget just how much of Alan Turing's work went towards "defense of the state" before they discarded him. Even with the royal pardon, my biggest gripe is that they continue to use his name and likeness for anything government affiliated.

And yet when I recommend that replacing senior leadership is one of highest ROI potentials for AI they immediately shut down the conversation.

This is a really great experiment that gets a lot of things right!

The fact that Mixxx works as well as it does on Linux is a testament to human ingenuity and perseverance. It is truly The People's mixing deck.

When I was a younger man, I fought long and hard and spent many late nights on the phone with the lawyers abroad, to convince my company to open source a tool that I was proud of and thought would help our brand and attract new developers. They finally granted approval, but I was not allowed to accept features or updates, customer service, spend time on fixes, accept pull requests, etc. Unfortunately my name was all over it, and I came to hate the fact that I had championed this, forced to watch the code rot and interest wane because the company couldn't fathom anything OSS besides lobbing some dead code over the wall periodically.

After I left I would still receive emails from frustrated users, but I had no access anymore. I could have forked it, but it just seemed too messy. I made some suggestions and wished them luck.

There is a lesson here, somewhere, but mainly it just convinced me to not rock the boat for the next decade, and to seek out smaller companies for employment.

I'll take the shameless plug. Thank you for putting this together! Very helpful overview of pg locks.

Access modifiers don't give you unlimited protection, they help you reason about the code and how it is used. If I change a public method and break something downstream, that's on me and my team. If I change a private method and break someone else's code which was bypassing using reflection or other mechanisms, that's on them.

Languages like Python don't have keywords but enforce using conventions like underscore and 'dunder', the latter of which is actually enforced using obfuscation. It is extremely helpful to signal to users that they should not be using certain methods or fields. When there are no access modifiers available, we still see teams writing methods like "xyx_UNSAFE" or "abc_DO_NOT_USE". It's ridiculous to me to encode this kind of information like this instead of having first class support in the language.

Access modifiers also tell the compiler or JIT what is safe or unsafe to manipulate. It has implications beyond users, and can be a determining factor when inlining or making other optimizations.

This article is so opinionated (edgy?) that it ends with "Inheritance was a hack in the first place." I think, like all things, we need to consider the broader landscape for object oriented programming instead of just saying these things are irrelevant and absurd and useless.

Why not make this contribute to something greater, like scientific grid computing, or a charitable bitcoin donation? Instead we're just burning a few watts to slow down crawlers.

Having been through a few acquisitions myself, I think there is a perverse incentive where buying and destroying any competition (real or imagined) leads to positive enough outcomes that it doesn't matter if the underlying asset is destroyed. Nobody would come out and say that, but when an acquisition is tossed aside there may not be enough repercussions to prevent it from happening again.

My whole life has been a lie... And yes I do have a drawer with several of these alongside VGA adapters and anything else I might need during the end times.

1. it makes tool discovery and use happen elsewhere so programs become more portable

2. it standardizes the method so every LLM doesn't need to do it differently

3. it creates a space for further shared development beyond tool use and discovery

4. it begins to open up hosted tool usage across LLMs for publicly hosted tools

5. for better or worse, it continues to drive the opinion that 'everything is a tool' so that even more functionality like memory and web searching can be developed across different LLMs

6. it offers a standard way to set up persistent connections to things like databases instead of handling them ad-hoc inside of each LLM or library

If you are looking for anything more, you won't find it. This just standardizes the existing tool use / function calling concept while adding minimal overhead. People shouldn't be booing this so much, but nor should they be dramatically cheering it.

Watching QuickBooks increase in price while decreasing in quality year by year, I keep wondering when the market will finally start to break. I hope this is your break, good luck! I think "QuickBooks, without the popup ads" is already a good enough pitch to me.