I was hired in the early 90's by a collection of franchises for a home care company. The privately owned head office self-developed and distributed required monthly updates to the only software franchises were permitted to run their business. The monthly updates (floppies) reset the license for another month at each location. After years of problems, poor support, and in a couple cases offices getting shut down because head office just "didn't like them anymore", they banded together to sue the owners (one of which developed the software). I did IT work for a couple of the offices and was already familiar with maintaining the software / systems. They hired me to bypass the licensing code which was a lot of fun to figure out. In the end I wrote a DOS based license generator each office had that could update their software by just getting a code over the phone for the upcoming month (or any date for 365 days). A few years later once the lawsuit settled and the company broke apart we issued a patch for the software to remove the license check completely. I should fire up DOSBox sometime so I can play with that old software again.
Let it be a choice, with the mandate that if you opt out and later contract it there will be no state funded assistance down the road. Your choice shouldn't be a burden on the system.
I loved Dilbert and I really believe that you often have to separate art from artist if you want to enjoy many things. He put a very unique perspective on corporate and tech environments that made me laugh. Sad to see a human pass but also sadder that later he expressed some disappointing opinions that diminished his contributions.
First thing I do on any Windows machine is uninstall OneDrive anywhere possible. It's caused me enough grief that I just avoid it entirely at this point.
We were on the same page. I also built something similar for a Conveyor company here in Canada in the early 90's. We parameterized all their tech drawings (or at least the initial versions) from their component libraries. Was a great project. Not sure how long they used it, they eventually acquired the resources to support it internally (I was an independent AutoLISP contractor). Good times back then. I haven't done AutoLISP in years now but great to see it's still around.
Ha, so I wasn't alone! Conveyors are a perfect fit - standardized components, parametric variations. The pattern was obvious once you saw it. Good to know it worked for you too.
I have a folder in my server where I archive the last several versions (usually 3-5) of all software I install. It would have helped in this situation but the main reason I started doing it >25 years ago is in case companies disappeared.
Perhaps I say at all the wrong (right?) hotels but... I stay in close to two dozen North American hotels a year and I haven't noticed this trend? Many have pocket doors but I can't think of a hotel in recent memory that was missing it completely. I usually partially close them so it's not as cold getting out of a shower so I hope I would have taken note if it wasn't there.
I rode in one of these in Phoenix in June, loved the experience! Had to go to a pharmacy so purposely picked one a half hour across the city so I could just watch the car perform. Felt like the future (though it did glitch once). Made a sudden turn off the road into a parking lot, did a lap of the outside of the parking lot, and exited back onto the same road to continue on. Must have thought something was blocking the road and made a detour around it? Other than that it seemed pretty flawless.
Please make AI disappear altogether until I want it. No pop-ups, no floating "Help me..." in fields, no spinning flashing icons on toolbars. I submit feedback on all products that do this that I would like a way to turn it all off. AI is useful when I want it, otherwise it's just annoying and gets in my way.
This sounds like myself as well. We are a small dev team of 6 (in a company of 30), however I also have a partial ownership stake in the company. Even though I spend a significant part of my time on "CTO" style work (client meetings, market assessments, product overviews, roadmap planning, third party collaboration, etc.) there also isn't near enough of that to fill my time or justify my salary. I code and review like my team does, but I also oversee technical direction for our whole portfolio and the responsibility for that technical success or failure rests on me. As we grow the coding will decrease I'm sure, but I see a lot of people here criticizing from a perspective of larger companies where a CTO would be a full time responsibility. In our situation the title (as much as I often dislike it) represents my level of responsibility, if not directly the full scope of my role.
reply