Software development for rev 1.0 is not usually the most expensive. It is maintaining and extending the code as requirements change and new features are added. This sometimes requires the decision to incrementally improve the code. Other times it requires some significant refactoring. Finally, in the worst case it requires the decision to throw the whole thing away and start over. Thus far, AI is very good in many cases at crafting a functioning version 1.0 release. But, once you try to change it, it can become a great big mess. Good architecture and design improves the length and ease of maintenance going into the future.

HP has realized this. Look at the "Smart Tank" printers from HP. Much more affordable supplies.

Reusable plastic bags are a good choice but be sure to sterilize them regularly.

https://health.clevelandclinic...

AM radio requires the least amount of infrastructure to keep going. In addition to HAM radio I also keep a GE Superadio handy as it has some of the best reception in a portable radio. At night I can often listen to California stations in SW Washington.

https://www.universal-radio.co...

I mentored multiple people while working full time remote over the Covid period. Two of them were recent college grads that hired on with us. Their growth was phenomenal and they have become fantastic contributors. Not bad for someone 2-3 years into their careers. My wife who worked at a another company was famous for mentoring others. They have been remote for over 11 years. We both recently retired so alas our professional mentoring has come to an end for these companies. We have found other opportunities in the recent months. Between us we make a good team between computers and finance and have helped others learn. Mentoring is something you need to promote and something you are willing to do. Some cultures make it a waste of time and being remote makes it even easier to avoid.

Agreed. Lack of street names alone has caused me to move more to Apple maps. And, try to get the exit numbers on the interstates.

I don't use self-checkout at the grocery store. The automation allows companies to low-ball wages and to automate people out of jobs. I refuse to support this trend. Using cost as the only metric in a business does not lead to a greater good. When I go to the store or one of these AI restaurants, I will always ask for a person to do this. If nobody uses the automation, they will be forced to hire people and probably raise prices as well, but that is OK.

Emacs malware!! Dem's fighting words. ;-)

--Emacs(and vim) user for over 30 years.

Offshoring repetitive project types or work does work to some extent. Doing something fundamentally new or with a high level of innovation usually does not work too well. Having them do well-known patterns such as putting a React utility UI over some of our REST endpoints seems to be optimal. Bottom line, as mentioned above, assuming you can just replace local teams with offshore is a simplistic way to head downward into disaster.

Demonstrate they can do it by having lots of calls supporting Trump. Twitter will be in an uproar and they will figure out how to cancel those calls within a week.

The Telco execs should get one call for every 100 robocalls sent.

We now have a global economy and many of us routinely work with people on the other side of the planet. Let's just everyone use UTC and be done with it. Each person post the hours they expect to be up or working and other people deal with it(or you mutually work out an agreeable overlap). If a company wants to set up shifts where people in the same or similar timezone are working that is their choice. Some people or night people, some people are morning people and forcing them to work a shift that is not compatible with their biology is both bad for their health and somewhat cruel.

Bottom line, get governments out of the time regulation business and everyone references the same timezone. No more constant browsing to timeanddate.com to figure out if someone is available.

In the real world there are often multiple cameras pointing at each other so that it makes it much harder to obscure and/or spoof a camera. Here is a case where we have a single point of failure and no other systematic monitoring to make sure that single point failed. Ideally, there are multiple security detections both for triangulation as well as layered security with independent gates. Having "root" for the whole system is ridiculous.

I had a similar experience.

I was getting scanned on port 22 at least 2-5 times a day. I blocked the approximate Russia and China subnets and the scans almost dropped to zero. Another thing that helped was to listen on a non-standard port. I very seldom saw a thorough port scan.

I see this every day at the Fortune 500 company that I work at. It is the challenge of finding the optimal spot amongst all the variables and software quality needs to be compromised. Good management will value it appropriately while others will neglect it because itâ(TM)s not on the spreadsheet.