phone: * that circle in whatsapp * find a freebie chatgpt proxy in telegram
web * "copilot" in ms Edge browser * https://kagi.com/fastgpt * https://grok.com/ * https://claude.ai
I find the need for a "search engine" reduced very considerably with all these "answer this question (NOW!)" options so readily available. They're the modern day "I feel lucky" button.
One thing that I do is that I keep writing code in my favorite languages Common Lisp, Haskell, Racket, and Python (Python only for deep learning). I also still write.
I envisage myself coding for another 45 years (I'm in my 50s now), but I worry about my ability to concentrate on a single task for long spells, think creatively yet realistically enough to find solutions; to learn the latest fads and tools, and maintain my enthusiasm to keep up with the latest fads and tools. Will my hands get too unsteady to type, my eyes too weak to focus; how long will I be able to sit (or stand) up and work in a session. No-one knows I'm a dog, but they will if I have to turn on the camera or go to the office, so, will I necessarily be transitioned to more results-driven work assignments via tasking sites?
(I guess these are the typical prejudices that a hiring team will make when considering an older candidate.)
Prepare me. Share your wisdom. What challenges has aging presented to your ability to code?
Mine likes the pretty graphs. As I enthusiastically explain them, the eyes start flickering elsewhere, attention rapidly dwindles, and trust is effectively reassured for another month, or six.
I was excited that this was an extension of markdown but now I that see it I react with horror: markdown is not a programming language. This looks rather like a programming language.
An individual who has "mastered the material" can answer quickly irrespective of their smarts: they learnt both the fundamental concepts and the derivatives in preparation for the test, and can commence answering the question immediately from the derivatives.
An individual who has not "mastered the material", but is smart, can start with the fundamentals, work out the derivatives, then commence answering the question: but only given enough time.
So tests which include a time element are, or should be, knowledge tests, and not an intelligence, or 'ability to answer the question', test.
My thoughts on going down to one-symbol-per-chord:
- Due to the small steno layout, you don't need to stretch your hands to far symbols on the keyboard. - You're not limited to what's on the keyboard. Symbols like ÷ and © and any emoji are now first-class citizens. - There are cases where you get multiple symbols per chord. For example, calling a function `()` is one chord. Writing an arrow like `=>` is also one chord.
Overall, I'd say that coding speed doesn't really change as typing fast is not what makes coding fast.
There are some real advantages that I find difficult to quantify, though. I switch between stenography and typing for both coding and writing depending on whether I'm at my desk and I find it hard to express clearly why coding in stenography feels natural and nice. I suppose: there's a certain fluidity when you break things down into semantic words rather than simply symbols.
Hope that helps!
When coding I seem to expend most of my keystrokes just moving around the page. I take it you just setup some short chords for each arrow key, pgup/pgdn, ctrl, alt... etc.
It is hard enough getting around a desktop with just keyboard shortcuts as it is!? I expect I would waste an inordinate amount of time fiddling with my dictionary trying to optimize keystrokes for the OS and apps that I spend the most time in.
The first column of numbers is the input scaled to a real number between 0.0 and 1.0
Not sure what the color of the flags mean, if anything. Not sure what the middle column of 4 numbers are or how/why they change. Still not sure what "power change" actually is.