Tag: Learning

Time For Me To Get To Work

I write in this blog about different aspects of technology and different ways of looking at how to use technology. I post links to other sites, about technology, which interest me.

Honestly, I could have done that in a diary and skipped the whole process of setting up a website. Using pencil and paper to record thoughts is pretty old technology. It’s definitely stood the test of time.

I started a blog, which has multiple steps, to learn more about how to set up websites in the current year. I’ve decided it’s time to remember that and get back to work.

There’s lots of sources, I think it’s more important to pick one and get started. So I’m going to try Khan Academy. I took a look at their basic courses on websites the other day. It’s under the heading “Computer Programming,” which I didn’t expect. They advocate learning JS before learning HTML and CSS. I didn’t expect that. I’ll start there, and see how it goes.

Perspective: The Last 20% Which Is 50% of the Entire Project, Part II — Ongoing Projects

Last week I wrote about the last 20% of a project which usually takes 50% or more of a project.

What if it’s a situation like this blog? This blog doesn’t have a set end date or a defined end goal. What then?

My experience is it will be entirely too easy to get caught up in details. I’ve thought about it, read about it, listened to podcasts about it. After all that, I’ve come to the conclusion an ongoing project can’t be treated as an ongoing project. It has to be treated as a succession of a number of set goals with set timelines.

The purpose of the goals and timelines isn’t to create an impossible amount of work, and to then beat myself or someone else over the head with failure to meet that impossible standard. Rather, the purpose of the goals and timelines is to have a strategic plan. This is the only way I can see to avoid being caught in endless rounds of minutiae that is the end details of any project.

Perspective: The Last 20% Which Is 50% of the Entire Project, Part I

How Most Projects Start and Progress

Almost every project has a final portion which feels — not planned out or calculated, but rough ballpark estimate — like “about” 20% of the project. It’s the small details at the end.

A big idea was conceived, prototypes were tried, a plan was made. The plan was followed, somewhat. There were mistakes and do-overs. Unexpected obstacles came up and were dealt with. The end is in sight! Most of what remains is small fiddly stuff.

That Last Fiddly 20%

That small fiddly stuff, in most projects, solo and group, hobby and professional, “feels” like “about” 20% of the project. That’s the same impression and discussion I hear from almost everyone else I’ve talked to about this phenomena. It’s not even a quarter of the project, not even 25%. It’s probably only 20%.

And that 20% — the quilting and binding on a quilt, the editing and spell checking and format checking and fact checking on a document, the sanding and finishing and possibly staining on woodwork, the documentation and environmental testing and agency approvals on an electronic device, and a million other examples — will actually take about 50% of the time and energy of the entire project.

That last detailed portion will take about 50% because it is so detailed. Some parts can be automated, a bit. I can use spellcheck on a document, but I shouldn’t rely on it, I’ll still need to check again. There are powered sanders for wood, but I see most woodworkers use touch or sight for one last check. I know of no ways to automate weaving in yarn ends at the end of a crochet project.

I almost wrote about changing formatting in a document, but that would take a whole post in itself because Microsoft Word is so ubiquitous and so unhelpful. It’s unhelpful when I’ve tried to change document-wide formatting after a document is done. It’s unhelpful when I’m trying to tell it whether a list should be treated as a formal ordered or unordered list. Fighting with overly helpful word processors often takes an amazing amount of time.

Avoiding This (Maybe)

It’s better to budget the time for the end of the project, at the start. Saying “oh, it’s probably about 20% of the project” and then finding out it’s 50% is stressful for everyone involved.

Why Is This “Part I?”

Avoiding this is difficult enough when the project has a definite end in sight.

But when it’s a blog, like this, which is ongoing? Does the tendency to mentally assign 20% to details still occur? Even for someone like me, who tends to be more focused and tolerant of the fiddly details for most? I’m finding that yes, it does. I’ll write about that more in Part II.

Error 79 on HP Laserjet M251nw. I changed the document scaling.

Spoiler to the story is in the title.

I’m not going to tell a three-page story full of angst, drama, and existential musings, when my solution was “I changed the document scaling and it printed.”

I am going to rant a bit about what happened before I found that solution.

The beginning of the story

More formally, the full name on the printer is “HP LaserJet Pro 200 color M251nw”. I bought this one used several years ago. The previous owner did not like how much the toner cost.

I was printing out a multipage document. I saw error code 79, firmware error. This sounded bad. The printer said to turn it off, turn it back on, try to reprint the document. I did. I still got error 79.

Multiple websites later, most of them recommended power cycling and trying to print again. I had already tried that.

The red herring: A surge suppressor???

At least one website said to disconnect it from any surge suppressor and plug it directly into the wall outlet. I was dubious, thinking that 1) I cannot see any way there would be enough line drop, current limitations, change to voltage waveform, change to line characteristics, or anything else I could think of which a surge suppressor would create which would prevent a previously functioning laser printer from continuing to function, and 2) if for some reason the circuitry is so tender and so balanced on knife’s edge that a surge suppressor does prevent it from functioning, and it got through HP’s design, design review, and QA teams like that and was still released, I would doubt all HP products forever after.

No, the surge suppressor had nothing to do with it. I have no reason to doubt HP’s products. I have no idea why that website said a surge suppressor could the cause of the firmware error.

What no one suggested (no one I saw, anyway)

After more troubleshooting, none of which I saw recommended on any of the sites I looked at, I narrowed the problems down to one page. It was one page, out of dozens, which caused the error 79 to show up when I tried to print it.

It was a PDF page, original scale 8.5″ x 11″. The page was a scan of an older document printed before laser printers existed. I had set my PDF reader to automatically scale to page margins or printer margins or something like that. It came up with a scale percentage around 99%. I changed to a custom scale, and reduced it to 97%. Then it printed fine. No errors, no problems.

