198 karma · joined November 27, 2017
Man we will do anything to not use the metric system. ;)
(tomorrow)
Twitter: Oh hey, we have a minor update to our TOS.
One thing I will add is getting tools and resources to do the work you want to do can be a challenge. There can be times when getting through the process to buy a $75 multimeter can be more difficult then the $16,000 signal generator.
I haven't worked for the government for 6 or so years, but the last box of skillcraft I had maybe 3 worked out of the box, and not one made it through annotating a paper. It was so bad that I bought a box of cheap store brand ones for myself so I could take notes.
One of the original methods used as copy protection used a special industrial writer write a invalid block, data was ok but the error correction would say it's something different, and check because the consumer hardware wouldn't read or write these blocks.
Take heed young adventurer: This balm will not solve all your ills. It will be your hard work, compassion, and perseverance that will bring the new golden age and sustain it.
TLDR: We've done this before, it solves some problems and causes other.
At $865 million[1] and 14.5B miles that about 0.034 Euros/Km. 1/20 of what he did in 2005.
1: https://voyager.jpl.nasa.gov/frequently-asked-questions/fact...
I kinda feel like I'm watching a glassblower and getting asked "So what do you think?". I could say if I like the piece or not, but I don't know the first thing about glassblowing to give effective criticism.
The first is if GitHub had a license to distribute the code they have learned on. This is assuming that the code it produces is a derivative, which I don't think would be much of a stretch. For this I think most of the licenses that are used, GPL MIT etc, allow for someone to distribute in such a way.
The second is the user of copilot. They would be getting and distributing code where they wouldn't know the original license, but that wouldn't be a viable defense of infringement. To actually comply with most licenses they would have to follow the requirements.
In both cases I don't know if a fair use would really apply. Maybe GitHub could stretch the research aspect, but if you just use the code in your product there is no fair use.
now I'm also really glad that when I got BBVA's terms I said "Hell no!" And found a different bank.
This will change. If there is more drag then expected, or any one hundreds of different things happen, the reentry time will change, and then the predicted area will change.
I'm actually scared what the internet will look like less 230. I'm guessing we will see more 4chan then pre-approved comments, just because that scales easier.
Where I was about 99.9% of the COEs where just a lesson learned and new process to prevent it. There was one that was basically used as a tool to remove a VERY good engineer, that didn't mesh well with new leadership.
A sister org, one I worked a lot with, wouldn't COE anything. If you were the lead engineer on a product or service that had a COE you were going to get a PIP by year end review. I wasn't surprised when all the talent left that group.
Here is my example, I have recently finished a project where while under development we were running instances at around 1.5x then we needed. We knew they were oversized, but not by how much because we were more focused on getting features done then making it efficient. When we were "done" we took a sprint to figure out what the "right" size needed to be, by measuring it. This means over the 6 months we "wasted" $2-3k, but you know what would have cost 25-30k? If we were running underpowered machines, that uncovered an intermittent bug that added a month to our development schedule.
Remember the goal is to be frugal not stupid. So before you try and do ANY cost cutting activity you need to go figure out what the impact of it might be, make sure you have some way to measure that impact, and then only do it if the cost of implementing is less then the savings.
What most people don't understand is that it's important that the demand + the transmission losses = the production, not just as a whole, but also for each link. To help with that most places don't produce 100%, and a lot of higher power links are redundant. But that can only cover so much. If it's not a high demand day you can probably source power from other providers, but sometimes that's not enough.
Looking at application development I think a similar thing could be done, but what would we pin identity to? I don't know if there is one thing that every app has like a website.
I could see a number of reasons why a content provider would want to remove a particular type of content from their site, like the consumers of that content are bad for business. You don't have any right to continue to use these services, why should you have a right to continue to have your content hosted with them?
I don't have good sound proposals, but bonuses for positive steps might be a good start.
Of course, this is completely different from the idea of QI, which, having worked for the federal government, I can see why it's important. Even if it has been over-applied.