In the end, a computer may be a bit safer. But if it is high enough value... someone will find a way.
1,174 karma · joined December 8, 2020
In the end, a computer may be a bit safer. But if it is high enough value... someone will find a way.
Think about like 100,000,000 tons of 1% acid being discord.
And 10,000 tons of pure acid being the things I mentioned. It is going to be easier to get burned in the places I mentioned.
Discord has much more acid.... but when ya want the good stuff, you have to look to the specialists.
The "look over your shoulder" attack is omni-present. (Also easier to prevent with paper, in general, than with a larger computer screen.)
A simple safe will stop most prying people. And if you die... Well, you are dead... there ain't much stopping anyone at that point.
Keeping secrets is hard. Very hard. There's a reason for the most part... I don't bother, except if/when I need to, and even then, if they can be timed out, all the better.
Paper also has a big benefit in that we know how to destroy it. :)
... Simple things are often best. Understanding how your system will bend/break is critical in security situations.
Also: If your papers are taken, you probably can figure it out.
At the nation state level... honestly, they'll read it straight off your montior's emissions. TEMPEST exists for a reason.
For these reasons, I tend to NOT trust my computer for absolutely critical things. I prefer paper.
Also remember yesterday's unbreakable crypto is 10 year's from now's breakable and 20 years from now they'll be doing class projects on it in college.
You get good will for your brand, and a person who is very happy in your store at that moment.
Simply Brilliant.
OpenPOWER: It may have to do with the size of the ISA when it started to be open.
RISC-V, when announced was a small ISA. That means making chips is easier.
It could just be the new hawtness effect. Look at how many people use NoSQL when SQL would work just fine ;).
A lawyer can handle the trial for you and things like that. The LLM can help you with issues of fact, etc. And could even make stronger privacy guarantees than a lawyer if setup right. (But I doubt that will ever happen.)
Trusting it blindly is stupid. But, so is trusting any sources without verification.
I think of ChatGPT like a pretty smart co-worker. Just because they are smart doesn't mean they are always right.
And I can still use ChatGPT and similar tools for some of what I do. It is a huge force multiplier.
But I could see that at any firm, in the right situation.
They aren't monoliths. Your experience could be totally different in a different part of the company. 300k people is going to create a ton of variance.
That said, I've found the larger the company, the more politics matters. And the more politics matters, the less your performance matters, and the more the other things matter.
Personally, if given my way, I might never work for a company over ~50 people, again. (I'm working for a small firm now. And pretty happy overall.)
The ability to walk up to high management and get a fairly straight answer on what is going on, is something you simply can't get in a 300k company.
"One throat to choke." If there is a problem, you have operations, and development mixed together to produce one nexus of responsibility.
The moment someone says "I can't.... because I'm not a..." in those situation you've lost the point.
The whole point is... It IS your problem as a team. FIX IT. You have everything. Make it happen.
Now a days... the thread has been totally lost. I've gone back to development. I prefer tossing the dead cats over the fence over receiving them.
Either way... the poor cat is dead... we didn't work together to save it :(
Visual Studio is widely considered one of the best IDEs out there today.
Personally, I use Linux for my work on Linux, what IDE varies depending on my work. JetBrains, VSCode, neovim. But I've used other eco-systems.
I still miss Genera. That thing was amazing.
That is an amazing system, that even now, could probably hang with the best of them. :/
I get it, though I had the day GitHub CoPilot came out and I wanted them to take a long walk off a short pier. (And I still do.)
"I used her, she used me and neither one cared. We were getting our share." - Night Moves / Seger.
In a sense, that's how I view work. I'm there to get a check, they are there to use my labor and make money. As long as we're both happy. It is all good. But... never forget we are using each other.
"Ain't it funny how the night moves
When you just don't seem to have as much to lose
Strange how the night moves"
Ain't it?
Linux did not have full compatibility before it took off. And I don't think the bar is THAT much higher today for a new competitor, where I can swap the kernel in.
If anything it may encourage us to use a few less Linuxisms in our code.
Look at things like ebpf and uring for examples of meeting real needs with new development in the kernel.
I doubt that a LLM will be able to come up with the ideas, and implement these things without substantial prompting.
For the every day stuff. Yeah, sure. Though you'd be amazed how many strange corner conditions POSIX and Linux have even around "simple" things like pipes.
... Understanding the whole context may be beyond where we are today based on what I have seen from LLMs, there may day where they can come closer. But as the Klingons say: "Not today."
And when it changed... Clearcase did not degrade gracefully. It was a full on collapse.
Thinking long term is not something that is rewarded next quarter, in general.
This is a large part of why I've worked over half my career for non-public companies. I want my management making the best choices for the product and the company. Not what Wall St. will like.
If the invisible hand worked... yes they would be the same. Reality says they aren't.
You just found the difference between Open Source (MIT/BSD and friends) and Free Software (GPL without copyright assignment.).
It ain't about money ;)
For those who know Clearcase, and winking in. Well, there was a team that had a 2 hour java build and they were suffering. Nothing was working right.
One could argue that using Clearcase and Clearmake was the error.. and even back then as a PFY I'd agree.
But help them I must. So I wrote a makefile, that wrote makefiles, that would then compile all the code into /tmp, and copy the jar back into place.
Because... Clearcase tracks every file you touch, it is critical, you ONLY touch your inputs, do not produce extra .class files where it can see them, or you'll end up with a bunch of files all interdependent and confused.
Their build went from ~2hrs to about ~5 minutes when I was done. Less if it "winked" in everything.
... The amount of good, stupid can do is amazing.
The curation of an experience is undervalued by many.
Just like coding isn't about mechanics. It is about understanding requirements and coming up with solutions that meet needs