My understanding is the nature of vinyl also necessitates remixing. That process is more of an artform than a science. I imagine the mix adds more character to the music than the vinyl itself.
Most developers I meet are utter shit anyway. Those who advertise themselves as full-stack developers are no exception. Most developers can't see the forest through the trees, so someone coined the term "full-stack" to differentiate those developers who can. The problem is no one came up with a formula to identify the developers who see the bigger picture, so everyone now claims to be "full-stack".
Programming is the art of abstraction. Systems are getting more complicated. Generalization is getting harder. Developers aren't getting smarter. Those who can see the bigger picture have the edge. They lay the groundwork for the rest of the team to be productive.
"Full-stack" is a buzz word now to put on your resume. Just like cloud computing. I find it fascinating how many candidates I meet who can't even define SaaS when they write "Cloud" on their resume.
Simple scales. Apple's cloud is not simple. Amazon already figured out that formula. Most tech companies think they can take legacy solutions and throw money at it to make them scale.
It has nothing to do with the accuracy. Actually the grid will vary about +-0.05Hz. Basically, if you use the grid for time keeping you have to tweak the frequency to get rid of the accumulated error. That means they speed up or slow down the grid accordingly. This can cause issues with some equipment that can't handle the grid running too fast or too slow. It can even trigger emergency shutdowns of some power generators.
If you're adjusting your gird using an atomic clock it is just as accurate as an atomic clock. If you're adjusting your grid a crystal it's just as accurate as the crystal. That's assuming you neglect any short-term variations in the frequency.
That commit in the article has absolutely NOTHING to do with containers. There is almost no reason to run a VM inside of a container. Sometimes you run a container in a VM.
It reminds me of Airliners. Commercial Airliners always want to push out General Aviation, as if they aren't paying their "fair share". Really they just want to own more of the sky. The airspace is for all Americans to use and so is the road as long as you can use it responsibly. We need to prevent profit-seeking corporations from co-opting the public welfare. It almost never works out the way they claim.
It's not a fair analogy. Software has similar latent failure properties to a poor electrical job. The way we write software now is like wiring a house without a grounding conductor. At one point houses did not have ground wires. Now, if you don't install one it's akin to arson.
>The result is a heaping monolith of layers of unreadable, unreadable code. And for some reason, those same engineers get pats on the back and promotions as they construct their labyrinths of code only they can decipher as everyone who is actually sane screams "We must rewrite it from scratch now!!!". Of course, this is not popular point amongst the deluded individuals who are running things into the ground and wondering why it takes an exponential amount of time and resources just to keep things running. The idea of actually innovating isn't even on the table.
I've seen it all. DevOps guys who can't deploy kubernetes, build a docker container or setup a decent CI pipeline. Software Engineers that still can't master the to fundamentals of Object Orientation after decades of practice. They have no hope learning ML or functional programming. Typesafe languages are viewed by senior technical leadership as cute academic stuff with absolutely no practical purpose.
At this point, I'll probably join a startup just to get away from charlatans.
Nope. The FAA doesn't pilot the aircrafts. You don't even have to talk to the controller most of the time. As long as you're in the right airspace and you are in VFR conditions you just have to avoid hitting other aircrafts. "See and Avoid" is the requirement of the thing directing the aircraft, which has traditionally been a pilot.
The FAA will change their rule once an autonomous drone can meet the intent of the "see and avoid" rule. It will be more like "sense and avoid", but you get the idea.
Slashdot Mirror
I can see this going horribly wrong. Crows know cigarettes and rubbish get rewards. This could easily devolve into a an Alfred Hitchcock movie.
You should be able to classify small code segments.
I seriously doubt it will work well with pure functional programs. Functional programmers tend to converge on similar programs.
Google is has nothing on Amazon.
My understanding is the nature of vinyl also necessitates remixing. That process is more of an artform than a science. I imagine the mix adds more character to the music than the vinyl itself.
Most developers I meet are utter shit anyway. Those who advertise themselves as full-stack developers are no exception. Most developers can't see the forest through the trees, so someone coined the term "full-stack" to differentiate those developers who can. The problem is no one came up with a formula to identify the developers who see the bigger picture, so everyone now claims to be "full-stack".
Programming is the art of abstraction. Systems are getting more complicated. Generalization is getting harder. Developers aren't getting smarter. Those who can see the bigger picture have the edge. They lay the groundwork for the rest of the team to be productive.
"Full-stack" is a buzz word now to put on your resume. Just like cloud computing. I find it fascinating how many candidates I meet who can't even define SaaS when they write "Cloud" on their resume.
ARM won't eliminate the license fees.
Your phone is already spying on you. They don't need a open source processor for that.
Simple scales. Apple's cloud is not simple. Amazon already figured out that formula. Most tech companies think they can take legacy solutions and throw money at it to make them scale.
It has nothing to do with the accuracy. Actually the grid will vary about +-0.05Hz. Basically, if you use the grid for time keeping you have to tweak the frequency to get rid of the accumulated error. That means they speed up or slow down the grid accordingly. This can cause issues with some equipment that can't handle the grid running too fast or too slow. It can even trigger emergency shutdowns of some power generators.
If you're adjusting your gird using an atomic clock it is just as accurate as an atomic clock. If you're adjusting your grid a crystal it's just as accurate as the crystal. That's assuming you neglect any short-term variations in the frequency.
Linux VMs to run inside a container
That commit in the article has absolutely NOTHING to do with containers. There is almost no reason to run a VM inside of a container. Sometimes you run a container in a VM.
You've been watching too much Westworld.
Start with an arduino and a couple of LEDs.
The c/c++ is simple.
I would imagine JavaScript closures are probably the hardest thing to grasp for someone who has never even written a for loop.
I don't call this emulation, just like wine is not an emulator. It is a implementation of the Linux system calls.
The question is malformed. Will Windows and Mac ever be made compatible with Linux?
Windows 10 has implemented Linux system calls. You can run Linux apps on Windows.
LD_PRELOAD is not enough for privilege escalation. You need more, like a buggy Microsoft product. Maybe Skype for Linux....
It reminds me of Airliners. Commercial Airliners always want to push out General Aviation, as if they aren't paying their "fair share". Really they just want to own more of the sky. The airspace is for all Americans to use and so is the road as long as you can use it responsibly. We need to prevent profit-seeking corporations from co-opting the public welfare. It almost never works out the way they claim.
It's not a fair analogy. Software has similar latent failure properties to a poor electrical job. The way we write software now is like wiring a house without a grounding conductor. At one point houses did not have ground wires. Now, if you don't install one it's akin to arson.
>The result is a heaping monolith of layers of unreadable, unreadable code.
And for some reason, those same engineers get pats on the back and promotions as they construct their labyrinths of code only they can decipher as everyone who is actually sane screams "We must rewrite it from scratch now!!!". Of course, this is not popular point amongst the deluded individuals who are running things into the ground and wondering why it takes an exponential amount of time and resources just to keep things running. The idea of actually innovating isn't even on the table.
I've seen it all. DevOps guys who can't deploy kubernetes, build a docker container or setup a decent CI pipeline. Software Engineers that still can't master the to fundamentals of Object Orientation after decades of practice. They have no hope learning ML or functional programming. Typesafe languages are viewed by senior technical leadership as cute academic stuff with absolutely no practical purpose.
At this point, I'll probably join a startup just to get away from charlatans.
ML means Meta Language
Nope. The FAA doesn't pilot the aircrafts. You don't even have to talk to the controller most of the time. As long as you're in the right airspace and you are in VFR conditions you just have to avoid hitting other aircrafts. "See and Avoid" is the requirement of the thing directing the aircraft, which has traditionally been a pilot.
Funny. I have a similar sentiment about certain software engineers. The only difference is it affects younger engineers as well.
Discounts for customers without stairs and no pickups.
The FAA will change their rule once an autonomous drone can meet the intent of the "see and avoid" rule. It will be more like "sense and avoid", but you get the idea.
If only we could teach your printer to not trust you we'd be set.