Friday, October 16, 2026
PRACTICE MAKES PERFECT
Monday, October 12, 2026
THE BOTTOM OF THE MOUNTAIN
“Because it’s there,” George Mallory’s famous reply when asked why he wanted to climb Mt. Everest.
Every task is viewed from the perspective of the bottom of the mountain. A letter you must write, a performance appraisal for employees, that tax filing you must do. Getting to the start line of that marathon run.
Life is bottom of the mountain stuff.
Wood Allen also famously said “90% of life is showing up.” The problem is getting to the start line, opening the blank document, and writing the first words, getting dressed and making your way to the bottom of the mountain. If life teaches us anything, getting to the start line is 90% of the problem solved.
And most of us never make it there. Mostly out of anxiety of overthinking the target. So focussed on the goal, the end point, and trying extremely hard to work backwards to the start, that we never make it to the start. We do not move from where we are because the discomfort of not knowing how we will move forward will work will play out causes inertia.
ALWAYS SOMETHING BETTER I COULD BE DOING
That’s the other problem. When faced with something you should be doing, we think of more interesting things that we could be doing. Like listening to music. Or watching a movie. Or riding my motorcycle.
It is procrastination but not readily recognizable so. The word better could be replaced with rather, more interesting. When George Mallory replied I’m sure he didn’t stop to wonder why he was actually doing it. Come up with a reason that would satisfy his audience. Come up with a reason that would satisfy himself. The consensus reason. Have a purpose for why I do what I do.
That thing that you should be doing only seems daunting (as Mt. Everest would be to anyone) only because you’re thinking of the plus 12,000 feet to get to the top. Of the sheer climbs, the rope work, the treacherous cold and possibly the statistical possibility of failure proven by many who have not made it to the top.
THE FIRST STEP
Nobody can really see what’s in your mind and as you’re working on something, your critics are bound to ask you many questions as you’re working on something. And sometimes, you don’t even know until you’re somewhere in the middle. Like, “where are you going?” and you say, “I don’t know, just going for a walk.” You’ll figure it out while you’re out there. Some things don’t need too much planning. Too much planning gets in the way of making that first step. Just put on your shoes, grab your keys and step out of the door. Then orient yourself in a direction and move. It’s that simple.
But there are some projects that may take a while longer. Like a longer road trip. Decisions on which route to take. Whether or not you have enough fuel in the car. When to leave and when to return. Or if you’re making a cabinet. Or writing a book. Or an essay. Or doing some gardening. Those may need a little bit more preprocessing, but too much thinking may stall that first step. And for many of those things, even the ones I’ve mentioned, a rough plan is the best plan. Because there’s no such thing as a perfect plan. And in all of those tasks, the result is known, only the path is not fully planned.
FINALLY… ANALYSIS PARALYSIS
The biggest obstacle I find, personally, that fuels the inertia at the start line is not having enough knowledge, not knowing enough, to see the task through. And being afraid of messing up just to start over again. So I research and research until I believe I’ve covered ALL the bases. Thought of all the obstacles. Planned each step and are confident that I’ve thought of all the possible scenarios and mitigated all potential for failure.
Hah!
That process never ends. It ensures that I remain at the bottom of the mountain, looking up at the sheer climb, never seeing the peak and wondering how far up it is and whether I’m standing at the right place for this climb. The overthinking says, don’t even open the computer and start writing because you may need to delete everything you’ve written and start all over again. Don’t go to the start line of the marathon, you may not have covered every aspect of the training and you may not be completely fit enough for this. Don’t write that letter, you don’t have all the facts to present to the group or all the answers.
The truth of the matter is that you never will. And that there’s never a perfect time. And the best that you can do is just take that step, and deal with the lack of knowledge as it comes.
Thursday, October 08, 2026
QUIET - THE SILENCE BETWEEN THOUGHT
ALWAYS ON - ALWAYS AVAILABLE
PRACTICE SILENCE
MEDITATION
Wednesday, October 07, 2026
DIGITAL DETOX
DETOXING
DISTRACTION
Tuesday, October 06, 2026
To Think, To Write
I was online thinking about why writing on the computer is so tiring, but writing on my notebook, on paper, with a pen, felt tip, isn't tiring. I can just keep rambling on and on without stopping.
And I've written a lot of words in my handwritten notes.
But I've also typed a lot. Much of that stuff remains in anonymity.
So I decided to find out how most authors write the stuff that they write and here are a few reasons.
Handwriting,
- Allows them to think SLOWLY.
- Forces them to be ACCURATE the first time around (no delete, spellcheck or backspace).
- Keeps them moving FORWARD.
- Rarely stop, because the mind is constantly, always AHEAD of the pen.
- Gives them permission to PAUSE and reflect since the PEN isn't as demanding as a blinking CURSOR.
- Because most people say that they have horrible HANDWRITING.
- Because writing by hand is TIRING.
- Because they type FASTER than they can write so the words can keep up with the thinking.
- Allows them to do some minor changes and corrections as they go along, deleting and backspacing and also re-reading.
- PAUSE frequently to allow the fingers to rest, so they re-read frequently.
- The editing process does not require re-writing.
Thursday, October 01, 2026
THE CHALLENG OF CODE - AI PERSPECTIVES
Google's search is way better today, with it's AI Mode, than it was years ago. It's grown. You can now have an intelligent conversation about what you're working on and most of the time, more than 75% of the time, get solid answers.
Especially if you're a programmer. Need to figure out how to write a function to grab some data from wherever and display it in a table. 5 seconds. How about adding user interactivity to that table. Maybe 10 seconds more. Hey, forgot a security wrapper, maybe a minute to fix this.
The need to have a full technology department with developers, testers, packagers, cyber experts with all the associated management is taking a 180-degree turn.
Of course you need to know what you want. You need to ask the right questions.
And you also need to know if the answer you got is the right answer.
So there's still a ton of homework to be done.
But the stressful work of trial-and-error, research and gradual knowledge building is becoming less painful. It hasn't gone away, it's just easier to have someone, something, tell you what you should be thinking about.
COMFORTABLE BEING UNCOMFORTABLE
I used to teach computer programming - not computer science. Teach students a programming language and how to solve mainly business related problems using a specific programming language. Automate the hard stuff.
And I'd tell my students that this world of programming is constantly changing. I'd tell them that you need to get used to being comfortable being uncomfortable. For as soon as you've mastered something, it's scheduled for obsolescence. And that a life as a software developer is a life of constantly trying to keep your skills current.
20 years isn't a really long time in a career, but it's a good enough span to say that you've matured in that area.
And 20 years ago, there was no AI to speak of. It wasn't in the horizon, at least for those of us writing desktop applications for Microsoft Windows, or server API's on Linux. After a while, you knew enough of the business logic and the actual coding sometimes became quite tedious.
For myself, mastery of a skill was quite disappointing, even though the work prior to mastery, the constant bouts of failure, were frustrating, finally getting it felt like being at the top of a mountain, and there was nowhere else to go but down.
But soon enough, another hill presents itself and another climb awaits.
THE LOVE OF CODE vs AI
If you're like me, it is not always about the goal, but the journey can be interesting. The well-trodden path can be delightful but you may also have great experiences when you go off-road and challenge yourself.
It took me a long time in my software developer career to discover that there really isn't a "best" way to write something, but there are "better" ways of getting things done. Much of the time I wasted researching, even when I had a solution that worked, is that I kept thinking that my solution is not good enough. I remember learning C++ and thinking that from this point on, I will do absolutely everything in an object-oriented way. I still don't know if that was a good or wrong thing to do. Computers were getting so fast, that for the problems I was solving, it wasn't a performance decision, more likely a complexity one.
And later in my career, my decision, and fortunately it was mine to make and not my employer's, to learn and focus on Python had more to do with the readability and simplicity of the language. No curly braces, yay! No semi-colon's double-yay! But now dealing with tabs-to-spaces ugh! Does anyone use tabs? Weren't they invented for the typewriter? Why are they still on the keyboard?
Anyhoo, writing software can be an intellectually satisfying, cerebral activity. Part problem solving. Part engineering. Part construction. And it's not always about the result. Behind a pretty interface can be some nasty stuff hanging together by the skin of its teeth, just waiting for a breeze to completely fall apart, like a set of Jenga blocks. You don't want to be the programmer who says, "I don't know what I did, but, hey, it's working!"
KNOWING IS EVERYTHING!
I spend a quite a bit of time, for my business, and also for fun, writing code in Python, using the Flask framework as well as Bootstrap. I like working with Sqlite databases. Sqlite does everything I need for the small tools stitched together to make my business semi-automated. We're mostly paperless (or paper-free) and I've always felt that its time well spent automating a very repetitive task, rather than simply slogging through it because the manual process isn't that difficult.
Like who wants to type up employee payslips each month. Even if it's less than 10 employees, a tiny Python app will do the work in a few seconds each month as well as maintain the database.
AI can write that entire app in a few seconds. With a simple prompt on Google, you can get a fully working application in mere seconds.
Try this prompt:
I'd like a Python/Flask application that uses Bootstrap for a nice user interface for managing my employee payroll information and then allowing me to print out payslips each month. Each employee will have a single payment record per month with about five, maximum seven, deductions each month. The payslip should have all that data.
I typed that in and got a ready application in less than five seconds!
Now, if you know Python / Flask, then it's easy enough to read the code generated and make tweaks to your satisfaction and this is far less work than actually writing the entire thing by yourself, but if you do not know Python / Flask, then the only problem may be making changes later. AI will really screw things up.
Oh, and in the prompt above I forgot to tell Google that I really don't like (hate) SQLAlchemy. I'm very, very old school and are super comfortable writing my own SQL statements and tracking them in a module.
And so the future of software development will be coming up with the right questions to ask the AI engine.
CAUTION
I don't work that way. I normally know how to start and then I use AI (mostly Google and sometimes the CoPilot agent built into Visual Studio Code) to suggest code snippets. Not whole functions, but methods of getting a piece of work done.
I remember when I first came across the DataTables Javascript library for presenting tabular data on the page. A piece of cake to implement and I didn't care too much that I didn't have to paginate long tables manually - though I must admit, that's a lot of the fun of data management - the complexity. But I needed to upgrade the DataTables links for the CDN I was using and also try to get rid of JQuery.
I hopped into Google, gave it the <head> and <script> sections of my boilerplate page with the code to be changed and the suggested "fix" came back almost immediately.
I cut-and-pasted it.
It did not work. My headers were ruined and there was no styling.
Back-and-forth we went, Google AI and myself. My first response was, "you broke everything!" and AI Mode came back with an apology and a fix.
It took a moment for me to realize that the fix contained the same links as the breakage, but I tried it and, of course, it did not work.
"You broke it more!" I complained again.
And another fix came forward.
I knew what was wrong, and what needed to be fixed, but I was too lazy and wanted generated code so that I could cut-and-paste it in. All I needed to do was to head over to the DataTables home page, see the template links well posted for Bootstrap v5 and Bob's your uncle!
Which is eventually what I did. The back-and-forth with Google AI Mode was not looking like it would come to an end.
CONCLUSION
Therein lies the problem. AI can generate the code, full apps, full classes and functions or simply code snippets.
But you still should read them, top to bottom, make sure you understand what's been offered, add some of your own character before you commit.
Knowing that it is guaranteed that one day, you will have to poke your head in the nest and pull a couple of branches, or twigs, out making sure you don't spring a leak.
And it may be impossible for AI to clean up as I found out. It may get into a numbing cyclical brain freeze and you're forced to do a complete reboot.
Sunday, September 07, 2025
my iPad Air 11-inch
MY SETUP
- The battery life was dwindling.
- It was too heavy to carry around with the Magic Keyboard.
- I thought that it was too close to my MacBook Air (a laptop) and I needed something closer to a tablet. Not a laptop, not a phone.
- I dreamt of writing and programming from anywhere, without having to carry my laptop.
CONFUSION ALL AROUND
iPad Air M3 11-inch
Saturday, September 06, 2025
Do You Remember...
READING INSTEAD.
BIKING
WORK
DRAWING
BACK TO ... READING
LIVING MINUTE BY MINUTE
Thursday, May 01, 2025
The Art of Code
Analysis Paralysis
Just Skin the Cat
The Skinned Cat – Now What?
Saturday, March 15, 2025
COMPUTER PROGRAMMING
MINDFULNESS
WRITING
Brown table, glass top, indicative of thought and a fireplace filled with logs becomes light and fuelled by, lost thoughts, carpeting is not good but a floor which is on the way to doors that open and close which is the reason why reason exists if only to become the thing that once was. However, it should be noted that even while you sit and browse as soon as things become overly complicated and the words structure themselves, you can chair the objection to the ceiling in order to remove the process that was getting to be very structural. In this case, you are not noticing but following even if the path takes you to a place that you are not familiar with, as the music plays so do you also play.
PROGRAMMING
f = open(‘file.txt’, ‘r’)line = f.readline()line_length = len(line)
counter = 0
for letter in line:
if letter == ‘a’:
counter = counter + 1




