Engineer #1: "Look at our amazing CO2 scrubbing system!" Engineer #2: "What's powering it?" Engineer #1: "That very large diesel generator right over there!" Engineer #2: Looks at floor... "You know..."
A system like this should be engineered to have some set of distinct modes like "Standby", "Testing" and "Live".
In order to put the system into "Live." should require a physical interconnect such as a key.
I would imagine from the "console" where you'd choose "Live" be prompted to turn the key. Then once it verified the circuit has been closed you'd then be able to choose from the live menu which thing you wanted to send, you'd then be presented with a big blinking red dialog box saying something like "THIS WILL SEND A MESSAGE STATEWIDE!" where they'd have to accept.
Once the message is sent, the system would automatically transition back into "Standby" mode. The user would then be prompted to open the circuit and remove the key. At that point the user could then choose "live" or "test" again.
I would also make these different modes have different colors / borders etc so there's zero confusion which mode you're in.
Considering they LOX drop and test fire each engine, eventually with this many engines you were bound to have one with a flaw. All I can say is, good job.. better on a test stand than on a Falcon 9.
My take on the Indian launch system is this. 1. It's a 4 stage rocket utilizing toxic hard to handle propellants. Everytime you add a stage, it introduces complexity and places where things can go wrong. 2. How fast can they manufacture these things? What happens when SpaceX decides to simply junk launch well worn F9's for 5M so they can write them off the books?
With that all said, buck shot firing a 100+ 3kg satellites into space is cool.
If you're one of the other launch providers, I can only imagine what this must look like.
For years, these companies laughed off SpaceX as some billionaires hobby. I suspect the laughing has officially stopped and lengthy meeting have begun.
These other companies in a response to SpaceX have promised reuseable rockets to bring their costs down, but at this point they're dreams on a whiteboard.
I see a number of problems any competitor is going to have. 1. In many cases their production line is optimized to prevent funding losses from their governmental sponsors, not to create lots of rockets. 2. Their cost/revenue structures are bloated. 2. Once SpaceX sets this pace for launch cadence it's going to be very hard for competitors to keep up. Especially when SpaceX is going to have a literal fleet of used boosters at their disposal. I can only imagine some satellite provider going into talks starting with "If you can't launch 10 a year, then we're walking... oh and we also want them super cheap as well..."
This race to the bottom is going to be very detrimental to other launch providers who'll have to try to cut corners to save costs and speed up production. I expect to see SpaceX's competitors have more failures.
Which pretty much means you're ass is going to be in the seat for the whole ride. Imagine a 120kg adult flying through the cabin because of a 3g deceleration.
Investigator #1: "How did these people die?" Investigator #2: "That fat fuck splattered against the wall over there was wandering around when suddenly emergency deceleration happened, he went cartwheeling through cabin like a wrecking ball"
Think about the fact that ~700mph = ~1000fps. For something like a hyperloop, the whole tube is going to be embedded with sensors. The moment an anomaly is detected, I'd imagine a whole pile of safety systems would kick in.
Though one has to imagine, most people generally don't like 3g's of acceleration, so how many miles of tube do you need to get up to the 700mph speed? Go about ~1.2g's during take off and you'll get complaints at the end of the flight.
Ultimately I predict this will be a loser of a deal. They'll build this plant, it'll be massively automated and employ few people and be massively productive.
Let's be frank here... 3 Billion dollars is A LOT of money in Wisconsin terms. This will be a major hit to the states tax revenues.
I hope this story is true, but my bullshit alarm is going off slightly. So when you didn't get a response to your text... you simply did nothing and waited to fire two of the best pen testers in the world? Sorry sounds fishing, but moving on...
If it did go down this way something tells me when the upper-upper management gets wind of how poorly this piece of asshattery was executed, this executive will be told politely to GTFO. The bad press alone will likely be this clowns undoing. The angry masses will demand a sacrifice and one they shall have.
Remember that a dumpster fire is where you specifically would light the dumpster on fire behind the store and when everybody ran out to put the dumpster out (to keep the whole building from burning) the thieves would run in and rob the place blind.
We're so busy watching the dumpster burn we missed the part where the republicans after instituting the nuclear option have appointed hundreds of judges. Trump will be a bad memory but these ass clowns will be with us for a long time.
Yeah, a big chunk of the GOP leadership is aghast by what's going on the WH, but it's not stopping them from taking advantage of the situation.
1. He'll simply slip into obscurity as that guy who was the first press secretary in a long line of press secretaries for Trump. Pitted by forgotten.
2. He'll come out strong as being a voice of reason in the white house who finally left in disgust when he realized Trump is surrounded by sycophants and ultimately Trump is a shitweasel. His reputation will be salvaged as the guy who left.
If option 2 becomes true maybe he becomes some kind of spokesman for/against the administration? Who knows!
Boss: "Let's deploy this application to the cloud!" Sysadmin: "Does it make sense to put it in the cloud?" Boss: >Holds up a CIO magazine with a picture of a cloud on it< "Because it'll be in the CLOUD" Sysadmin: "What's this application going to do? What type of data is it going to be handling? Boss: "But it'll be in the cloud, it'll be <looks quickly in magazine> a fully virtualized extensible angular flask framework!" Sysadmin: "You're just reading buzzwords!" Boss: "Let's senergize our git repos with our FOSS machines!" Sysadmin: "Fuck me."
Microsoft still hasn't solved the really annoying nagging problem... apps. I have a really nice blackberry Z10. Well okay, relatively nice, who are we kidding it's a piece of shit. The hardware's okayish... but you know what makes the phone a real piece of shit? I can't fucking run [Insert App I might want]. Granted compared to my wife or daughters that list of apps is small... but I only have to look at the shitton of apps my daughters have on their phones to see why this phone will fail. Does it run the cartwheel app, which seems to be a favorite of theirs. How about the latest chat apps? Yeah, didn't think so. Does it run Candy [King / Crush / Castle / *]? Yeah, didn't think so.
The problem is these companies i.e. app companies know most people have either an Apple or some flavor of Android. Microsoft is either going to make an SDK that mimics to the syscall everything one of those two platforms does or they're fucked.
Don't confuse work and life. You work to live, you don't live to work, that's what differentiates us from beasts of burden. Yes, I love what I do and I'm good at it, but I put my tools down at the end of the day and go home. I garden, I make cheese, I backpack. I unapologetically use up all my time off. When I first started working, I didn't use any and I burned out.
I once had a boss complain to me that use all my vacation time, I ask them if they'd like to go to HR and formally complain I'm using the vacation time that's part of my compensation package. Oddly, they didn't. I then pointed out that they thought it was sad that the company I should value my job over my health and my family. I pointed out that when I'm on the clock I work my ass off. I then mentioned that first line I wrote. Oddly, after that he started using all his vacation time and become a happier person, and a better manager.
As for co-workers saying stuff, they have and I always respond with some variation of "Yup, thirty years from now I'll still have the photos from these trips and the memories but I won't remember a single line of code I've written today"
Slashdot Mirror
Engineer #1: "Look at our amazing CO2 scrubbing system!"
Engineer #2: "What's powering it?"
Engineer #1: "That very large diesel generator right over there!"
Engineer #2: Looks at floor... "You know..."
Oddly, Ford parts don't fit into my Chevy either!
A system like this should be engineered to have some set of distinct modes like "Standby", "Testing" and "Live".
In order to put the system into "Live." should require a physical interconnect such as a key.
I would imagine from the "console" where you'd choose "Live" be prompted to turn the key. Then once it verified the circuit has been closed you'd then be able to choose from the live menu which thing you wanted to send, you'd then be presented with a big blinking red dialog box saying something like "THIS WILL SEND A MESSAGE STATEWIDE!" where they'd have to accept.
Once the message is sent, the system would automatically transition back into "Standby" mode. The user would then be prompted to open the circuit and remove the key. At that point the user could then choose "live" or "test" again.
I would also make these different modes have different colors / borders etc so there's zero confusion which mode you're in.
Bing is still a search engine? Holy shit. I thought they'd killed that thing years ago.
We've know for a LONG time that Intel's compiler can do tricks with x86 that the GCC guys could only dream of.
Considering they LOX drop and test fire each engine, eventually with this many engines you were bound to have one with a flaw. All I can say is, good job.. better on a test stand than on a Falcon 9.
They could have gotten in touch with a company that makes scanners or something where they could have digitized all this... too bad.
Point taken.
My take on the Indian launch system is this.
1. It's a 4 stage rocket utilizing toxic hard to handle propellants. Everytime you add a stage, it introduces complexity and places where things can go wrong.
2. How fast can they manufacture these things? What happens when SpaceX decides to simply junk launch well worn F9's for 5M so they can write them off the books?
With that all said, buck shot firing a 100+ 3kg satellites into space is cool.
So far I only see Blue Origin as demostrating their system. When they actually put a satellite into orbit, then it'll be more interesting.
Also, they've got a single boutique craft. They don't have a factory cranking them out.
If you're one of the other launch providers, I can only imagine what this must look like.
For years, these companies laughed off SpaceX as some billionaires hobby. I suspect the laughing has officially stopped and lengthy meeting have begun.
These other companies in a response to SpaceX have promised reuseable rockets to bring their costs down, but at this point they're dreams on a whiteboard.
I see a number of problems any competitor is going to have.
1. In many cases their production line is optimized to prevent funding losses from their governmental sponsors, not to create lots of rockets.
2. Their cost/revenue structures are bloated.
2. Once SpaceX sets this pace for launch cadence it's going to be very hard for competitors to keep up. Especially when SpaceX is going to have a literal fleet of used boosters at their disposal. I can only imagine some satellite provider going into talks starting with "If you can't launch 10 a year, then we're walking... oh and we also want them super cheap as well..."
This race to the bottom is going to be very detrimental to other launch providers who'll have to try to cut corners to save costs and speed up production.
I expect to see SpaceX's competitors have more failures.
One option is to set up a separate user. Then use cgroups to limit the cpu/ram that user is allowed to use.
I have to imagine Chrome/Moz/Opera will quickly put in code to throttle threads in their browser.
320 Tflops! I'm going to buy myself one of these cars and then simply rent its CPU out when it's sitting in the driveway!
Imagine thousands of super computing taxis that as soon as they go and sit idle hook back up to the grid and keep computing!
Which pretty much means you're ass is going to be in the seat for the whole ride. Imagine a 120kg adult flying through the cabin because of a 3g deceleration.
Investigator #1: "How did these people die?"
Investigator #2: "That fat fuck splattered against the wall over there was wandering around when suddenly emergency deceleration happened, he went cartwheeling through cabin like a wrecking ball"
Think about the fact that ~700mph = ~1000fps. For something like a hyperloop, the whole tube is going to be embedded with sensors.
The moment an anomaly is detected, I'd imagine a whole pile of safety systems would kick in.
Though one has to imagine, most people generally don't like 3g's of acceleration, so how many miles of tube do you need to get up to the 700mph speed? Go about ~1.2g's during take off and you'll get complaints at the end of the flight.
Ultimately I predict this will be a loser of a deal. They'll build this plant, it'll be massively automated and employ few people and be massively productive.
Let's be frank here... 3 Billion dollars is A LOT of money in Wisconsin terms. This will be a major hit to the states tax revenues.
Would NK freak out if Japan decided to shoot down the warhead? Technically it's flying over their territory. Does that set a bad precedent?
That lot more than software is hardware.
However, in this case I think they should just keep going. Just because even the more exceedingly uncool kids are doing it doesn't mean you should.
I hope this story is true, but my bullshit alarm is going off slightly. So when you didn't get a response to your text... you simply did nothing and waited to fire two of the best pen testers in the world? Sorry sounds fishing, but moving on...
If it did go down this way something tells me when the upper-upper management gets wind of how poorly this piece of asshattery was executed, this executive will be told politely to GTFO. The bad press alone will likely be this clowns undoing. The angry masses will demand a sacrifice and one they shall have.
This is partially a dumpster fire.
Remember that a dumpster fire is where you specifically would light the dumpster on fire behind the store and when everybody ran out to put the dumpster out (to keep the whole building from burning) the thieves would run in and rob the place blind.
We're so busy watching the dumpster burn we missed the part where the republicans after instituting the nuclear option have appointed hundreds of judges. Trump will be a bad memory but these ass clowns will be with us for a long time.
Yeah, a big chunk of the GOP leadership is aghast by what's going on the WH, but it's not stopping them from taking advantage of the situation.
I think a couple of things might happen.
1. He'll simply slip into obscurity as that guy who was the first press secretary in a long line of press secretaries for Trump. Pitted by forgotten.
2. He'll come out strong as being a voice of reason in the white house who finally left in disgust when he realized Trump is surrounded by sycophants and ultimately Trump is a shitweasel. His reputation will be salvaged as the guy who left.
If option 2 becomes true maybe he becomes some kind of spokesman for/against the administration? Who knows!
Remember. None of this is normal.
As cool as all that is, I still think the better solution is to have every roof covered with panels and have local / neighborhood battery storage.
Boss: "Let's deploy this application to the cloud!"
Sysadmin: "Does it make sense to put it in the cloud?"
Boss: >Holds up a CIO magazine with a picture of a cloud on it< "Because it'll be in the CLOUD"
Sysadmin: "What's this application going to do? What type of data is it going to be handling?
Boss: "But it'll be in the cloud, it'll be <looks quickly in magazine> a fully virtualized extensible angular flask framework!"
Sysadmin: "You're just reading buzzwords!"
Boss: "Let's senergize our git repos with our FOSS machines!"
Sysadmin: "Fuck me."
Microsoft still hasn't solved the really annoying nagging problem... apps. I have a really nice blackberry Z10. Well okay, relatively nice, who are we kidding it's a piece of shit. The hardware's okayish... but you know what makes the phone a real piece of shit? I can't fucking run [Insert App I might want]. Granted compared to my wife or daughters that list of apps is small... but I only have to look at the shitton of apps my daughters have on their phones to see why this phone will fail. Does it run the cartwheel app, which seems to be a favorite of theirs. How about the latest chat apps? Yeah, didn't think so. Does it run Candy [King / Crush / Castle / *]? Yeah, didn't think so.
The problem is these companies i.e. app companies know most people have either an Apple or some flavor of Android. Microsoft is either going to make an SDK that mimics to the syscall everything one of those two platforms does or they're fucked.
Don't confuse work and life. You work to live, you don't live to work, that's what differentiates us from beasts of burden. Yes, I love what I do and I'm good at it, but I put my tools down at the end of the day and go home. I garden, I make cheese, I backpack. I unapologetically use up all my time off. When I first started working, I didn't use any and I burned out.
I once had a boss complain to me that use all my vacation time, I ask them if they'd like to go to HR and formally complain I'm using the vacation time that's part of my compensation package. Oddly, they didn't. I then pointed out that they thought it was sad that the company I should value my job over my health and my family. I pointed out that when I'm on the clock I work my ass off. I then mentioned that first line I wrote. Oddly, after that he started using all his vacation time and become a happier person, and a better manager.
As for co-workers saying stuff, they have and I always respond with some variation of "Yup, thirty years from now I'll still have the photos from these trips and the memories but I won't remember a single line of code I've written today"