This is interesting. I wrote a “memory indexer” with the idea to provide a tool (cli) for my agent to “remember” past conversations we had in other session. A little bit in the spirit of your second tool I think

I’ll take a look at the others you have.

The thought behind my aichat tool was to directly leverage the session log files and avoid creating any special memory artifacts. I do create a rust/tantivy index for the fast full text search.

The aichat approach does require intentionally asking the agent to find specific earlier work: it doesn’t automatically have “awareness” of prior work. I think of this as the “unknown unknowns” problem. This is where creating explicit memory artifacts can be useful since we can pre-inject recent work-summaries into context. So I’m thinking about a lightweight hook based system to automatically create memory artifacts or work-logs of some sort.

Water used to be managed by a local cool here where I live. I had been for decades.

A few months ago i got an email saying that PE had acquired it.

I was paying between ~$25/month before. Today i got the first bill from new management for $89.

Same volume/usage, nothing significantly different.

Sigh.

Definitely complain to you local water/utility regulator, and your state representative.

Regional regulators have to approve the transfer of ownership of water utilities. The best time to fight this sort of thing is as early as possible.

I had no idea about any of this. I’ll talk with my neighbors and see if there’s anything we could do

Maybe folks where still confused by memories of the Australian breakdancer from last summer olympics (?)

This was excellent comedy, and I never say that, kudos

I got a pair of Santoni’s leahther sneakers in 2017, for about $500. I still have them and while they worn out a bit, they are still nice.

The most comfortable shoes I’ve ever owned. I remember describing them like “walking in clouds”.

Never bought any of them and all the other pairs I got from different brands in the $200-$400 bracket have been awfully disappointing

This is in my mind the hardest part as well.

I can solve the cube with the regular “easy” 3-layer approach, but I’d like to solve it faster.

The issue is that the techniques for fast solving require to learn many different patterns to get to the right solution fast.

I don’t know really how ppl that solve it fast accomplish getting to that level, but to me it would be amazing if i could just set the cube in know scrambled states that let me practice and memorize specific algorithms repeatedly until I learn them.

The problem is that I don’t know enough yet to distinguish which are those initial states, let alone setting the cube in that state, so something that could set it up for me to practice would be amazing

> I don’t know really how ppl that solve it fast accomplish getting to that level

Just like everything else in life, they do it really slow and with lots and lots and lots of errors at first, but (and this is where the magic happens) keep doing it, training hours a day or their entire week ends, for years.

Where are you located at?

Maybe this may help. What if we are not talking internal development teams but something different, like a commercial/public API?

In those cases you cannot affort or expect to have meetings with folks to explian and communicate, and you also can appreciate more the abuse (unintended or not) that tokens can have.

I particularly liked that OP mentioned about expiration, key rotation and more advanced features you can achieve with his proposal, like switching schemes

Agreed: if the situation were completely and totally different to the one described by OP, then yes, different circumstances apply.

I’ve been hiring interns and managing internships for the past 10+ years.

The number of interns at any given time varies from 1 to 10+

We were a small team at some point (less than 10) and now the company is bigger (~500 engineers).

We hire most interns if they have a successful internship and are interested in working with us.

I really love working with young engineers, mentoring them and helping them shape their careers.

I don’t have any specific resources to pint you to, but typically what I do is to have a bunch of well defined/specified projects, that can take anywhere from 2 to 4 months to complete.

Projects vary so I can accommodate to their interest if they have anything specific in mind:

- testing

- api development

- frontend

- systems programming

- etc

If I’m the mentor of an group of interns, I make sure I meet with them on a daily basis. I will also meet with them 1:1 and provide prompt and actionable feedbak on how they can improve.

I can say that we at my company are really satisfied with the results we’ve yielded during the past 10+ years, and the talent we have been able to recruit and groom through that program.

Back in the day when I started coding in Go, I basically did the Go Tour on the official website, and watched some of videos.

I paid close attention to learning how to write idiomatic Go. I also read a bunch of code from the std lib.

Then after a few days I jumped right into coding. I started with a simple CLI to do some heave lifting in our Ci/CD pipelines (for work) and then I also started coding some web apps for my perdonal use.

After this, I started designing and building a few systems that were needed internally at my workplace and I also started training other folks in Go.

That was back in 2017. Today we have several big systems running in production and a strong team of engineers all working and enjoying Go :)

I would recommend to anyone a similar path:

- learn the basics

- build and release things

- teach others who may be interested

At that time my background was as software engineer (~17 years) mainly writing Java and some Javascript

A few years ago we started using HackerRank and created a test with 4 or 5 coding questions for candidates to do on their own. They could pick the programming language from about 10 options and the questions had varying degrees of complexity, with one being particularly difficult.

I sent it to almost all engineers on the team before we started using it and none could hit a 100% on it.

We still went ahead and started using it in our process. Non surprisingly, most folks would fail to get a perfect score but we still use it to see what they tried and also one of the following interviews was a review of the whole test with the applicant as we discussed their thought process and what other odeas they may have come with since they took the test.

Our intention with the test was mostly basic problem solving skills and was the first step in the process so it also worked as a filter.