The trick to this is to attach a handle to the back of it. I'm using one that telescopes from the "popsockets" brand (I'm unaffiliated and have no idea how it compares with other brands). It makes it possible for me to access all parts of my screen holding it one handed. It should be a standard feature.
I want a handle on the back of my phone even less than I want a larger phone. I also refuse to use cases and any other contraption that adds further bulk.
I have had an excellent experience with the OhSnap grip. https://ohsnap.com/products/snap-grip It is significantly smaller than the popsocket and adds a strong magnet which can attach your phone to magnetic surfaces. It looks flimsy, but I've had it two years and even moved phones and it shows no signs of breaking.
Are there any guidelines for what exactly this would entail?
My short term memory is falling off a cliff. What do I need to do to prevent that from getting worse? Are there any other bases I need to cover that I don't know that I'm missing?
Are you sure? I thought this was happening to me too, and then I realized when looking back 10 years ago that I have way more responsibilities now both in and out of work: I am not only getting more done at work, but also for more people. I am now picking and choosing which meetings to even hold, much less attend, because I have a higher throughput. My children's needs are much more complicated now than when they were younger. I have a side business.
I can't fathom how I would have even gotten this all done when I was younger simply due to how much leisure time I spent, much less kept all of this in short term memory back then.
> I thought this was happening to me too, and then I realized when looking back 10 years ago that I have way more responsibilities now both in and out of work
This so much. When I was in my 20s I never forgot things, but I didn't have anything that I really needed to remember lol.
It's easy to forget about how many more responsibilities we take on as we age, simply by nature of how those responsibilities slip into our lives one at a time, bit by bit, gradually shifting our window of normalcy.
My phone is now full of Notes, Alarms, and timers. I can barely leave the house to run an errand without writing down what I need to do.
As far as actually improving memory, I try to expose my mind to as much raw material as I can. The mind is a muscle, it has to be exercised, and as you get old you need to focus on its core strength rather than physique and raw strength.
Rehearsal and repetition. Read constantly, get out in the environment and really try to observe all the things that are going on. Write down all the things you want to do this year, and when you’ve done them, write that down, too. Every so often, review the list. It will prompt your recall to a wonderful degree.
Write down your little milestones - ‘in March we found a clutch of tadpoles in a tire track puddle and we watered and fed them there for six weeks”
Regarding memory, I have made a habit of assuming I have a faulty memory, and trying to write down anything I think I may want to remember in the future using a wiki style tool that supports back linking. The tool I use is Org Roam in Emacs, but there are lots of options. I have found that by doing this, I have offloaded a lot onto my computer, and made space in my mind to remember a lot of new things.
Contrary to the other comments saying to carry a pocket computer: my brain. Hence the improved memory. I offload my thoughts into my notes when I can. If it wasn't important enough to remember until I can find a seat at my desk, it wasn't important enough to write a note on.
You are not supposed to store things in the brain, that only causes stress.
Brain is to do thinking work, you are better off writing and tracking things on paper. Use the brain to think, and paper for planning, scheduling, tracking etc..
The only 'exercise' I've heard of that offers measurable improvement is "N-Back", kind of like the old TV game "Concentration". The app is available on most smartphones.
Avoid weed if you don't already. Might seem out of left field but a programmer friend of mine is absolutely convinced their memory is shot because of long covid and it's like, well, maybe, and the trauma of the pandemic certainly put a dent in everyone's cognitive ability, but also the dabs can't be helping.
I was in the same boat, but I started noticing that if I force myself not to do silly multitasking (like not paying attention to what I am doing because my mind is thinking about irrelevant other things) it gets better. Since I stopped the infinity doom-scrolling it has improved a bit
Stress and lack of sleep also affect me a lot. Both are omnipresent, since I am a parent of young-age special-need kids.
Both of my grandfathers in their 90s have insanely sharp memories. I feel that theirs is a lot better than mine at instantly recalling details. I have noticed this in other older people from that generation too.
Emotions can have a large impact on memory, as far as I know. They provide the catalyst, in a way, in the process that forms memories. If you are depressed or otherwise not emotionally engaged, it can become much harder to form memories.
Solve emotional problems and memory may improve. (I have no idea if that applies to you, of course.)
> short term memory
Which sort of memory do you mean? Short term memory is remembering a name while you write it down, not remembering it the next day or week.
You can premove as many moves as you want in a lichess correspondence game. I feel like you can even premove to whatever depth you want, but it has been a while since I've played.
You wanted a Map<String, String>, and that's exactly what you should have made. A String is a convenience wrapper for storing a &str on the heap, so storing a String on the heap is redundant. The other options are for performance concerns, which you haven't mentioned any.
Now make it a global thread safe hash map where the keys are references into a mutable memory map that can move it's address (be remapped.) That's currently where rust is making my life miserable today. In C++ this is quite straightforward, albiet full of footguns.
Every time I need a static mutable thread safe map in rust for a cache or registry or some such thing, I groan.
I have a love hate relationship with rust. I love a lot of things about it, but sometimes I get so fed up with the borrow checker I drop into unsafe and just write the problem off as something better not done safely.
Maybe I am misunderstanding your needs, but could you not just use a RwLock[0]? For being global you will need to use the lazy_static[1] crate. Admittedly, I have not tried doing this directly though.
I'm using 'static references for the map keys, but they're not really 'static, so I use unsafe transmute to create them and I rebuild the map when the memory map changes to a different address.
Lisp always sounds cool to me until someone starts talking about macros. What's it like inheriting a lisp code base, finding out its full of homemade macros like list comprehensions, and that they're not documented? Inheriting a code base is always scary, but I feel like it kicks it up a notch when your predecessors can customize the language itself. Are my fears justified?
> What's it like inheriting a lisp code base, finding out its full of homemade macros like list comprehensions, and that they're not documented?
If such a macro is used in more than two places, it's generally a relief that the author did that instead of doing copy and paste by hand.
The author had some coding idea, and formalized it into a little robot that writes that idea, which has a name.
Even if that thing isn't accompanied by documentation, it can serve as a kind of documentation to what it's doing.
Code is going to be full of homemade functions that are not documented; whether they are functions that write code at compile time, or whether they are run-time functions, is kind of a minor concern.
Macros look the same as functions in lisp, the only difference is that you can't pass them as function arguments. Unless there is a bug in the macro you just spend the same time understanding the macro that you would understanding a function.
Most macros are just simple syntactic abstractions that expands simple code to more lines of relatively simple code to avoid boilerplate. Very rarely do people write complex beasts without documentation.
You do realize that "vast selection of easy-to-use libraries" is the most important feature of a programming language. Right? It's up there with, "it's not hard to hire programmers for the language", which Python also benefits from.
Like, I'm partial to Haskell, but if I'm actually trying to get work done, I reach for a language with a robust ecosystem. These days I reach for Typescript, but before then, python was my go-to since it's way nicer to program with than java/c++/c/javascript.
>You do realize that "vast selection of easy-to-use libraries" is the most important feature of a programming language.
No, it's not. When I switched from Python to OCaml it felt like blessing, since the quality of the libraries felt much higher in OCaml. There are also the projects that you have to build from the ground up without libraries (any mission critical software), and in such cases you don't care about libraries at all, you care about the merits of the language solely.
Python is the BASIC of the XXI century, and it's fine in that role, but not as a general purpose language.
Personally, I would love to ditch python for a language with strong types and type inference, but what is the replacement for django? Where do I find a well-designed, well-documented, battle-tested framework that I can easily hire developers for?
Currently, I think the nearest competitor is node with typescript, and I'd rather stick with python. Please tell me if I'm wrong.
Haskell's Yesod framework is pretty feature competitive with rails/django, but it doesn't have 1/10th of the community.
I'd love to see Haskell gain wide popularity, but I don't think it's realistically going to happen. People generally travel the path of least resistance, and learning Haskell requires a lot of time and effort before you can be competitively productive with it. Individuals will choose to make that investment, but the masses won't unless they are forced.
I think the closest thing to what we want right now is node with typescript.
The idea is that it acts as an irritant which increases blood flow and other healing responses to that area. Tendons in particular are thought to heal slowly because they don't have great blood flow. This strikes me as similar to the ideas of dry-needling and platelet-rich plasma injections.
