I mean, not really. Imagine how much more information they can collect by literally observing employees all day in the office. There is no limit to the amount of information they can gain from surveillance.
Afghanistan needs to be left alone. Those poor people just want to live their life. Having been there and talked to people, that’s all the want. They all say the taliban is better than constant war.
We had a four story office building just for engineering and technology. The business has taken it over. We have the top floor and it’s empty. Our new policy is remote if you want. Office if you want. Whatever you want. Just do good work.
Friend of mine just runs a script to verbose git clone, npm i, ng test, rm and start over. Just fills his screen with log statements. Of course, everyone knows he isn’t doing dick but he’s convinced the security cameras are watching him.
The only problem I can recall from using UUIDs was having to write adapters for the serialization and deserialization common with DTOs because it is treated like a value instead of an object. Other than that, love them.
I know from my experience that my employer's ecosystem is entirely built around having java applications. We moved to kube and that has eased a bit; however, we're all java developers. I attempted to push the bounds of our "use the best tool for the job" policy and worked in dotnet for awhile and I was hit with a lot of pushback. First off was using spring cloud config and trying to figure out steeltoe for my application, but I powered through it. Then came getting support for a new build process with our build agents and pipelines. Just constant pushback on everything. And then there was the review process. It was hard to get PRs done because no one cared to look over "the dotnet" project. I say all that to say that moving to Go or nodeJs isn't easy because it requires a lot of personnel work to get there, for enterprises at least. They have invested a lot into having Java apps and moving to a new stack requires proving out that the investment for the move will outperform the current investment and then some.
From the logistics industry, this problem is definitely harder than it sounds. Scheduling is one thing but scheduling accurately is difficult. I spent two years of my life working on developing a system to consume various inputs and predict when a load would be delivered. This was anywhere from cross country OTR loads to in-town deliveries. The main problem I ran into was the business wasn't willing to limit the inputs to the system and threw everything plus the kitchen sink into the algorithms. This, IMO, unnecessarily complicated the problem. I would give anything to try this system over again.
Sure, it is the job of the CTO to steer juniors in an appropriate direction. But, and I hate to say this, isn't it also the job of the CTO to help source funding and it seems VCs like to go after the buzzwords?