Dave.

And how if you share a file in Teams and then six months later you want to share a file with the same name to ANYONE else via teams, well that’s a big no-can-do. Teams just went ahead and uploaded that file to your “stuff to share” folder in OneDrive and didn’t put it in a subfolder unique to the chat, or add a unique prefix or suffix or anything because hey, you’ll only ever share a file with a particular name once in your life, right?

And nobody would ever want to share a file with the same name, but different data, right? So Teams can just give the end user the choice between replacing the current file with the new one, or sharing the same one again to these new guys, because there’s no possible use case for actually having two files named the same with different information in the file, right?

Nobody would want to share a README.TXT, or Photo001.jpg, or contact.ics, or a zip file of a folder they just downloaded from Teams’ SharePoint interface, the file that’s automatically called “OneDrive.zip” without the option to change it before saving, more than once, right? Right??

Fuck teams. And fuck Teams(New) too, just for the shitty name.

Generally I bash together the one-off programs in Python and if I discover that my “one off” program is actually being run 4 times a week, that’s when I look at switching to a compiled language.

Case in point: I threw together a python program that followed a trajectory in a point cloud and erased a box around the trajectory. Found a python point cloud library, swore at my code (and the library code) for a few hours, tidied up a few point clouds with it, job done.

And then other people in my company also needed to do the same thing and after a few months of occasional use, I rewrote it using C++ and Open3D. A few days of swearing this time (mainly because my C++ is a bit rusty, and Open3D’s C++ interface is a sparsely-documented back end to their main python front end).

End result though is that point clouds that took 3 minutes to process before in python now take 10 seconds, and now there’s a visualisation widget that shows the effects of the processing so you don’t have to open the cloud in another viewer to see that it was ok.

But anyway, like you said, python is good for prototyping, and when you hash out your approach and things are fairly nailed down and now you’d like some speed, jump to a compiled language and reap the benefits.

Australian here. Last time I wrote a cheque, Michael Jackson was still black.

They are supposed to be the glue that binds the internal team together as well as bonding to external groups.

The project manager organises external requirements and steers the project in the direction needed for the business. That direction might change depending on the status of other projects, it’s their job to be on top of that.

They also report progress and roadblocks upstream so that those who manage groups of related projects can work on keeping everything running.

Whether they’re actually competent, well that’s something else entirely.

You can stare at that code all afternoon but you won’t spot the bug until a microsecond after you hit “commit”.

Having SSD dram allows the SSD to say “done” sooner to the OS despite it taking the same total time.

That’s exactly why. When writing to a drive the OS waits until the disk says “done” and then goes about it’s business.

If the drive then takes an extra bit of time internally to write to permanent storage that’s none of the OS’s business as long as it can pull that written data from “somewhere” and deliver it to the OS if asked.

You should release what you’ve written as a framework, that’s what everyone else is doing.

<Insert XKCD standards comic here>

Seems to be a rare thing,

Didn’t you know? All the cool kids these days skip documentation and just hang out on discord, where you can get a laggy response to your query about build dependencies in 2-3 business days.

Nah, you’ve always got to check the corner cases. It’s a variation on Murphy’s Law - you don’t encounter corner cases when you’re developing a program but corner cases are 99 percent of an everyday user’s interaction.

What your code can do is run this first and if it returns false then do a quick double check using a traditional isPrime function. Really speeds things up!

Mmm I have a general dislike of systemd because it doesn’t adhere to the “do one thing and do it well” approach of traditional Unix systems.

It’s a big old opaque blob of software components that work nicely together but don’t play well with others, basically.

Edit: but it solved a particular set of problems in serverspace and it’s bled over to the consumer Linux side of things and generally I’m ok with it if it simplifies things for people. I just don’t want a monoculture to spring up and take root across all of Linux as monocultures aren’t great for innovation or security.

You! You are BANNED from this forum! You, and your children, and your children’s children!

For six months.

strings mysterytool

As a last resort haha

Red Hat 5.0 for lyfe.

Kernel 2.0.36 represent! ✊

Open it up in midnight commander, and it will unpack it into a virtual directory structure, complete with install/uninstall scripts.

Look at the install script to see what it’s thinking, pull out the file structure, copy into your filesystem.

Oh, and hope. Because often you need to get matching glibc and other dynamic libraries that the program was compiled against. Which isn’t the end of the world as the dynamic linker will look in the local directory where the program is first for libraries, but it becomes a hassle pretty quickly.

It’s not a dramatic thing for me personally. 90 percent of the time my laptop politely sleeps when I ask it to, the remaining 10 percent of the time it’s going to sleep regardless of its opinion on the matter.

Small edit: I have sometimes been the unlucky recipient of a bundle of windows updates that that 15-20 minutes to complete. One thing about Linux distros, they don’t pull that kind of stunt in shutdown.

And lucky you to be able to not have any last minute things to deal with at the airport that get foisted upon you by clients / coworkers. Computer time is never over.

Nope. Not when my laptop is connected to my monitors/dock at home. The screen locks, the monitors time out and power off, everything else remains on/dormant. When travelling with it, it just hibernates.

If I had a desktop PC and it had fans/etc I would probably hibernate it rather than shut it down. As I understand it windows tends to do this by default these days as well.

Would be nice, but it (that is, windows in this case) won’t go to standby because by the time you get to the shutdown/update stage, power management is shut off.

Instead it turns into a lovely mini furnace in its pocket in my travel bag until windows deems that it has finished.

Edit: and that’s what I find alarming. Once , I just hit the power button and closed my laptop and got on the plane, and about 15 minutes later I went to get something from my bag in the overhead compartment before we took off. Holy shit, was my laptop hot, and it was 70 percent through an update. Presumably it was throttling due to heat and the throttling was making the updates even slower so it was a vicious cycle.

Tell that to my laptop when I’m at the airport and boarding.

It’s the same with windows - push power button, “Windows is installing some updates, do not turn off y…” (screen goes blank from the forced shutdown as I continue to hold the power button)

If I’m turning off my computer, I’m turning it off for a reason. Any delay gets in the way of my reason nearly 100 percent of the time.