I fixed the error, in that document, on my printer, by changing the document scaling. I have no idea if that will work for anyone else.

Great Power Brings Great Responsibility

Yes, it’s trite. It’s also true.

Not having to do repetitive routine tasks by hand is one of the benefits of technology.

An obvious example is using a spreadsheet program to create and calculate spreadsheet numbers, instead of having to write everything by hand. And then not having to rewrite everything by hand because one of the starting number changed.

A less obvious example is being able to model unsolvable math problems. Back in the 1990s I was told there were heat transfer problems which engineers and mathematicians had not been able to solve with calculus. Those same problems could be solved by a computer program modeling heat transfer over thousands and millions of small volumes.

However, with great power comes great responsibility.

That same computer will do other things we ask it to do, like delete every file we have. There was an article in The Register, “Automation is great. Until it breaks and nobody gets paid.” It was published on April 14, 2023 and written by Simon Sharwood. It is part of The Register‘s ongoing “On Call” series where readers write in with stories of tech problems they’ve had to fix.

Even more enlightening than the story was the comments section. There were quite a few comments in there about former co-workers who had written something “simple” which had very not-simple repercussions.

Technology is great and saves a lot of time, but only if it’s used responsibly and wisely.

Have You Decided What Your Intent Is?

I was looking at some purchased patterns today. None of them really fit the purpose I want to use them for.

I realized I’d look differently at the patterns depending on what I was trying to achieve:

  • Do I only want a pattern that looks nice, done and move on to something else?
  • Does my purpose require specific properties like right angles on two edges, or it looks nice when mirrored?
  • Do I want to look at the pattern as a starting point to make my own patterns in the same style? And that means I’m looking at aesthetics?
  • Or do I not really like the design, but I like the way it was constructed and I want to learn from that?

The first two points apply if it’s just a hobby project. But I ever want to look at that craft as a way to make money, I’ll need to think about the second two points too.

How It Fits Together, How It Moves

It’s just as important to figure out how things move together, as it is to figure out how they fit together.

It’s also a lot more difficult. When things aren’t moving correctly, it’s easy to see. My computer doesn’t boot up, my kitchen appliances don’t work, my sewing machine doesn’t sew. These are all things that happen when things don’t move together correctly.

Intended movement isn’t usually shown in user manuals or service manuals either. I suppose in some cases it might be a trade secret. In other cases it might be something difficult to document. Seeming odd or arbitrary troubleshooting in user and service manuals often seems to be focused at getting parts aligned to move the way they’re intended.

Timing in software is an entire other black art.

Slowing Down to Speed Up, Writing Edition

I listen to some small business and entrepreneur podcasts. One of the phrases I frequently hear is “slow down to speed up.”

I’ll be honest, I typically hear that right before the host explains why they fought that idea when they first heard it, before having to learn it the hard way. And by “hard way,” I mean by repeated painful experience. Anyway, I’ll get back on topic.

Slowing down to speed up also applies to writing. I used to wonder why there were so many different types of notebooks and stationery. For that matter, why were there so many different types of accounting ledger books?

In both cases, writing something down and then rewriting it somewhere else in a different way helps focus the mind.

For writing, I’ve seen guidelines which say there is a creative mode which runs fast and often a bit too free, then there is the editing mode. These are different parts of the brain, and trying to switch in and out of editing mode while ostensibly being in creating mode doesn’t work that well.

I’ve tried that with writing and it does work. I’m still not fully in the habit. But each time I get a little bit better are remembering to let it flow first and then go back and correct later.

I’m also finding it helps to do that with money. I don’t write down every cent of every transaction, but I’m starting to create a list of regular expenses, pulling the information from multiple other places it’s recorded. And it is helping me focus on what I want to keep and what I’m fine letting go.

Why am I writing this on a blog about making technology work for you?

Technology has created so many time-saving services, it’s erased the friction which used to exist. So we all, myself included, want to let the apps and programs and whatever do it all for us. When we do that, we convince ourselves we’re going faster and faster. But we’re planning and considering less and less.

A re-read and rewriting of a good idea is better than writing it hurriedly fifteen times. And it will be fifteen times because we’re moving so fast we forgot what we already wrote.

An inventory and accounting of what classes and guides and books have already been purchased is better than purchasing more variations of the same thing. But it’s faster and feels faster to just buy more of what has already been purchases.

Slowing down to go faster is a real thing.

Useful Link: Humble Bundle For Good (And Sometimes Unexpected) Deals

I can’t remember how I found Humble Bundle. It’s a really great and thoroughly addictive site. They have bundles of various things such as software, games, and digital books. The prices are usually unbeatable. Part of the price will go to a charity.

There are usually online class bundles for something software related at any given time. They also have many book bundles. I’ve seen book bundles on software, but also on hardware, sewing, outdoors skills, and many other things.

The bundles are limited in time and it’s unpredictable (at least to me) what will show up at any given time.

It’s definitely a good site. No, I’m not compensated by them in any way. I think it’s a good site.

Useful Finds: Taking the time for a class rather than re-inventing the wheel, MS Excel

I generally avoid Microsoft Office if I can. It tries to do too much. And no matter how much I log in and confirm on whichever websites, if I am using Microsoft Office while I’m logged in to Windows on a different email than I bought the Microsoft Office license under, Windows and Microsoft Office throw fits.

Currently, I’m working on a project which needs Excel. I signed up for a couple of Udemy courses. I’m currently working my way through the first one, Unlock Excel VBA and Excel Macros by Lella Gharani. I’m only partway through and I’ve already learned a lot.