Tag: API

It’s winter. Here’s some hot IT links to warm you up (What I find interesting in tech, January, 2026 edition)

I haven’t posted on tech in awhile, which I think is a shame, because I like to see these posts myself, if no one else does. Especially I like to come across them years later and think: oh yeah, I was working on that then. Or think: I forgot about that…I need to take that up again.

So here are dozens of good links on IT that I have found interesting over the last year while I’ve been developing software that uses much of the technology you see highlighted below.

As always, almost all of these links are self explanatory. The ones that aren’t…well…few if anyone but me reads these posts anyway. Just treat it like a collection of potentially good resources that I found worthy of sharing.

AWS: I was doing some work on pushing containers into AWS (which I wrote about, here) so I found these useful
Okta/Authentication: before I pushed the containers into AWS, I had to integrate them into Okta. So I did a ton of research on Okta. Here’s some of the links I found useful:
API Dev: my code has a FastAPI interface, so I also had a few issues on that front I had to figure out first:
Milvus: likewise my code interacts with Milvus, which took a moment to master. Ha! Master! I have barely scratched the surface: 
Langchain: Langchain is at the core of my application, so I have been doing lots of studying on this software:
RAG: RAG is another essential part of my application, specifically agentic RAG. Hence these links:
Other good stuff: I’d be remiss if I didn’t keep these links and share them….some of them are especially good.

Finally here’s the obituary for Lou Gerstner. IBM and my place in it was greatly and positively affected by him. I wonder if there would have even been an IBM anymore if Lou did not come along. May he rest in peace. More on his impact on IBM, here.

A return to Twitter (not the service, but the community)

After the frustration with the Twitter service for changes like this, I thought I would give up Twitter. However, Twitter is the sum of a number of parts: there is the service that Twitter provides, from the backend servers to the APIs to the user interfaces and client software you use;  and then there are the people that contribute to Twitter. Among those contributors are people I really enjoy socializing with whom I cannot connect with any other way. To give up all of Twitter means tossing out the baby, the bathwater and even the tub itself. That’s dumb. (I do dumb things often, but typically correct most of them in time. :))

To get around that, I decided to use my limited software skills and the APIs that Twitter provides to write my own Twitter client, in a way. It is a hack, but it is a good hack (for me). I am able to control what I see this way. Not only do I not have promoted tweets, etc., in my feed, but I am able to get rid of things like RTs from everyone, rather than having to turn of RTs one at a time. I’m also able to save all the tweets in a spreadsheet or some other format, so I can look at them when I am less busy, or decide on other filters I want to apply, etc. Later on I can write more filters so if a trending topic gets to be too much, I can just delete it or save it to a different file for later.

Now my Twitter experience is gone from poor to great (for me).  I have thrown out the dirty bath water, but kept the tub and the baby. This makes more sense, obviously.

Last but not least, I appreciate all the people who expressed concern over my leaving Twitter. It was very kind of you, and why I want to stick around, if I can.