I like vi/vim, but it gets me all too frequently because I'm not precise enough of a typist. I'm busy typing away and I hit the wrong modifier key or hitting caps lock and I end up pulling things up or making changes that I never intended to make. Worse, in the split second after it happens and my muscle memory tries to correct it my immediate intuition of what mode I was in is wrong or which modifier key I'm pressing or caps lock is on and I only make the situation worse. Any improvements in performance because of the quick key interface are long gone.

It's very common to disable caps lock or rebind it to something else (e.g. Esc for even more ergonomics)

This could probably be solved with a better keyboard

I wonder if this will be true because we're interested in software for humans and the AIs are not as good at understanding humans. The recent news that AIs select for their own resumes over the resumes of humans and other AIs makes me wonder if the AIs will be good at producing software for their own "needs", but not for humans whom they don't "understand" as well.

Interesting, I've been using Flet for my projects lately, and I've been very happy for desktop environments. Never tried it on web and phone platforms, but Flet has similar run-everywhere marketing which originally drew me in. Anyone know how PyWry differs from Flet?

Ditto. My kids are still pretty young, and my old Construx are one of the favorite building toys.

Over planning and scope creep are a problem, but let's not swing the pendulum to far the other way. Some of my most successful projects were projects where I planned out and worked through most of the features ahead of time through the process of modeling my data without any working software to try out. When I'm in that phase, I often don't really know what is too much. If I leave out features I think I or the users will probably want, I spend a lot of time with significant redesign of core aspects of the code. If I'm wrong, the project gets too big and we chalk it up to scope creep.

My ability to get this right is often a matter of how well I know the domain. If I don't know the domain as well I think I do, I fall into a lot of rework. If I know the domain more than I imagine then I waste my time with a baby step process when I could have run. All of this is a big judgement call, and I have "regrets" in both directions.

I think the ideal solution is to spend a lot of time in the analysis phase to load your brain up with the correct context, but then be ready to throw out the overengineered solution and just build what feels right.

Don't fall prey to sunk cost fallacy. Just because you spent hours researching a PhD level topic doesn't mean you now have to use it in your project, if it's not quite the right application.

You worry too much about being wrong. Just try something and adjust as needed.

For some reason this reminds me of people at work who walk up and say we did x bazillion things in n time, and then pause and expect us to express shock at how amazing that is and how much more productive they are than other teams. So what. Without a proper comparison to something equivalent I can't evaluate whether it's exceptional. I could treat each molecule as a thing and tell people how incredibly many things I eat on average per minute, but if I explain no one would find this to be exceptional.

"Rice is great if you're really hungry and want to eat two thousand of something" - Mitch Hedberg

Also, if you have huge amounts of fresh water and a tropical climate... you can get three harvests per year. Unlike most staple crops.

50 story points!!!

The only thing that matters

I think this demonstrates that while there are many factors at play, including difference in geography as many have pointed out, the main factor is priority. American's generally have different priorities, sometimes that just prioritizing our personal comfort by not having to fight against the current "system". So, even if we would love to have better internet, other things are more important. I'm one of those people. My cellular based rural internet would be considered poor by most people on Hacker News, but it's good enough for us. I have no motivation to pay for faster. I only rarely download large file and have always been willing to let them download in the background and come back hours later. If I'm going to campaign for something I currently have far bigger priorities.

I decided to operate on a older budget phone for a while when my phone died outside of my planned budget and timeline for replacing it. By far the greatest problem was managing storage space. Except for core productivity apps, if a website option wasn't offered I was never going to be one of their users.

The solution is sufficiently perfected with markdown. Just like new revolutionary technologies doesn't replace wheel technology.

To actually manage notes and information in plain text I like org-mode markup. For just writing, markdown is good enough.

In many ways this looks fun. I love the precise control and programming power of tools like this, but when I need something in real life, I never use them any more. The productivity of graphical tools is so much greater (as far as my brain works).

When I was younger I used POVray for a few small projects, but once I had access to graphical interfaces the difference in output quantity and quality was huge. I still keep tools like POVray installed, but all I ever do with them is tinker once in a while.

I remember running across POVray in the early 90's and not having a clue how to do anything more complex than a sphere with a light source.

Some artists have done some truly magical things with it: https://hof.povray.org

Oh my, thank you so much for bring back the POVray memories!